Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to employee salary data via a simple POST request. The specific resource `/api/v1/employees/141/salary` returns salary information for employee ID 141 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) at a cost of $0.02 per request.
The endpoint is part of a broader API platform (lowpaymentfee.com) that offers dozens of pay-per-call endpoints across data analytics, AI/ML inference, finance, and utility categories — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. Payment is made by attaching an X-PAYMENT header with a signed x402 payment challenge; no traditional authentication or subscription is required.
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. The endpoint is confirmed live (returns a proper 402 challenge), but the actual response payload structure is unknown.
Capabilities
Use cases
- —Retrieving salary information for a specific employee by ID
- —Integrating pay-per-call salary data into HR or payroll workflows
- —Agent-driven lookups of compensation data without API key management
Fit
Best for
- —Agents or apps needing on-demand employee salary data with no subscription
- —Developers experimenting with x402 payment-gated APIs
- —Use cases where per-request billing is preferred over monthly plans
Not for
- —Bulk salary data exports across many employees (no batch endpoint documented)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto workflows that cannot attach x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/141/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no documented request/response format, no examples, and the docs pages are empty. The purpose of the endpoint (employee salary data) is only inferable from the URL path. This is effectively a stub listing.
Warnings
- —No OpenAPI or JSON schema available for request or response bodies
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
- —The response payload structure is completely unknown — no sample or field descriptions exist
- —The endpoint path suggests employee PII (salary data); consumers should verify data provenance and compliance obligations
- —It is unclear whether employee IDs beyond 141 are valid or what the data source is
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/employees/141/salary
- —Payment is in USDC on Base network with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/141/salary
- —Platform advertises $0.02/request, no API keys, no rate limits, instant accesshttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages show only 'Connect wallet' with no documentation contenthttps://lowpaymentfee.com/docs