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 (specifically employee record 200) 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 (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 uniformly priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments are made inline via the x402 X-PAYMENT header on the Base L2 network.

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 request/response schema documentation, and no example payloads available. The specific data returned by the /api/v1/employees/200 endpoint is unknown beyond the fact that it serves application/json. The endpoint is confirmed live (returns a valid 402 x402 challenge).

Capabilities

x402-paymentusdc-settlementbase-networkemployee-datajson-apipay-per-callno-api-key

Use cases

  • Fetching employee data records on demand without API key management
  • Integrating pay-per-call employee lookups into agent workflows
  • Demonstrating x402 payment protocol integration on Base

Fit

Best for

  • Agents needing keyless, pay-per-call access to employee data
  • Developers experimenting with x402 payment protocol on Base
  • Use cases requiring no rate limits and no subscription commitments

Not for

  • Production workloads requiring documented request/response schemas
  • Bulk employee data retrieval (pay-per-call at $0.02 adds up)
  • Users who need detailed API documentation before integration

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no example payloads, and the docs pages are empty. The purpose of the /employees/200 endpoint is only vaguely implied by its URL path.

Warnings

  • No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or schema definition found; request body format and response structure are unknown
  • The specific data returned by /api/v1/employees/200 is undocumented — it may be sample/demo data
  • No robots.txt or agents.txt present

Citations

Provenance

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

Agent access

Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart