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/10/salary` returns salary information for employee ID 10 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) with no API keys, accounts, or rate limits required.
The endpoint charges a maximum of 0.02 USDC per request (20,000 base units with 6 decimals), consistent with the provider's flat $0.02/request pricing across all their APIs. The provider, lowpaymentfee.com, hosts a broader catalog of endpoints spanning data analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/crypto market data, and utility services — all at the same $0.02 per-call price point.
Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The endpoint is live (returns a valid 402 challenge), but the actual shape of the salary data returned after payment is unknown. The employee salary use case appears to be a demonstration or sample endpoint rather than a production HR data source.
Capabilities
Use cases
- —Demonstrating x402 payment protocol integration with a simple data endpoint
- —Fetching sample employee salary data for testing pay-per-call workflows
- —Prototyping agent-to-API payment flows on Base L2
Fit
Best for
- —Developers experimenting with x402 protocol payments
- —Testing micropayment-gated API calls on Base
- —Learning how pay-per-request endpoints work without API key setup
Not for
- —Production HR or payroll data needs — this appears to be sample/demo data
- —High-volume bulk data retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/10/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the actual data returned is unknown. The employee salary endpoint appears to be a demo resource with no clear production utility.
Warnings
- —No documentation available — all doc/pricing/API/README pages render only 'Connect wallet'
- —No OpenAPI or schema definition; request body and response shape are completely unknown
- —The endpoint appears to serve demo/sample data (employee #10 salary) rather than a real data source
- —No information on data freshness, accuracy, or source of salary data
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/employees/10/salary
- —The provider charges $0.02 per request across all endpoints with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/10/salary