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 165) 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 no upfront commitments — 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 and all using the same x402 payment flow on Base. This particular endpoint (/api/v1/employees/165/salary) appears to serve structured JSON salary information for a single employee record. However, no OpenAPI schema, request body specification, or example 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. The payment is routed to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the USDC contract on Base (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum timeout for payment settlement is 300 seconds.
Capabilities
Use cases
- —Retrieving salary information for employee records on demand
- —Integrating pay-per-call salary data into payroll or HR dashboards
- —Agent-driven lookups of compensation data without managing API keys
Fit
Best for
- —Developers needing on-demand salary data without subscription commitments
- —AI agents that can settle micropayments via x402 on Base
- —Prototyping pay-per-call data access patterns with USDC
Not for
- —Bulk salary data exports requiring thousands of records at once
- —Users who cannot transact in USDC on the Base network
- —Production HR systems needing guaranteed SLAs and documented schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/165/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 example payloads, and the docs pages are essentially empty ('Connect wallet'). The purpose of the endpoint (employee salary data) is only inferable from the URL path. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —Documentation pages (/docs, /api, /pricing, /README) return no meaningful content
- —The endpoint path references a hardcoded employee ID (165); it is unclear if other IDs are supported or how to discover them
- —The nature of the 'salary' data is unverified — it may be demo/synthetic data
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/employees/165/salary
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/165/salary