Pay-per-call employee data endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves employee data (specifically record ID 135) behind a micropayment wall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised — access is granted purely through the x402 payment header.
The endpoint is part of a broader platform (lowpaymentfee.com) that advertises multiple API categories including data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, the specific endpoint probed (/api/v1/employees/135) is not listed among the advertised categories on the landing page, so its exact data schema and response fields are unknown. The platform's documentation, pricing, and API pages all appear to require a wallet connection and provide no additional detail in the crawled content.
Because there is no OpenAPI spec, no response schema, and no documentation beyond the landing page summary, the actual structure of the employee record returned is unclear. Agents should expect a JSON response but will need to inspect the payload to determine available fields.
Capabilities
Use cases
- —Retrieving employee record #135 via a single micropayment call
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-call employee data into agent workflows
Fit
Best for
- —Agents needing on-demand employee data without subscription commitments
- —Developers experimenting with x402 payment protocol on Base
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Bulk employee data exports or batch queries
- —Use cases requiring documented response schemas before integration
- —Free or subscription-based API access patterns
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/135 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no response schema, no documentation, and the specific /employees/135 path is not mentioned in the site's own advertised API list. The crawled docs/pricing/API pages are all blank beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No OpenAPI or response schema available — response structure is unknown
- —The /api/v1/employees/135 path is not listed among the provider's advertised endpoints
- —Documentation, pricing, and API pages returned no useful content beyond 'Connect wallet'
- —The nature and source of the 'employee' data is undocumented; data accuracy and freshness are unknown
Citations
- —The endpoint returns a 402 challenge requiring USDC payment on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/135
- —The platform advertises $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/135