Pay-per-call employee data API on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to an employee record (ID 109) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units (0.02 USDC, i.e. $0.02 per request).
The provider lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share the same $0.02/request pricing model with no API keys, no rate limits, and no minimum commitments. Payments are handled entirely through the x402 protocol's X-PAYMENT header.
This specific endpoint (/api/v1/employees/109) appears to serve employee data, though the exact response schema is not documented. No OpenAPI spec, detailed docs, or example responses were found in the crawl — the docs, pricing, and API pages all rendered only a "Connect wallet" prompt. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation means callers must discover the response format empirically.
Capabilities
Use cases
- —Retrieving employee record data on demand with per-call USDC micropayments
- —Integrating employee lookups into agent workflows without managing API keys
- —Demonstrating x402 payment protocol integration on the Base network
Fit
Best for
- —Developers experimenting with x402 pay-per-call protocols
- —Agents needing keyless, on-demand data access settled in crypto
- —Low-volume or sporadic employee data lookups where subscription pricing is wasteful
Not for
- —High-volume bulk employee data retrieval (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/109 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no response schema, no example payloads, and the docs pages are effectively empty (wallet-connect only). The purpose of the /employees/109 endpoint is only inferable from the URL path. This is essentially a stub listing.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown
- —Docs, pricing, and API pages render only a 'Connect wallet' prompt with no substantive content
- —The specific purpose and fields of the /api/v1/employees/109 endpoint are undocumented
- —Cannot verify what data is actually returned without making a paid request
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base at maxAmountRequired 20000https://lowpaymentfee.com/api/v1/employees/109
- —All endpoints priced at $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/109