x402basequality 0.30

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/151

What it does

This endpoint at lowpaymentfee.com provides access to employee data records via the x402 payment protocol. The specific resource `/api/v1/employees/151` returns JSON data for employee ID 151 when a valid USDC micro-payment is submitted on the Base network. The endpoint is live and responds with a standard x402 challenge (HTTP 402) requiring payment of up to 20,000 base units of USDC (0.02 USD) per request.

The provider lowpaymentfee.com hosts a broader suite 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 advertised at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments settle on the Base L2 network using USDC (contract 0x8335…2913).

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the employee record contains or what input parameters the POST method expects. The endpoint is confirmed live via the 402 challenge, but the actual data returned after payment is unknown from available materials.

Capabilities

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

Use cases

  • —Retrieving employee records by ID with per-call USDC payment
  • —Integrating employee data into agent workflows without API key management
  • —Programmatic access to personnel information via crypto micro-payments

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 lookups where $0.02/request is cost-effective

Not for

  • —High-volume bulk employee data exports (no documented batch endpoint)
  • —Users who need detailed API documentation or schema guarantees before integrating

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation of request parameters or response fields, and all doc pages render only a wallet-connect prompt. The actual data returned is entirely unknown, making this effectively a stub listing.

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 employees endpoint
  • —The purpose and contents of the employee data record are undocumented and cannot be verified
  • —The endpoint path suggests a demo/sample resource (employee ID 151) rather than a production dataset

Citations

Provenance

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

Agent access

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