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 employee salary information for a specific employee (ID 160) 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 requires no API keys, no rate limits, and offers instant access — callers simply attach an x402 payment header to each request.
The provider (lowpaymentfee.com) hosts a broader catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/employees/160/salary` endpoint. No OpenAPI schema, request body specification, or response examples are documented in the crawled material, so the exact input parameters and output format are unknown. The endpoint is confirmed live: it returns a proper x402 402 challenge with version 1, advertising the USDC asset on Base with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals).
Capabilities
Use cases
- —Retrieving salary information for employee records
- —Integrating employee compensation data into payroll or HR dashboards
- —Agent-driven lookups of salary data with automatic micropayment settlement
Fit
Best for
- —Developers needing on-demand salary data without subscription commitments
- —AI agents that can settle x402 payments autonomously on Base
- —Applications requiring low-friction, keyless API access to employee data
Not for
- —Bulk export of salary data for large employee populations (single-employee endpoint)
- —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/160/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI schema, no documented request/response format, no examples, and the crawled docs pages are empty stubs. The purpose of the endpoint (employee salary for ID 160) is only inferable from the URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or request/response schema available — input parameters and output format are unknown.
- —Documentation pages (/docs, /api, /pricing, /README) returned no meaningful content beyond a 'Connect wallet' prompt.
- —The endpoint is hardcoded to a single employee ID (160); unclear if other employee IDs are supported or how to discover them.
- —The nature and source of the salary data is undocumented — could be mock/demo data.
Citations
- —Endpoint returns a 402 x402 challenge with USDC on Base, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/160/salary
- —Provider advertises $0.02 per request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/employees/160/salary