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

What it does

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

The specific endpoint `/api/v1/employees/171` returns JSON data when a valid x402 payment header is included with a POST request. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request. Payment is settled on-chain to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout window.

The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example request/response payloads, and no description of the employee data model or what fields are returned. The endpoint is confirmed live (402 challenge captured), but the actual data behind the paywall is unknown.

Capabilities

x402-paymentusdc-micropaymentbase-networkemployee-datapay-per-requestno-api-key

Use cases

  • —Retrieving employee record data for ID 171 via a single paid API call
  • —Demonstrating x402 micropayment integration on the Base network
  • —Agent-driven data retrieval without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call data access on Base
  • —Projects requiring on-chain payment settlement for API usage

Not for

  • —Bulk employee data retrieval (single record endpoint, no batch support documented)
  • —Users who need detailed API documentation or schema guarantees before integrating
  • —Anyone without USDC on the Base network

Quick start

# 1. Send a POST to get the 402 challenge
curl -X POST https://lowpaymentfee.com/api/v1/employees/171
# 2. Parse the 402 response, construct an X-PAYMENT header
#    with a valid x402 payment proof (USDC on Base, 20000 base units = $0.02)
# 3. Resend with the header:
curl -X POST https://lowpaymentfee.com/api/v1/employees/171 \
  -H "X-PAYMENT: <payment_proof>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no example responses, and no description of what employee data is actually returned. The docs/pricing/README pages are all empty beyond a wallet connect prompt. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — response format is completely unknown
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The endpoint path suggests a single employee record (ID 171); unclear if other IDs are available or what the data model contains
  • —No example request or response payloads available to verify actual functionality behind the paywall

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/bNmnQT
x402-gated employee data endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart