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/145/salary` returns salary information for employee ID 145 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 hosting provider, lowpaymentfee.com, operates a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced uniformly at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, documentation beyond the landing page is essentially empty (all doc/pricing/API pages just show a "Connect wallet" prompt), so there is no schema documentation, example payloads, or detailed field descriptions available for this specific endpoint.
The endpoint is live: it returns a proper x402 version-1 challenge with a 402 status code when called without payment. The challenge specifies the `exact` payment scheme, a max amount of 20,000 base units of USDC (6 decimals → $0.02), and a 300-second timeout. Because no request body schema or response schema is documented, callers will need to experiment or rely on the generic JSON response. The employee-salary framing suggests HR/payroll demo data rather than a production HR system, but this is not confirmed.
Capabilities
Use cases
- —Retrieving employee salary information programmatically with per-call payment
- —Demonstrating x402 protocol payment flows on Base network
- —Integrating pay-per-use data endpoints into agent workflows without API keys
Fit
Best for
- —Developers experimenting with x402 micropayment protocols
- —Agents that need on-demand salary/payroll data without subscription commitments
- —Testing USDC-settled pay-per-call API integrations on Base
Not for
- —Production HR/payroll systems requiring authenticated, auditable access
- —Bulk data retrieval where per-call pricing would be cost-inefficient
- —Users without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/145/salary \
-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 documentation, no request/response schema, no examples, and the docs pages are all blank. The purpose of the data (employee salary) is unclear — it may be demo/synthetic data. Effectively a stub listing.
Warnings
- —No API documentation available — all doc pages show only 'Connect wallet'
- —No request body schema or response schema documented
- —No example responses available; actual data content and structure unknown
- —Employee salary data context is unclear — may be synthetic/demo data
- —No OpenAPI spec or AI plugin manifest found
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/employees/145/salary
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/employees/145/salary