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

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/5` returns JSON data for employee ID 5 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 dozens of 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. There are no API keys, no rate limits, and no subscription commitments; each call is individually settled on-chain.

The x402 challenge confirms the endpoint is live and returns a 402 Payment Required response with a maxAmountRequired of 20000 base units. USDC uses 6 decimals, so this equals $0.02 per request. The payment is directed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. Documentation beyond the landing page is sparse — the /docs, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail about request/response schemas for this specific employee endpoint.

Capabilities

x402-paymentusdc-baseemployee-dataper-call-pricingno-api-keyjson-response

Use cases

  • Retrieving employee records on demand without subscription or API key management
  • Integrating employee data lookups into agent workflows that settle payments on Base
  • Demonstrating x402 protocol usage for micro-payment gated REST APIs

Fit

Best for

  • Developers experimenting with x402 payment-gated APIs
  • Agent-based systems that need on-demand employee data with crypto micropayments
  • Projects requiring keyless, pay-as-you-go API access on Base

Not for

  • High-volume bulk employee data exports where per-call pricing is impractical
  • Users without USDC on Base or unfamiliar with on-chain payment flows
  • Production HR systems requiring guaranteed SLAs and detailed documentation

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no request/response examples, and all documentation pages beyond the landing page are empty wallet-connect stubs. The specific employee data schema is entirely unknown.

Warnings

  • No documentation available — /docs, /pricing, /README all render only a wallet connect prompt with no technical content
  • No request or response schema provided for the /api/v1/employees/{id} endpoint
  • The employee data endpoint is not listed on the landing page's API catalog, raising questions about its intended use or demo status
  • Unknown what fields the employee record contains; no sample response available

Citations

Provenance

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

Agent access