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 employee record #173) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — access is gated purely by the x402 micropayment.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers numerous pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, the specific endpoint being listed here (/api/v1/employees/173) is not explicitly documented on the site's landing page among the advertised API categories. Its purpose appears to be retrieving data for a specific employee resource, but the exact response schema and input parameters are not documented.

The probe confirms the endpoint is live, returning a proper 402 challenge with x402 version 1. The payment timeout is 300 seconds. Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no example requests or responses, and no description of what fields the employee record contains.

Capabilities

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

Use cases

  • Retrieving employee record data with per-call micropayments
  • Integrating employee data into agent workflows without API key management
  • Demonstrating x402 payment protocol for data access

Fit

Best for

  • Agents or applications that need on-demand employee data without subscription commitments
  • Developers experimenting with x402 micropayment-gated APIs
  • Low-volume or sporadic data retrieval where pay-per-call is cost-effective

Not for

  • High-volume bulk employee data exports (no documented batch endpoint)
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Applications needing employee search or listing (this endpoint targets a single record by ID)

Quick start

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

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 documented request/response schema, no examples, and the specific /employees/173 path is not listed among the site's advertised APIs. Documentation pages are effectively empty. The listing is largely inferred from the 402 challenge and the site's generic landing page.

Warnings

  • The /api/v1/employees/173 endpoint is not listed among the advertised APIs on the provider's landing page — its purpose and data content are unclear.
  • All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no usable content.
  • No OpenAPI spec or response schema is available; the structure of the returned employee data is unknown.
  • The endpoint may be a demo or placeholder rather than a production data source.

Citations

Provenance

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

Agent access