x402basequality 0.35

x402-gated employee data endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to an employee record (ID 16) via the x402 payment protocol. It is part of a broader platform offering various pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 micropayments on the Base network using USDC.

The specific endpoint `/api/v1/employees/16` returns JSON data (MIME type application/json) for a single employee resource. Payment is settled on-chain on Base to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum amount required per request is 20,000 base units of USDC (6 decimals), which equals $0.02. The endpoint accepts POST requests and has a payment timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. However, 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 response examples, and no description of what fields the employee record contains. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data to expect in a successful response.

Capabilities

x402-paymentusdc-micropaymentbase-networkemployee-datajson-responsepay-per-request

Use cases

  • Retrieving employee record data for ID 16 via a single paid API call
  • Demonstrating x402 micropayment integration on Base network
  • Agent-driven data retrieval with per-call USDC payment

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need on-demand employee data without API key management
  • Low-volume, pay-as-you-go data access

Not for

  • Bulk employee data retrieval (single-record endpoint only)
  • Users who need detailed API documentation or response schema before integrating
  • Production use cases requiring SLA guarantees or support

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no response examples, no documentation of the employee data fields, and the docs/pricing/README pages are all empty. The endpoint's purpose (employee record by ID) is only inferable from the URL path.

Warnings

  • No OpenAPI or response schema available — the structure of a successful response is unknown.
  • Documentation pages (/docs, /pricing, /README, /api) contain no substantive content, only a 'Connect wallet' prompt.
  • The specific data returned for an employee record is undocumented; field names and types are unknown.
  • This endpoint serves a single hardcoded employee ID (16); it is unclear if other IDs are available or how to discover them.

Citations

Provenance

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

Agent access