Pay-per-call employee salary data endpoint on Base via x402 (USDC).
What it does
This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 157) via a POST request. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML, finance, and utility categories, all settled on the Base network using USDC.
The endpoint charges a maximum of $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled inline via the x402 protocol: callers receive a 402 challenge with payment details, submit an X-PAYMENT header with a signed USDC transaction on Base, and receive the response. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-use.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned 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 returns or what input it expects beyond the POST method. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data is actually returned or how to structure a request body.
Capabilities
Use cases
- —Retrieving salary information for a specific employee on demand
- —Integrating employee compensation data into payroll or HR workflows
- —Agent-driven lookups of salary records without API key management
Fit
Best for
- —Developers needing one-off salary data lookups without subscriptions
- —AI agents that can settle x402 payments on Base
- —Projects already using USDC on Base for micropayments
Not for
- —Bulk payroll data exports (only one employee ID exposed in this endpoint)
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto users who cannot settle USDC payments on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/157/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but documentation is essentially nonexistent — no OpenAPI schema, no request/response examples, and no explanation of what data is returned. The endpoint path (employees/157/salary) is oddly specific with no indication of whether other employee IDs are supported. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all return only a wallet connect prompt
- —No OpenAPI or request/response schema provided; request body format and response fields are unknown
- —Endpoint is hardcoded to employee ID 157 with no indication of parameterization
- —The nature and source of the 'salary' data is completely undocumented — unclear if this is real, mock, or demo data
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/employees/157/salary
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/employees/157/salary