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 employee salary data for a specific employee (ID 98) 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 authorize each call.
The provider (lowpaymentfee.com) hosts a broader 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 listing covers only the `/api/v1/employees/98/salary` endpoint. The response MIME type is `application/json`, and the endpoint accepts POST requests. No OpenAPI schema, request body schema, or response body schema was found in the probe or crawl, so the exact request parameters and response fields are unknown.
The endpoint is live: it returns a proper x402 version-1 challenge (HTTP 402) with a valid USDC asset address on Base (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum payment timeout is 300 seconds. Because no documentation beyond the landing page was retrievable (docs, API, pricing, and README pages all returned only a "Connect wallet" stub), the actual data content and request format remain unverified.
Capabilities
Use cases
- —Retrieving salary information for employee records
- —Integrating pay-per-call salary data into HR or payroll dashboards
- —Agent-driven lookups of employee compensation without managing API keys
Fit
Best for
- —Agents needing on-demand salary data with crypto micropayments
- —Developers who want keyless, pay-as-you-go API access on Base
- —Prototyping x402 payment flows with a low-cost endpoint
Not for
- —Bulk salary data exports (no batch endpoint documented)
- —Users without a Base-network USDC wallet
- —Production HR systems requiring documented schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/98/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page stub, and the endpoint path (employees/98/salary) appears to be a single hard-coded resource with unclear real-world utility. The docs, API, pricing, and README pages are all empty stubs.
Warnings
- —No OpenAPI or request/response schema available — request body format and response fields are unknown.
- —Documentation pages (/docs, /api, /pricing, /README) all return only a 'Connect wallet' stub with no actual content.
- —The endpoint path is hard-coded to employee ID 98; it is unclear whether other employee IDs are supported or what data is returned.
- —The provider's broader API catalog lists many endpoints but none have documented schemas; treat all with caution.
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/employees/98/salary
- —Payment is in USDC on Base network, asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/98/salary
- —maxAmountRequired is 20000 base units = $0.02 USDC (6 decimals)https://lowpaymentfee.com/api/v1/employees/98/salary
- —Provider advertises $0.02/request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages return only 'Connect wallet' stubhttps://lowpaymentfee.com/docs