x402basequality 0.35

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
Endpoint
https://lowpaymentfee.com/api/v1/employees/183

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #183) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units 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 uniformly at $0.02 per request. However, the specific endpoint being listed here (/api/v1/employees/183) is not documented on the provider's landing page among the advertised API categories. It appears to be an employee resource endpoint, but the exact schema of the response (fields returned, data format) is not documented anywhere in the crawled material.

The endpoint is confirmed live — it returns a proper 402 challenge with x402 version 1 headers. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (Base mainnet USDC). The maximum timeout for payment settlement is 300 seconds.

Capabilities

x402-paymentusdc-baseemployee-datajson-apipay-per-callno-api-key

Use cases

  • —Retrieving employee record data on a per-call payment basis
  • —Integrating employee information into agent workflows without API key management
  • —Accessing structured personnel data with crypto micropayments

Fit

Best for

  • —Agents needing on-demand employee data without subscription commitments
  • —Developers prototyping x402 payment flows against a live endpoint
  • —Low-volume lookups where per-call pricing is more economical than a subscription

Not for

  • —Bulk employee data exports requiring thousands of records at once
  • —Users who cannot transact in USDC on the Base network
  • —Applications requiring documented response schemas before integration

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/183
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but the /api/v1/employees/183 path is not listed among the provider's documented APIs. There is no OpenAPI schema, no response example, and no documentation of what fields the employee record contains. The crawled docs/pricing/README pages are all blank beyond a 'Connect wallet' prompt.

Warnings

  • —The /api/v1/employees/183 endpoint is not listed among the provider's advertised APIs on the landing page — it may be a demo or test resource.
  • —No response schema or example response is available; callers cannot know what fields to expect.
  • —Documentation pages (/docs, /pricing, /README) returned no meaningful content beyond 'Connect wallet'.
  • —The nature and source of the 'employee' data is unknown — verify data provenance and privacy compliance before use.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/TpPnXK
Pay-per-call employee data API on Base, settled in USDC via x402 at $0.02/request. — Clawmart · Clawmart