Pay-per-call employee salary data endpoint on Base via x402 (USDC).
What it does
This x402-enabled endpoint at lowpaymentfee.com returns employee salary data for a specific employee (ID 137) via a POST request. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.
The endpoint charges a maximum of $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled inline via the x402 protocol: callers receive a 402 challenge with payment parameters, construct a signed USDC payment on Base, and attach it in the X-PAYMENT header. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-use.
The specific resource path (`/api/v1/employees/137/salary`) suggests it returns salary information for employee record 137. However, no OpenAPI schema, request body specification, or example response is available in the crawled documentation. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional technical detail. The endpoint is confirmed live (returns a well-formed x402 challenge), but the actual data returned after payment is undocumented.
Capabilities
Use cases
- —Retrieving salary data for a specific employee record via automated agent
- —Demonstrating x402 pay-per-call protocol integration on Base
- —Building payroll or HR data pipelines that settle per-request in USDC
Fit
Best for
- —Developers experimenting with x402 micropayment protocol
- —Agents needing on-demand employee salary lookups without API key management
- —Low-volume, pay-as-you-go data access on Base L2
Not for
- —Bulk payroll data exports (single-employee endpoint, no batch support documented)
- —Users without a Base-compatible USDC wallet
- —Anyone needing detailed API documentation or response schema guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/137/salary
# Returns 402 with x402 challenge. Attach signed USDC payment in X-PAYMENT header to receive data.Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documented request/response format, and the docs pages are empty beyond a wallet-connect prompt. The specific data returned (employee salary) is only inferred from the URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or request/response schema available — actual payload structure is unknown
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no technical content
- —The endpoint path references a hardcoded employee ID (137); it is unclear if other IDs are supported or what the broader API surface looks like
- —The 'Premium API Access' title/description from the provider is generic and does not describe the actual data returned
Citations
- —Endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/employees/137/salary
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/137/salary