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 #137) 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 priced uniformly at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments are handled entirely through the x402 protocol on the Base L2 network.
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/137 endpoint is unknown beyond the fact that it serves application/json. The endpoint is confirmed live (returns a valid 402 challenge).
Capabilities
Use cases
- —Retrieving employee record data on a per-call payment basis
- —Demonstrating x402 payment protocol integration for data APIs
- —Agent-driven data retrieval with automatic crypto micropayments
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need on-demand employee data without API key management
- —Low-volume, pay-as-you-go data access on Base
Not for
- —Bulk employee data retrieval (no documented batch endpoints)
- —Users who need detailed API documentation or response schema guarantees
- —Non-crypto users who cannot settle payments on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/137 \
-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 request/response schema, no documentation beyond a wallet-connect prompt, and the actual data returned by this employee endpoint is completely undocumented. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition; request body format and response structure are unknown
- —The purpose and content of the /api/v1/employees/137 endpoint is undocumented — it is unclear what employee data is returned or whether this is sample/demo data
- —No robots.txt or agents.txt present
Citations
- —Endpoint returns a valid x402 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/employees/137
- —All endpoints priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/137