Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves employee salary data for a specific employee (ID 106) 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 requires no API keys, no rate limits, and provides instant access — callers simply attach an x402 payment header to authenticate and pay in a single step.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, this specific endpoint (`/api/v1/employees/106/salary`) is not listed on the site's public catalog, and no documentation beyond the x402 challenge was found. The response MIME type is `application/json`, but the exact schema of the returned salary data is undocumented. The endpoint is live and returns a valid x402 challenge (HTTP 402) with x402Version 1.
Because the endpoint path is hardcoded to employee ID 106, it is unclear whether other employee IDs are supported at similar paths or whether this is a demonstration/sample endpoint. No OpenAPI spec, detailed docs, or example responses were available from the crawl. Treat this as a low-documentation endpoint with verified liveness.
Capabilities
Use cases
- —Retrieving salary information for employee records
- —Integrating pay-per-call salary data into HR or payroll workflows
- —Demonstrating x402 micropayment protocol usage with real endpoints
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand salary data without API key management
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Bulk payroll data exports across many employees
- —Production HR systems requiring documented SLAs and schemas
- —Users without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/106/salary \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/employees/106/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, but there is no OpenAPI spec, no documented response schema, no example responses, and the specific employee salary endpoint is not listed on the provider's own catalog page. Effectively a stub with verified liveness.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —Endpoint path is hardcoded to employee ID 106; unclear if other IDs are supported
- —This specific endpoint is not listed on the provider's public API catalog
- —No example response data available; response schema is unknown
- —Docs, pricing, API, and README pages all returned only a 'Connect wallet' stub with no useful content
Citations
- —Endpoint returns HTTP 402 with x402Version 1 challenge on POST, confirming livenesshttps://lowpaymentfee.com/api/v1/employees/106/salary
- —Payment is in USDC on Base network; maxAmountRequired is 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/106/salary
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/106/salary