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 28) via a POST request. It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, all settled on the Base network using USDC. The endpoint charges $0.02 per request (20,000 base units of USDC with 6 decimals) and requires no API keys, accounts, or rate-limit management — payment is handled inline via the x402 protocol's X-PAYMENT header.
The provider's landing page advertises categories spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities, all at a uniform $0.02/request price point. However, this specific endpoint (`/api/v1/employees/28/salary`) is not listed on the homepage, and no documentation, request schema, or response schema is available for it. The endpoint is confirmed live: it returns a proper 402 challenge with x402 version 1, accepting the "exact" payment scheme on Base with USDC (contract 0x8335…2913). The response MIME type is application/json.
Because no OpenAPI spec, example payloads, or detailed docs were found, the actual structure of the salary data returned is unknown. The crawled docs, pricing, API, and README pages all rendered only a "Connect wallet" prompt with no substantive content. Users should treat this as a lightly documented endpoint and test with a small payment to inspect the response format.
Capabilities
Use cases
- —Retrieving salary information for employee records
- —Integrating payroll data into HR dashboards
- —Agent-driven compensation benchmarking queries
Fit
Best for
- —Developers wanting keyless, pay-per-call access to salary data
- —AI agents that can settle USDC payments on Base automatically
- —Prototyping x402 payment flows with a low-cost endpoint
Not for
- —Bulk payroll data exports (single-employee endpoint, no batch mode documented)
- —Users without a Base-network USDC wallet
- —Anyone needing detailed API documentation or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/28/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but there is no OpenAPI schema, no request/response examples, and no documentation beyond a wallet-connect prompt. The specific employee salary endpoint isn't even listed on the provider's homepage. Effectively a stub listing.
Warnings
- —No OpenAPI spec or request/response schema available
- —This specific endpoint (/api/v1/employees/28/salary) is not listed on the provider's homepage — its purpose and data source are unverified
- —All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' prompt with no content
- —The nature and source of the 'salary' data is completely undocumented — it may be demo/mock data
Citations
- —The endpoint returns a 402 challenge with x402 version 1, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/employees/28/salary
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/28/salary
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation, pricing, API, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs