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 #117) 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 (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 at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments flow through the x402 protocol on the Base L2 network.
This specific endpoint (/api/v1/employees/117) is not listed on the provider's landing page among the advertised API categories, so its exact response schema and data source are unclear. The probe confirms the endpoint is live (returns a valid 402 challenge), but no documentation, OpenAPI spec, or example responses were found. The docs, pricing, and README pages all returned only a wallet-connect prompt with no substantive content.
Capabilities
Use cases
- —Retrieving employee record data on a per-call payment basis
- —Integrating employee information into agent workflows without API key management
- —Demonstrating x402 payment protocol integration for data access
Fit
Best for
- —Agents needing on-demand employee data without subscription commitments
- —Developers experimenting with x402 pay-per-call patterns on Base
- —Low-volume data lookups where per-request pricing is economical
Not for
- —High-volume bulk employee data retrieval (no documented batch support)
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Applications needing well-documented response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/117 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documentation, no example responses, and the specific /employees/117 path is not listed among the provider's advertised APIs. Response schema is entirely unknown.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /api/v1/employees/117 path is not listed among the provider's advertised API catalog — its data source and accuracy are unknown
- —Docs, pricing, and README pages returned only wallet-connect prompts with no substantive content
- —Response format and fields are undocumented; integration requires trial-and-error
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/117
- —All listed APIs are 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 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/117