x402basequality 0.30

Pay-per-call employee data API 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/74

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/74` returns JSON data for employee ID 74 when called with a valid x402 payment header. Payment is settled on the Base network using USDC (contract 0x8335…2913) at a cost of $0.02 per request (20,000 base units with 6 decimals).

The endpoint is part of a broader API platform hosted at lowpaymentfee.com that offers multiple categories of pay-per-call services including data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced uniformly at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; authentication and billing are handled entirely through the x402 payment challenge mechanism.

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 request/response examples, and no description of what fields the employee record contains. The endpoint accepts POST requests based on the outputSchema in the 402 challenge, but the expected request body (if any) and the response shape are unknown.

Capabilities

x402-paymentusdc-baseemployee-datapay-per-callno-api-key

Use cases

  • —Retrieving employee records by ID via automated agent workflows
  • —Integrating employee data lookups into x402-compatible payment pipelines
  • —Demonstrating x402 micropayment protocol usage with a simple data endpoint

Fit

Best for

  • —Agents or bots that need on-demand employee data without API key management
  • —Developers experimenting with x402 payment protocol on Base
  • —Workflows requiring low-cost, single-call data retrieval

Not for

  • —Bulk employee data exports or batch processing (no documented batch endpoint)
  • —Use cases requiring detailed schema documentation or SLA guarantees
  • —Production HR systems needing authenticated, auditable access controls

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing and network details. However, there is no OpenAPI schema, no documentation beyond a landing page listing, no request/response examples, and the docs pages are empty. The specific purpose of the employees endpoint is undocumented, making this effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response shape are completely unknown
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The employee data endpoint's fields, filters, and behavior are undocumented
  • —No information on data source, freshness, or accuracy of employee records

Citations

Provenance

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

Agent access

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