Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 79) 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, accounts, or rate-limit management — callers simply attach an x402 payment header with each request.
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 and all using the same x402 payment flow on Base. This particular endpoint appears to serve structured JSON containing employee salary data, though no detailed schema or sample response is documented. The output schema indicates it accepts HTTP POST and is marked as discoverable.
Because the crawled documentation pages (docs, pricing, README) all resolve to a minimal "Connect wallet" prompt with no further content, there is very little information about request parameters, response format, or the nature of the underlying data. The endpoint is confirmed live (returns a proper 402 challenge), but consumers should be aware that documentation is essentially absent.
Capabilities
Use cases
- —Retrieving salary information for employee ID 79 in an automated workflow
- —Demonstrating x402 pay-per-call patterns on the Base network
- —Integrating employee compensation data into an agent pipeline without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol on Base
- —Agents that need on-demand employee salary data without subscription overhead
- —Prototyping micropayment-gated data access
Not for
- —Bulk payroll data retrieval across many employees (single-employee endpoint)
- —Users who need detailed API documentation or guaranteed SLAs
- —Applications requiring non-crypto payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/79/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/employees/79/salary",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, documentation is effectively nonexistent — all doc pages return only a wallet-connect prompt. There is no response schema, no request body schema, no sample responses, and the purpose of the data (employee 79's salary) is opaque. This is essentially a stub listing.
Warnings
- —No API documentation available — all doc/pricing/README pages show only 'Connect wallet'
- —No response schema or example response provided by the provider
- —The endpoint is scoped to a single employee ID (79); unclear if other IDs are supported
- —The nature and source of the 'employee salary' data is undocumented — could be mock/demo data
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network at maxAmountRequired 20000 (= $0.02)https://lowpaymentfee.com/api/v1/employees/79/salary
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/79/salary