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

What it does

This endpoint at lowpaymentfee.com provides access to employee data (specifically record ID 144) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider lowpaymentfee.com hosts a broader suite of APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with the same x402 payment model on Base.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the employee record contains or what input the POST body expects. The endpoint is confirmed live (returns 402 challenge), but the actual data shape and purpose remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-dataper-call-pricingno-api-keyjson-response

Use cases

  • Retrieving employee record data on a pay-per-call basis without needing API keys
  • Integrating employee information into agent workflows that support x402 payments
  • Demonstrating x402 micropayment protocol usage on Base network

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need on-demand employee data without subscription commitments
  • Low-volume, pay-as-you-go data retrieval

Not for

  • Production HR systems requiring well-documented, schema-validated APIs
  • High-volume bulk employee data exports (no documented batch endpoint)
  • Users without a Base-network USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/144 \
  -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 via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and documentation pages are empty stubs. The purpose and data shape of the employee endpoint are entirely undocumented, making this effectively a stub listing.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet' with no content
  • No OpenAPI or schema describing request body or response fields for the employee endpoint
  • Purpose and contents of employee record 144 are unknown — no field descriptions anywhere
  • The specific endpoint path (/api/v1/employees/144) suggests a single hardcoded record; unclear if other IDs are supported

Citations

Provenance

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

Agent access