Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 159) when called via POST. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/employees/159/salary` charges up to $0.02 per request (maxAmountRequired of 20,000 base units of USDC, which has 6 decimals = $0.02). Payment is made via the x402 `exact` scheme, meaning the caller includes a cryptographic payment proof in the X-PAYMENT header with each request. No API keys, rate limits, or upfront commitments are required — access is instant once payment is attached.
The platform's documentation pages (docs, pricing, README) appear to be behind a wallet-connect gate and contain no substantive content in the crawl. As a result, the exact response schema for this salary endpoint is unknown. The endpoint is confirmed live, returning a proper 402 challenge with x402 version 1. The response MIME type is application/json.
Capabilities
Use cases
- —Retrieving salary information for employee records
- —Integrating payroll data into HR dashboards without API key management
- —Agent-driven compensation benchmarking workflows
Fit
Best for
- —Developers wanting keyless, pay-per-call access to salary data
- —AI agents that can settle micropayments in USDC on Base
- —Prototyping HR data integrations without subscription commitments
Not for
- —Bulk payroll data exports (single-employee endpoint, no batch mode evident)
- —Users without USDC on Base network
- —Anyone needing detailed API documentation before integrating (docs are sparse)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/159/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 OpenAPI schema, no response examples, and all documentation pages are gated behind wallet-connect with no readable content. The endpoint path suggests employee salary data but the actual response structure is unknown. This is effectively a stub listing.
Warnings
- —No OpenAPI or response schema available — the exact fields returned are unknown.
- —All documentation pages (docs, pricing, README) are behind a wallet-connect gate and returned no useful content.
- —The endpoint is scoped to a single employee ID (159); it is unclear whether other employee IDs are supported or how to discover them.
- —The 'Premium API Access' title/description from the provider is generic and does not describe what this specific endpoint does.
Citations
- —The endpoint returns a 402 challenge with x402 version 1, exact scheme, on Base network, paying in USDC (asset 0x8335...)https://lowpaymentfee.com/api/v1/employees/159/salary
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals) = $0.02 per requesthttps://lowpaymentfee.com/api/v1/employees/159/salary
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com