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 #113) via an x402-gated POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units (i.e., $0.02 per request, since USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The endpoint is part of a broader platform (lowpaymentfee.com) that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities, all priced uniformly at $0.02 per request. However, the specific endpoint probed (/api/v1/employees/113) is not listed on the site's landing page among the advertised APIs. It returns a valid 402 challenge with description "Premium API Access" and outputs application/json.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example request/response payloads, and no description of the employee data model or what fields are returned. The endpoint is live and responds correctly to the x402 protocol, but without documentation it is difficult to know exactly what data is returned or what input the POST body expects.
Capabilities
Use cases
- —Retrieving employee record data on a pay-per-call basis without subscription
- —Agent-driven data lookups where per-request USDC micropayments are preferred over API keys
- —Integrating employee information into workflows that support x402 payment headers
Fit
Best for
- —Developers or agents that already support x402 payment flows on Base
- —Low-volume, on-demand employee data retrieval without upfront commitments
- —Use cases where avoiding API key management is desirable
Not for
- —High-volume bulk employee data exports (no documented batch endpoint)
- —Users who need detailed documentation or schema guarantees before integration
- —Non-crypto payment workflows — only USDC on Base is accepted
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/113 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, there is no OpenAPI schema, no documented request/response format, no example payloads, and the /docs pages are empty. The specific employee endpoint is not even listed among the site's advertised APIs. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or JSON schema describing request body or response format for this endpoint.
- —The /api/v1/employees/113 path is not listed among the site's advertised APIs, raising questions about whether it is a production endpoint or a demo/test resource.
- —No example responses available; the data model for employee records is unknown.
Citations
- —The endpoint returns a 402 challenge requesting USDC payment on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/employees/113
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/employees/113
- —The site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompt with no substantive content.https://lowpaymentfee.com/docs