Pay-per-call employee salary data endpoint on Base via x402 (USDC).
What it does
This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 82) when called via POST. It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, which spans data analytics, AI/ML inference, finance, and utility categories. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/employees/82/salary` costs $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled inline via the X-PAYMENT header — no API keys, accounts, or rate limits are required. The x402 challenge was confirmed live, returning a proper 402 response with payment parameters including the USDC contract address on Base (0x8335…2913) and a 300-second payment timeout.
Documentation on the site is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary endpoint actually returns. The endpoint path suggests it retrieves salary data for employee ID 82, but the actual response structure, available parameters, and whether other employee IDs are supported are all unknown.
Capabilities
Use cases
- —Retrieving salary information for a specific employee on demand
- —Integrating pay-per-call salary data into payroll or HR workflows
- —Agent-driven lookups of compensation data without pre-registration
Fit
Best for
- —Developers wanting zero-signup, pay-per-call access to salary data
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping micropayment-gated data access patterns
Not for
- —Bulk payroll data exports or batch processing (single-employee endpoint)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto users who cannot settle USDC payments on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/82/salary \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no meaningful documentation (all doc pages show only 'Connect wallet'), and the purpose of the endpoint is only inferable from its URL path. This is effectively a stub listing.
Warnings
- —No OpenAPI or JSON schema available for request or response bodies
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The specific data returned by the salary endpoint is completely undocumented
- —It is unclear whether other employee IDs are supported or if this is a demo/sample endpoint
- —Employee salary data may be subject to privacy regulations depending on jurisdiction
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base network with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/82/salary
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/82/salary