x402-gated employee salary lookup endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to employee salary data (specifically employee ID 185) via an x402 payment-gated POST request. It is part of a broader platform (lowpaymentfee.com) that hosts 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 specific endpoint `/api/v1/employees/185/salary` returns JSON and costs $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is made inline via the x402 protocol: callers receive a 402 challenge with payment parameters, construct a signed USDC payment to the specified address on Base, and include it in the X-PAYMENT header. No API keys, subscriptions, or rate limits are advertised.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the salary response contains or what input the POST body expects. The endpoint appears live (402 challenge returned successfully), but the actual data behind it is unverified and the use case (looking up a single hardcoded employee's salary) is narrow and unclear.
Capabilities
Use cases
- —Retrieving salary information for a specific employee record
- —Demonstrating x402 payment-gated API access on Base
- —Integrating pay-per-call data retrieval into agent workflows
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand employee salary data without API key management
- —Testing USDC micropayment flows on Base
Not for
- —Bulk payroll data retrieval across many employees
- —Anyone needing documented request/response schemas before integration
- —Use cases requiring free or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/185/salary
# Returns 402 with x402 challenge. Include signed USDC payment in X-PAYMENT header to access.Endpoint
Quality
The endpoint is live (402 challenge confirmed), but documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, no explanation of what the salary endpoint returns or what POST body it expects. The use case (a single hardcoded employee ID) is narrow and unexplained. Pricing is clear ($0.02/request) but everything else must be guessed.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —No OpenAPI or output schema provided; request body format and response fields are unknown.
- —Endpoint targets a single hardcoded employee ID (185); unclear if other employee IDs are supported or what the data source is.
- —The nature and provenance of the 'employee salary' data is completely undocumented — could be synthetic/demo data.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base network.https://lowpaymentfee.com/api/v1/employees/185/salary
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 is used for payment on Base.https://lowpaymentfee.com/api/v1/employees/185/salary