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 data for a specific employee (ID 164) 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 provides instant access — callers simply attach an x402 payment header with each request.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. This particular endpoint sits under an employees/salary path, suggesting it returns compensation or payroll-related information for the given employee record. However, no OpenAPI schema, request body specification, or sample response is documented, so the exact input parameters and output fields are unknown.
The endpoint is live and returns a valid x402 challenge (HTTP 402) with x402Version 1, confirming it is operational. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base. The maximum payment timeout is 300 seconds.
Capabilities
Use cases
- —Retrieving salary information for a specific employee record
- —Integrating pay-per-call employee compensation data into HR dashboards
- —Agent-driven payroll data lookups without API key management
Fit
Best for
- —Agents needing on-demand employee salary data with no subscription
- —Developers prototyping x402 payment flows on Base
- —Applications requiring keyless, pay-as-you-go data access
Not for
- —Bulk payroll data exports across many employees (single-employee endpoint)
- —Users who need detailed API documentation or schema guarantees before integrating
- —Applications requiring non-crypto payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/164/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documented request/response format, no sample data, and the crawled docs pages are empty stubs. The purpose of the endpoint (employee salary for ID 164) 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
- —The endpoint path references a hardcoded employee ID (164); unclear if other IDs are supported or how to discover them
- —The nature of the 'employee salary' data is unverified — it may be demo/synthetic data
Citations
- —Endpoint returns HTTP 402 with x402 challenge on POST, confirming it is livehttps://lowpaymentfee.com/api/v1/employees/164/salary
- —Price is $0.02 per request, paid in USDC on Base networkhttps://lowpaymentfee.com
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/employees/164/salary
- —No API keys, no rate limits, instant access advertisedhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/164/salary