Pay-per-call employee salary data endpoint on Base via x402 (USDC).
What it does
This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 167) when called via POST. It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, which spans data analytics, AI/ML inference, finance, and utility categories. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/employees/167/salary` costs $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled via the x402 `exact` scheme: callers include an `X-PAYMENT` header with a signed payment proof, and the server returns the requested data. No API keys, rate limits, or subscriptions are required — each call is independently paid.
Documentation on the site is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional 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 (returns a proper 402 challenge), but the actual data returned after payment is unknown. The employee ID 167 is hardcoded in the URL, and it is unclear whether other employee IDs are available or what the broader employee data model looks like.
Capabilities
Use cases
- —Retrieving salary information for employee ID 167 via a single paid API call
- —Demonstrating x402 payment protocol integration for pay-per-call data access
- —Building automated payroll or compensation analysis pipelines that settle per-request in USDC
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand salary data without API key management
- —Use cases requiring per-call crypto-settled data access
Not for
- —Bulk employee data retrieval (only one employee ID exposed in this endpoint)
- —Users without USDC on Base network
- —Anyone needing detailed API documentation or schema guarantees before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/167/salary \
-H "X-PAYMENT: <x402-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and no description of what data is actually returned. The docs pages are empty stubs. The endpoint path suggests employee salary data but nothing confirms the response structure or data quality.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content
- —No OpenAPI or output schema provided; response format is completely unknown
- —Only a single hardcoded employee ID (167) is exposed in this endpoint URL
- —No information on what salary fields are returned or data source/accuracy
- —The broader lowpaymentfee.com platform lists many endpoint categories but none match this employee/salary path, suggesting this may be a demo or test endpoint
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, on Base network using USDChttps://lowpaymentfee.com/api/v1/employees/167/salary
- —The maxAmountRequired is 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/employees/167/salary
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs