Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns employee salary information for a specific employee (ID 170) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint requires no API keys, no rate limits, and provides instant access — callers simply attach an x402 payment header to authenticate.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. This particular endpoint appears to be a demonstration or sample resource (employee salary lookup) rather than a widely documented production data service. No OpenAPI schema, request body specification, or response examples are provided in the crawled documentation — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further detail.
Because the endpoint returned a valid 402 challenge with a well-formed x402 v1 payload, it is confirmed live. However, the lack of documentation about what fields the POST body expects, what the response schema looks like, and whether employee ID 170 is the only valid resource makes this endpoint difficult to integrate without experimentation. Treat this as a low-documentation, exploratory endpoint.
Capabilities
Use cases
- —Retrieving salary data for a specific employee via a micropayment-gated API
- —Demonstrating x402 payment protocol integration with a simple data endpoint
- —Building agent workflows that pay per call for structured employee data
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need on-demand employee salary data without API key management
- —Prototyping pay-per-call data access patterns
Not for
- —Bulk payroll data retrieval (single-employee endpoint, no batch support documented)
- —Production HR systems requiring documented schemas and SLAs
- —Users without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/170/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI schema, no request/response examples, and no meaningful documentation beyond a landing page listing. The specific resource (employee 170 salary) is narrow and undocumented, making integration speculative.
Warnings
- —No OpenAPI or request/response schema available — input and output formats are unknown
- —Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no usable content
- —The endpoint path references a specific employee ID (170); it is unclear whether other IDs are valid
- —This appears to be a demo or sample endpoint rather than a production data service
Citations
- —Endpoint returns a valid x402 v1 challenge with 402 status on POSThttps://lowpaymentfee.com/api/v1/employees/170/salary
- —Payment is in USDC on Base network, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/170/salary
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/170/salary