Pay-per-call employee salary data endpoint on Base via x402 (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to employee salary data (specifically employee ID 119) via an x402 payment-gated POST request. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.
The x402 challenge confirms the endpoint is live and accepts payments in USDC (contract 0x8335…2913 on Base) with a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals). The platform advertises flat $0.02/request pricing across all endpoints, no API keys, no rate limits, and no minimum commitments. Payment is made via the x402 protocol's X-PAYMENT header.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further 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 a POST method. The endpoint path suggests it returns salary information for a specific employee (ID 119), but the actual payload structure is unknown.
Capabilities
Use cases
- —Retrieving salary data for employee records via automated agents
- —Integrating pay-per-call salary lookups into HR or payroll workflows
- —Demonstrating x402 payment protocol integration on Base
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents needing on-demand salary data without API key management
- —Low-volume, pay-as-you-go data access on Base
Not for
- —Bulk payroll data exports requiring thousands of records at once
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/119/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the purpose of the specific endpoint (employee 119 salary) is only inferable from the URL path. The broader site's docs pages are empty.
Warnings
- —No OpenAPI schema or request/response documentation available
- —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
- —The endpoint path is hardcoded to employee ID 119 — unclear if other employee IDs are supported
- —No information on what fields the salary response contains or what POST body is expected
- —The nature of the 'employee salary' data is unclear — could be demo/synthetic data
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/119/salary
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/119/salary