Pay-per-call employee data API on Base, settled in USDC via x402 at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #191) via the x402 payment protocol. 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).
The provider lowpaymentfee.com hosts a broader suite of pay-per-call APIs spanning data & analytics, AI/ML (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 advertised at $0.02 per request with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific data returned by the /api/v1/employees/191 endpoint is unknown beyond the fact that it serves application/json. The endpoint is confirmed live via a valid 402 challenge.
Capabilities
Use cases
- —Retrieving employee record data on a per-call payment basis without API key management
- —Integrating employee data lookups into agent workflows that support x402 payments
- —Demonstrating x402 micropayment protocol usage with USDC on Base
Fit
Best for
- —Agents or applications that support x402 payment protocol
- —Use cases requiring keyless, pay-per-call access to employee data
- —Developers experimenting with crypto-settled API micropayments
Not for
- —Bulk employee data retrieval (no documented batch endpoints)
- —Users who need detailed API documentation or request/response schemas before integration
- —Applications that cannot settle payments in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/191 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The purpose of the employees/191 endpoint is unclear beyond its URL path.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
- —No request body schema or response schema documented; the data returned by /api/v1/employees/191 is unknown
- —No OpenAPI or ai-plugin manifest found
- —The endpoint path suggests a single hardcoded employee record (#191); unclear if other employee IDs are supported
Citations
- —The endpoint returns a 402 challenge requesting USDC payment on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/191
- —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/191