x402basequality 0.30

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

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/150` returns JSON data for employee ID 150, gated behind a per-request USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts payments using the "exact" scheme.

The provider operates a broader platform offering multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request. The x402 challenge for this specific endpoint advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimal places. No API keys or rate limits are advertised; access is granted purely through the x402 payment header.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example request/response payloads, and no description of what fields the employee record contains. The endpoint is confirmed live (402 challenge captured), but the actual response schema and data content are unknown.

Capabilities

x402-paymentusdc-baseper-request-micropaymentemployee-datajson-responseno-api-key

Use cases

  • Retrieving employee records by ID for HR or payroll integrations
  • Agent-driven lookups of personnel data without API key management
  • Micropayment-gated data access for on-demand employee information

Fit

Best for

  • Developers needing keyless, pay-per-call access to employee data
  • AI agents that can settle x402 USDC payments on Base
  • Prototyping integrations where low per-request cost matters

Not for

  • Bulk employee data exports (no batch endpoint documented)
  • Users without a Base-compatible USDC wallet
  • Production HR systems requiring documented schemas and SLAs

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI schema, no example responses, and no documentation beyond a landing page listing. The actual data returned is completely unknown, making this effectively a stub listing.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or output schema provided; the structure of the employee data response is unknown.
  • The endpoint path '/api/v1/employees/150' is hardcoded to a single employee ID; it is unclear whether other IDs are supported or what the broader API surface looks like.
  • The 'employees' endpoint is not listed on the provider's own landing page, which only advertises analytics, AI, finance, and utility APIs.

Citations

Provenance

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

Agent access