Pay-per-call employee salary lookup API on Base via x402, settled in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to employee salary data via a simple POST request. It is part of a broader suite of pay-per-call APIs offered by the provider, spanning data analytics, AI/ML inference, finance, and utility categories. The specific resource `/api/v1/employees/9/salary` returns salary information for employee ID 9 in JSON format.
Payment is handled via the x402 protocol on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys are needed; payment is made inline with each request via the X-PAYMENT header. The provider advertises no rate limits and instant access.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary response contains. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response payload structure is unknown.
Capabilities
Use cases
- —Retrieving salary data for a specific employee on demand
- —Integrating employee compensation data into payroll or HR dashboards
- —Agent-driven lookups of salary information without API key management
Fit
Best for
- —Developers needing quick, keyless access to employee salary data
- —AI agents that can settle x402 payments on Base
- —Applications requiring pay-per-use data access without subscriptions
Not for
- —Bulk employee data exports (single-employee endpoint, no batch support evident)
- —Users who cannot transact in USDC on the Base network
- —Production use cases requiring documented response schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/9/salary \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming it accepts payments. However, there is no OpenAPI schema, no documented request/response format, no examples, and the docs pages are empty. The specific endpoint (employees/9/salary) is not even listed on the provider's landing page, making its purpose and output entirely inferred from the URL path. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Docs, pricing, and API pages render only 'Connect wallet' with no technical content
- —This specific endpoint (/api/v1/employees/9/salary) is not listed among the provider's advertised APIs — it may be a demo or test resource
- —Response payload structure is completely unknown
- —The hardcoded employee ID '9' in the path suggests this may be a demo endpoint rather than a general-purpose API
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/9/salary
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/9/salary
- —Provider advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com