Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to employee salary data via a simple POST request. The specific resource `/api/v1/employees/121/salary` returns salary information for employee ID 121 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) at a cost of $0.02 per request.
The endpoint is live and returns a standard x402 402 challenge when called without payment. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs across categories including data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments. All endpoints settle on the Base L2 network.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint's actual behavior (required POST body fields, response structure) must be discovered experimentally.
Capabilities
Use cases
- —Retrieving employee salary information programmatically
- —Integrating salary data into payroll or HR dashboards
- —Agent-driven compensation benchmarking workflows
Fit
Best for
- —Developers needing quick, keyless access to salary data
- —AI agents that can settle x402 payments on Base
- —Prototyping pay-per-call data integrations without signup
Not for
- —Production HR systems requiring documented SLAs and schemas
- —Users who need bulk employee data exports (single-employee endpoint)
- —Anyone unable to settle USDC payments on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/121/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The actual data returned is unknown, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content
- —The endpoint path suggests access to a specific employee record (ID 121); generalizability to other IDs is unconfirmed
- —No SLA, rate limit, or uptime guarantees documented
Citations
- —Endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units USDC on Basehttps://lowpaymentfee.com/api/v1/employees/121/salary
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/121/salary