x402-payable employee salary lookup endpoint on Base, settled in USDC at $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to employee salary data via a POST request, gated by the x402 payment protocol. The specific resource `/api/v1/employees/153/salary` returns salary information for employee ID 153 in JSON format. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider (lowpaymentfee.com) hosts a broader catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced at $0.02 per request. However, this specific endpoint appears to be a demonstration or sample resource for employee salary data. Documentation beyond the landing page is extremely sparse — the /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for what fields the salary response contains or what input the POST body expects.
The endpoint is confirmed live: the probe received a proper HTTP 402 challenge with a well-formed x402 v1 payment envelope. The x402 challenge specifies an exact payment scheme, a 300-second timeout, and outputs application/json. Without documentation on the expected POST body or response schema, callers will need to experiment or contact the provider for integration details.
Capabilities
Use cases
- —Retrieving employee salary information for a specific employee ID
- —Demonstrating x402 payment protocol integration
- —Building payroll or HR data aggregation tools
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents needing on-demand employee salary data without API key management
- —Prototyping micropayment-based data access patterns
Not for
- —Production HR/payroll systems requiring documented schemas and SLAs
- —Bulk employee data exports across many records
- —Users who need fiat-only payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/153/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs showing only 'Connect wallet'. The purpose of this specific employee salary endpoint is unclear — it may be a demo resource. Effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all return only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided; POST body format is unknown
- —The employee salary endpoint does not appear in the provider's listed API catalog, suggesting it may be a demo or undocumented resource
- —Response schema is entirely unknown — callers must experiment to discover fields
Citations
- —The endpoint returns a valid x402 v1 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/employees/153/salary
- —All APIs on lowpaymentfee.com 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 is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/153/salary