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

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically record ID 181) 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 0.02 USDC per request (20,000 base units at 6 decimals).

The endpoint is part of a broader platform (lowpaymentfee.com) that advertises multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. The platform emphasizes simplicity: no API keys, no rate limits, no commitments, and instant access. Payment is handled entirely through the x402 header mechanism on the Base L2 network.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all resolve to a minimal "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the employee record contains or what POST body (if any) is expected. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data returned after payment is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-dataper-call-pricingno-api-keyjson-response

Use cases

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

Fit

Best for

  • —Agents that need on-demand employee data with no subscription
  • —Developers exploring x402 payment protocol integrations
  • —Use cases requiring keyless, pay-as-you-go API access

Not for

  • —Bulk employee data retrieval (no batch endpoint documented)
  • —Users who need detailed API documentation or schema guarantees before integrating
  • —Non-crypto payment workflows (USDC on Base only)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, confirming pricing and network details. However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schema, no description of what the employee data contains. The listing is effectively a stub with only the 402 challenge and landing page to go on.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet' with no content
  • —No OpenAPI or schema describing request body or response fields for the employee endpoint
  • —The specific endpoint path (/api/v1/employees/181) suggests a single hardcoded record; unclear if other IDs are available
  • —Purpose and contents of the 'employee' data are completely undocumented

Citations

Provenance

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

Agent access

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