x402basequality 0.30

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 166) via the x402 payment protocol. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance, crypto, and utility categories — all gated behind x402 micropayments on the Base network.

The specific resource `/api/v1/employees/166` returns JSON and costs up to $0.02 per request (20,000 base units of USDC on Base, which uses 6 decimals). Payment is made via the x402 "exact" scheme by sending USDC to the specified payTo address. No API keys, rate limits, or upfront commitments are required — callers simply attach an X-PAYMENT header with a valid payment proof.

Documentation on the site is extremely sparse: the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data returned after payment is unknown. The endpoint path suggests it returns information about a specific employee entity, but the structure and fields of that response are not documented anywhere in the crawled material.

Capabilities

x402-paymentusdc-basepay-per-requestemployee-datajson-responseno-api-keyno-rate-limit

Use cases

  • Retrieving employee record data on a per-request payment basis
  • Demonstrating x402 micropayment protocol integration on Base
  • Accessing structured employee information without API key registration

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing on-demand employee data without subscription commitments
  • Projects requiring pay-per-call data access on Base network

Not for

  • Bulk employee data retrieval (no documented batch endpoint)
  • Users who need detailed API documentation or response schemas before integrating
  • Applications requiring non-crypto payment methods

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/166 \
  -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 confirmed live with a valid 402 challenge, but there is zero documentation on request parameters, response schema, or what employee data is actually returned. The docs/pricing/API pages are all blank beyond a wallet connect prompt. This is effectively a stub listing.

Warnings

  • No OpenAPI spec or response schema available — actual response structure is unknown
  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no content
  • The endpoint path '/api/v1/employees/166' is not listed on the provider's homepage among their advertised APIs, raising questions about whether it is a production resource
  • No information on what 'employee' data is returned or its source/accuracy

Citations

Provenance

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

Agent access