x402basequality 0.30

Pay-per-call employee data API on Base, settled in USDC via x402 protocol.

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 #186) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC at a cost of $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities, all priced at $0.02 per request. However, this specific endpoint (`/api/v1/employees/186`) is not listed on the platform's landing page among the advertised APIs, and no documentation describes the employee data schema or what fields are returned. The endpoint is live and returns a proper 402 challenge, confirming it is operational.

Because there is no OpenAPI schema, no response examples, and no documentation beyond the generic "Premium API Access" description, the actual structure and content of the employee data response is unknown. Callers should expect a JSON response but will need to discover the schema empirically.

Capabilities

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

Use cases

  • Retrieving employee record data on a per-request payment basis
  • Agent-driven data lookups that require no pre-registration or API keys
  • Programmatic access to employee information settled via crypto micropayments

Fit

Best for

  • Agents or applications needing on-demand employee data without subscription commitments
  • Developers experimenting with x402 pay-per-call patterns on Base
  • Low-volume, ad-hoc data retrieval where per-request pricing is preferred

Not for

  • High-volume bulk employee data exports (no batch endpoint documented)
  • Use cases requiring a well-documented, stable schema with guaranteed fields

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/186 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_proof>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid 402 challenge, but there is no OpenAPI schema, no response examples, and no documentation describing the employee data model. The endpoint path (/api/v1/employees/186) is not listed among the platform's advertised APIs, raising questions about its intended use. Effectively a stub listing.

Warnings

  • No OpenAPI or response schema available — the structure of the returned employee data is unknown.
  • This specific endpoint (/api/v1/employees/186) is not listed among the platform's advertised API categories.
  • Documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no useful content.
  • The nature and source of the 'employee' data is undocumented — verify data content and privacy compliance before use.

Citations

Provenance

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

Agent access