x402-gated employee salary endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to employee salary data via an x402 payment-gated API. The specific resource `/api/v1/employees/69/salary` returns salary information for employee ID 69 in JSON format. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).
The endpoint accepts POST requests and requires an X-PAYMENT header conforming to the x402 protocol (version 1, "exact" scheme). The provider site lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments.
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 response contains. The endpoint is confirmed live (402 challenge captured), but the actual data returned after payment is unknown.
Capabilities
Use cases
- —Retrieving salary information for a specific employee via micropayment
- —Integrating pay-per-call employee data into payroll or HR workflows
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Agents or apps needing on-demand employee salary data without API key management
- —Developers experimenting with x402 payment-gated APIs on Base
- —Low-volume, pay-as-you-go data retrieval
Not for
- —Bulk payroll data exports requiring thousands of records at once
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Users without USDC on the Base network
Quick start
# 1. Send a POST to the endpoint — you'll get a 402 with payment challenge
curl -X POST https://lowpaymentfee.com/api/v1/employees/69/salary
# 2. Parse the 402 response, construct an x402 payment proof, then retry:
curl -X POST https://lowpaymentfee.com/api/v1/employees/69/salary \
-H "X-PAYMENT: <signed-payment-header>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 x402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs ('Connect wallet' only). The purpose of this specific employee salary endpoint is unclear — it may be demo/test data. Effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response fields
- —Unknown whether this returns real or synthetic/demo employee salary data
- —The endpoint path references a specific employee ID (69); unclear if other IDs are supported or what the data model looks like
Citations
- —Endpoint returns 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/employees/69/salary
- —Payment is 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network, equaling $0.02https://lowpaymentfee.com/api/v1/employees/69/salary
- —Provider advertises $0.02/request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs