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 161) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint follows the x402 protocol: unauthenticated callers receive a 402 Payment Required challenge, and once a valid X-PAYMENT header with a USDC micropayment is attached, the endpoint returns its JSON payload.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. This particular endpoint appears to serve structured employee salary information, though the exact response schema is not documented. The site's docs, pricing, and API pages are behind a wallet-connect gate, so detailed documentation is unavailable.
Because there is no OpenAPI spec, no response schema, and no example responses available, the actual fields and structure of the salary data returned are unknown. Agents should treat this as a low-cost exploratory endpoint and verify the response format before relying on it in production workflows.
Capabilities
Use cases
- —Retrieving salary information for a specific employee record
- —Integrating pay-per-call payroll data into agent workflows
- —Demonstrating x402 micropayment protocol usage on Base
Fit
Best for
- —Agents needing on-demand employee salary data without API key registration
- —Developers experimenting with x402 micropayment-gated APIs
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Bulk payroll data exports requiring thousands of records at once
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Production systems needing a well-documented response schema
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/161/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/employees/161/salary",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402_payment_token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no response schema, no example responses, and the site's documentation pages are gated behind wallet-connect with no visible content. The purpose ('employee salary data') is only inferable from the URL path.
Warnings
- —No OpenAPI or response schema available — actual response structure is unknown
- —Documentation pages (docs, pricing, API, README) are all behind a wallet-connect gate and returned no useful content
- —The endpoint path references a specific employee ID (161); it is unclear if other IDs are supported or if this is a demo
- —The nature and source of the 'employee salary' data is undocumented — could be synthetic/demo data
Citations
- —Endpoint returns a 402 x402 challenge with USDC on Base network, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/161/salary
- —Site advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/161/salary