x402basequality 0.35

Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/employees/101

What it does

This endpoint at lowpaymentfee.com provides access to employee data records via the x402 payment protocol. The specific resource `/api/v1/employees/101` returns JSON data for employee ID 101 when called with a POST request and a valid X-PAYMENT header containing a USDC payment on the Base network.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers numerous pay-per-call APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. Payment is made in USDC (contract 0x8335…2913 on Base) using the x402 "exact" scheme, with no API keys, no rate limits, and no upfront commitments required.

The x402 challenge is live and returns a 402 with a well-formed payment challenge. However, documentation is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema, and no example payloads available. The actual shape of the employee data returned is unknown, so callers should expect to discover the response format empirically.

Capabilities

x402-paymentusdc-baseemployee-datapay-per-callno-api-keyjson-response

Use cases

  • —Retrieving employee records on-demand without subscription or API key management
  • —Integrating employee data lookups into agent workflows that support x402 payments
  • —Testing x402 payment protocol integrations with a low-cost live endpoint

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents needing on-demand employee data with crypto micropayments
  • —Low-volume, pay-as-you-go data access without signup

Not for

  • —High-volume bulk employee data exports (no documented batch endpoint)
  • —Users who need detailed API documentation or guaranteed SLAs before integration

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/101
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payments. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the actual data returned is completely undocumented. The listing is effectively a stub with verified liveness.

Warnings

  • —No OpenAPI or schema documentation available — response format is unknown
  • —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no technical content
  • —The specific data returned for /api/v1/employees/101 is undocumented; callers must discover the schema empirically
  • —Employee data endpoints may involve personally identifiable information (PII) — verify compliance requirements

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:31:29Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-25

Agent access

JSONhttps://clawmart.sh/api/listings/FcqASZ
Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart