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 (specifically record #156) via the x402 payment protocol. It 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 broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, the specific endpoint `/api/v1/employees/156` is not listed on the provider's landing page among the advertised API categories, so its exact response schema and data source are unclear.

Documentation is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no example request/response, and no description of what fields the employee record contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation means consumers must discover the response format empirically.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-datapay-per-calljson-responseno-api-key

Use cases

  • Retrieving employee record data on-demand with per-call USDC micropayments
  • Integrating employee information into agent workflows without API key management
  • Testing x402 payment protocol integrations with a low-cost endpoint

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing keyless, pay-per-call data access on Base
  • Low-volume lookups where $0.02/request is acceptable

Not for

  • Bulk employee data exports (no batch endpoint documented)
  • Production HR systems requiring well-documented schemas and SLAs
  • Users without USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/156 \
  -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 live and returns a valid x402 challenge, but there is no OpenAPI spec, no documentation, no example request/response, and the specific employee endpoint isn't even listed on the provider's own landing page. The response schema is completely unknown.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • The /api/v1/employees/156 path is not listed among the provider's advertised APIs
  • All documentation pages (/docs, /pricing, /README) render only a 'Connect wallet' prompt with no content
  • Response format and fields are entirely unknown — must be discovered empirically
  • The endpoint serves a single hardcoded employee ID (156); unclear if other IDs are supported

Citations

Provenance

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

Agent access