x402basequality 0.30

x402-gated employee data endpoint on Base, pay $0.02 per request in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to an employee record (ID 94) behind an x402 payment wall. The provider operates a broad catalog of pay-per-request APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per call, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The specific endpoint `/api/v1/employees/94` is described only as "Premium API Access" with no further documentation on request parameters or response shape. The x402 challenge confirms it accepts POST requests and returns `application/json`. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 USD. Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a 300-second timeout.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no explanation of what the employees endpoint actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

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

Use cases

  • —Retrieving employee record data on a per-request payment basis
  • —Integrating pay-per-call employee lookups into agent workflows
  • —Testing x402 payment protocol integrations with a low-cost endpoint

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand employee data without API key management
  • —Low-volume, pay-as-you-go data retrieval

Not for

  • —Bulk employee data exports (single-record endpoint, no batch support evident)
  • —Users who need detailed API documentation before integration
  • —Production HR systems requiring guaranteed SLAs or compliance certifications

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/94 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_proof>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what 'employees/94' actually returns. The docs pages are empty wallet-connect stubs. Pricing is clear ($0.02/request) but the endpoint's purpose is opaque.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet' with no content
  • —No OpenAPI spec or response schema provided; the actual data returned by /api/v1/employees/94 is unknown
  • —The endpoint path suggests access to a specific employee record (ID 94) but no context is given on what employee data is served or its source
  • —This appears to be a demo or test catalog; the breadth of advertised endpoints (AI, finance, geocoding, employee data) from a single provider with no docs is unusual

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:54:36Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/mzXbfS
x402-gated employee data endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart