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 via a simple POST request. The specific resource `/api/v1/employees/50/salary` returns salary information for employee ID 50 in JSON format. Payment is handled inline using the x402 protocol on the Base network, settling in USDC (contract 0x8335…2913) with no API keys, accounts, or rate limits required.
The endpoint charges a maximum of 0.02 USDC per request (20,000 base units with 6 decimals), consistent with the provider's flat $0.02/request pricing across all their APIs. The provider, lowpaymentfee.com, hosts a broader catalog of endpoints spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). All endpoints share the same pricing model and x402 payment flow.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the salary endpoint actually returns. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know the exact request format or response structure beyond what the x402 challenge advertises.
Capabilities
Use cases
- —Retrieving employee salary information programmatically
- —Integrating salary data into payroll or HR dashboards
- —Agent-driven lookups of compensation data with instant micropayment
Fit
Best for
- —Developers needing quick, keyless access to salary data
- —AI agents that can settle x402 payments on Base
- —Projects wanting pay-per-use data without subscriptions
Not for
- —Bulk data exports requiring thousands of records at once (no documented batch endpoint)
- —Users who need detailed API documentation or SDKs before integrating
- —Anyone unable to pay with USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/50/salary \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI schema, no request/response examples, and all documentation pages are empty beyond a wallet-connect prompt. The purpose of the specific employee salary endpoint is only inferable from the URL path. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages are empty
- —No request or response schema provided; request body format is unknown
- —The endpoint path suggests demo/sample data (employee ID 50) rather than a production data source
- —Provider hosts many endpoints but none have documented schemas or examples
Citations
- —Endpoint returns a 402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/employees/50/salary
- —Provider charges $0.02 per request across all APIs with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/employees/50/salary