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 103) 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 to 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 appears to serve structured JSON containing salary information for a given employee resource. However, no OpenAPI schema, request body specification, or sample response is documented, so the exact input parameters and response shape are unknown.
The endpoint is live and returns a valid x402 challenge (HTTP 402) with version 1 of the protocol. 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 in a pay-per-call model
- —Integrating employee compensation data into HR or payroll workflows
- —Agent-driven lookups of salary data without managing API keys or subscriptions
Fit
Best for
- —Developers needing on-demand employee salary data without subscription commitments
- —AI agents that can settle x402 micropayments on Base
- —Prototyping pay-per-use data access patterns with USDC
Not for
- —Bulk payroll data exports requiring thousands of records at once
- —Users who cannot transact on the Base L2 network or hold USDC
- —Production HR systems that need guaranteed SLAs and documented schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/103/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 schema, no documented request/response format, no sample payloads, and the docs/pricing/README pages all render only a wallet-connect prompt. The endpoint's actual behavior and data shape are entirely unknown beyond the resource URL pattern.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —Docs, pricing, and README pages return only a 'Connect wallet' prompt with no useful content
- —The specific endpoint path (/employees/103/salary) suggests demo or sample data; unclear if other employee IDs are supported
- —No SLA, rate limit, or uptime guarantees documented
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge on POSThttps://lowpaymentfee.com/api/v1/employees/103/salary
- —Payment is 20000 base units of USDC (6 decimals = $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/employees/103/salary
- —Site advertises $0.02/request pricing with no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/employees/103/salary