Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to employee salary data (specifically employee ID 149) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint returns JSON and requires no API keys, rate limits, or upfront commitments — callers simply attach an x402 payment header to each request.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, the specific endpoint being listed here — `/api/v1/employees/149/salary` — is not documented on the provider's landing page among the advertised API categories. Its purpose appears to be returning salary information for a specific employee record, but no schema documentation, example responses, or detailed descriptions are available beyond the x402 challenge metadata.
The endpoint is confirmed live: it returns a proper HTTP 402 challenge with x402 version 1, advertising payment to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC on Base. The maximum amount required is 20,000 base units (i.e., $0.02 given USDC's 6 decimals). Timeout is 300 seconds. No OpenAPI spec, request body schema, or response schema is published.
Capabilities
Use cases
- —Retrieving salary information for a specific employee record
- —Integrating employee compensation data into payroll or HR workflows
- —Agent-driven lookups of salary data without API key provisioning
Fit
Best for
- —Developers needing quick, keyless access to employee salary data
- —AI agents that can settle micropayments on Base via x402
- —Prototyping pay-per-call data retrieval without subscription overhead
Not for
- —Bulk payroll data exports across many employees (only one employee ID exposed)
- —Users who cannot transact in USDC on the Base network
- —Production HR systems requiring documented schemas and SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/149/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation for this specific endpoint, and it is not listed among the provider's advertised APIs. The purpose and data returned are unclear beyond the URL path.
Warnings
- —This specific endpoint (/api/v1/employees/149/salary) is not listed among the provider's advertised APIs on the landing page
- —No request body schema or response schema is documented anywhere
- —No example responses available — the data format returned is unknown
- —The endpoint appears to serve data for a single hardcoded employee ID (149); generalizability is unclear
- —Docs, pricing, API, and README pages all render only a 'Connect wallet' prompt with no substantive content
Citations
- —The endpoint returns HTTP 402 with x402 version 1 challenge advertising USDC payment on Basehttps://lowpaymentfee.com/api/v1/employees/149/salary
- —maxAmountRequired is 20000 base units of USDC (6 decimals), equaling $0.02https://lowpaymentfee.com/api/v1/employees/149/salary
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —This specific employee salary endpoint is not listed among the provider's advertised API categorieshttps://lowpaymentfee.com