Pay-per-call employee data API on Base, settled in USDC via x402 protocol.
What it does
This endpoint at lowpaymentfee.com provides access to employee data (specifically employee record #139) via the x402 payment protocol. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC at a cost of $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys, rate limits, or subscriptions are required — each call is individually paid for via the X-PAYMENT header.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. However, this specific endpoint (/api/v1/employees/139) is not listed among the advertised categories on the landing page, and no documentation describes the employee data schema or what fields are returned. The response MIME type is application/json.
Because the endpoint returned a valid 402 challenge with a well-formed x402 payload, it is confirmed live. The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base. The maximum timeout for payment is 300 seconds.
Capabilities
Use cases
- —Retrieving employee record data on-demand without subscription
- —Integrating employee information into agent workflows with micropayments
- —Testing x402 payment protocol integrations with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand employee data without API key management
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Bulk employee data exports (single-record endpoint, $0.02 each)
- —Use cases requiring documented response schemas before integration
- —Production HR systems needing guaranteed SLAs and support
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/139 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no documentation on the employee data schema, no example responses, no OpenAPI spec, and the /employees/ path is not even listed among the provider's advertised APIs. The response format and fields are entirely unknown.
Warnings
- —The /api/v1/employees/139 path is not listed among the provider's advertised API endpoints — it may be a demo, test, or undocumented resource.
- —No response schema or example response is available; the structure of returned employee data is unknown.
- —Documentation pages (/docs, /api, /pricing, /README) all returned only a 'Connect wallet' prompt with no actual content.
- —The endpoint targets a single hardcoded employee ID (139); it is unclear if other IDs are available or how to discover them.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/139
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02https://lowpaymentfee.com/api/v1/employees/139
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/139
- —The /employees/ endpoint is not listed among the provider's advertised API categorieshttps://lowpaymentfee.com