x402basequality 0.30

Pay-per-call employee data API on Base, settled in USDC via x402 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 (specifically employee record #161) via the x402 payment protocol. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The provider lowpaymentfee.com hosts a broader suite of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments are made inline via the x402 protocol on the Base L2 network.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the employee endpoint returns or what input it expects. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data content and schema remain unknown.

Capabilities

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

Use cases

  • Retrieving employee record data on a per-call payment basis
  • Integrating pay-per-use employee data into agent workflows
  • Accessing structured employee information without API key registration

Fit

Best for

  • Agents needing on-demand employee data without subscription commitments
  • Developers testing x402 payment protocol integrations
  • Low-volume data retrieval where per-call pricing is economical

Not for

  • High-volume bulk employee data exports (no documented batch endpoints)
  • Use cases requiring detailed schema documentation or SLA guarantees
  • Users who cannot transact in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/161 \
  -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 with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and no meaningful documentation — every doc page just shows 'Connect wallet'. The actual data returned by the employee endpoint is completely unknown.

Warnings

  • No documentation available — all doc pages render only 'Connect wallet'
  • No OpenAPI or JSON schema describing request parameters or response fields
  • Unknown what employee data fields are returned
  • The specific endpoint /api/v1/employees/161 is not listed on the provider's homepage; it may be a demo or test record

Citations

Provenance

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

Agent access