x402basequality 0.30

Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 57) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint requires no API keys, no rate limits, and provides instant access — callers simply attach an x402 payment header to authenticate.

The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3, and infrastructure utilities, all priced at $0.02 per request. This particular endpoint (/api/v1/employees/57/salary) appears to serve structured JSON containing salary information for a given employee record. However, documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further detail on request/response schemas, field definitions, or error handling.

Because there is no OpenAPI spec, no request body schema, and no example responses available, the actual data returned and the required POST body are unknown. The endpoint is confirmed live (returns a valid 402 x402 challenge), but consumers should expect to experiment or contact the provider for integration details.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-callno-api-keyjson-response

Use cases

  • Retrieving salary information for employee records programmatically
  • Integrating payroll or compensation data into HR dashboards
  • Agent-driven lookups of employee compensation without API key management

Fit

Best for

  • Developers needing on-demand salary data without subscription commitments
  • AI agents that can settle x402 micropayments on Base
  • Prototyping pay-per-call data integrations

Not for

  • Bulk payroll data exports (no batch endpoint documented)
  • Users who need detailed API documentation or OpenAPI specs before integrating
  • Non-crypto payment workflows (only USDC on Base is accepted)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/57/salary \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 x402 challenge, but there is no OpenAPI spec, no request/response schema, no example payloads, and the docs pages are empty beyond a wallet-connect prompt. The purpose (employee salary data) is only inferable from the URL path. This is effectively a stub listing.

Warnings

  • No OpenAPI or request/response schema available — request body and response format are unknown
  • Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no useful content
  • The endpoint path references a hardcoded employee ID (57); it is unclear if other IDs are supported or how to discover them
  • The nature of the 'employee salary' data is unverified — it could be mock/demo data

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:34:46Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-23

Agent access