x402basequality 0.35

Pay-per-call employee data endpoint 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/122

What it does

This x402-enabled endpoint at lowpaymentfee.com serves employee data (specifically employee ID 122) via a POST request, with payment settled in USDC on the Base network. The endpoint returns a 402 challenge requiring an X-PAYMENT header with an exact-scheme payment of 20,000 base units of USDC (0.02 USD per request, since USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by micropayment.

The provider lowpaymentfee.com hosts a broader catalog of x402 endpoints spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/employees/122` resource. The response MIME type is `application/json`. No OpenAPI schema, detailed documentation, or example responses were found in the crawl — the docs, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content.

Because the endpoint's actual response payload is undocumented and the purpose of an "employees/122" resource is unclear (it may be a demo or sample endpoint), consumers should treat this as a low-documentation offering. The x402 challenge is live and well-formed, confirming the endpoint is operational.

Capabilities

x402-paymentusdc-micropaymentbase-networkjson-responseemployee-datapay-per-call

Use cases

  • —Fetching employee record data (ID 122) with per-call USDC micropayment
  • —Demonstrating x402 payment protocol integration on Base
  • —Testing agent-driven pay-per-request workflows

Fit

Best for

  • —Developers experimenting with x402 micropayment protocols
  • —Agents that need to purchase API data on-the-fly without API keys
  • —Projects already operating on the Base L2 network with USDC

Not for

  • —Production HR or employee management systems (no documentation on schema or data provenance)
  • —Users who need bulk employee data retrieval (single-record endpoint, no batch support evident)

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works. However, there is no OpenAPI schema, no example responses, and the docs/pricing/README pages are all empty (just 'Connect wallet'). The purpose and schema of the employee data returned are entirely undocumented.

Warnings

  • —No documentation available — docs, pricing, and README pages render only 'Connect wallet' with no content.
  • —The response schema for /api/v1/employees/122 is completely undocumented; consumers cannot know what fields to expect.
  • —This appears to be a single-record endpoint (employee 122); it is unclear whether other employee IDs are available or if this is a demo resource.
  • —No OpenAPI or AI plugin manifest found.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:38:05Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-25

Agent access

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