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 employee ID 115) behind a micropayment wall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum charge of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — access is gated purely by the x402 payment header.
The broader lowpaymentfee.com platform advertises a variety of API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. However, this specific endpoint (/api/v1/employees/115) is not listed among the advertised categories on the landing page, and no documentation exists describing the employee data schema, available fields, or what employee records contain. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content.
Because there is no OpenAPI schema, no example responses, and no documentation beyond the x402 challenge itself, the actual shape and usefulness of the returned data is unknown. The endpoint is confirmed live (returns a proper 402 challenge), but prospective consumers should be aware that they are paying for an undocumented resource.
Capabilities
Use cases
- —Retrieving employee record #115 via a single micropayment
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-call data retrieval into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents that need on-demand data access without API key management
- —Low-volume, pay-as-you-go data consumers
Not for
- —Bulk employee data retrieval (single record endpoint, no batch support documented)
- —Users who need detailed API documentation or guaranteed SLAs
- —Production systems requiring well-documented response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/115 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and network details. However, there is zero documentation on the employee data schema, no example responses, no OpenAPI spec, and the endpoint path (/employees/115) doesn't appear in the site's own advertised API catalog. This is effectively a stub listing.
Warnings
- —No documentation exists for the /api/v1/employees/115 endpoint — response schema is completely unknown.
- —This endpoint is not listed among the provider's advertised APIs on the landing page.
- —All doc/pricing/API pages render only 'Connect wallet' with no substantive content.
- —No OpenAPI or schema definition is available.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base network.https://lowpaymentfee.com/api/v1/employees/115
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/employees/115