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 employee data (specifically employee record #118) 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 cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call 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 uniformly priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no example payloads available. The specific data returned by the /api/v1/employees/118 endpoint is unknown beyond the stated mime type of application/json. The endpoint is confirmed live via a valid 402 challenge.
Capabilities
Use cases
- —Retrieving employee record data on-demand with per-call USDC micropayments
- —Integrating employee data into agent workflows without managing API keys
- —Programmatic access to employee information settled via x402 on Base
Fit
Best for
- —Agents or applications needing keyless, pay-per-call employee data access
- —Developers experimenting with x402 payment protocol integrations
- —Use cases where avoiding subscription commitments is preferred
Not for
- —Bulk employee data retrieval or batch processing (no documented batch endpoints)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/118 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The purpose of the employees/118 endpoint is opaque — effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available; request and response formats are unknown.
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no technical content.
- —The specific data returned by /api/v1/employees/118 is undocumented; 'employee data' is inferred from the URL path only.
- —This endpoint targets a single hardcoded employee ID (118); it is unclear if other IDs are supported or how to discover them.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/118
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/118
- —Documentation pages render only a 'Connect wallet' prompt with no further contenthttps://lowpaymentfee.com/docs