x402-gated employee data endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to an employee record (ID 153) via the x402 payment protocol. It is part of a broader suite of pay-per-request APIs offered by lowpaymentfee.com, which spans data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints on the platform share a uniform $0.02 per-request pricing model, settled in USDC on the Base network.
The specific endpoint `/api/v1/employees/153` returns JSON (mimeType: application/json) and accepts POST requests. Payment is handled via the x402 protocol: callers receive a 402 challenge containing payment parameters, then submit a signed USDC payment (maxAmountRequired of 20,000 base units = $0.02 given USDC's 6 decimals) in the X-PAYMENT header. The payTo address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the accepted asset is USDC at contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no description of request/response fields, and no examples of what the employee data payload looks like. The endpoint is confirmed live (402 challenge captured), but the actual data returned after payment is unknown.
Capabilities
Use cases
- —Retrieving employee record data for ID 153 via a single paid API call
- —Demonstrating x402 payment protocol integration with USDC on Base
- —Building agent workflows that purchase data on-demand without API keys
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents that need keyless, pay-per-request data access
- —Projects already using USDC on Base for micropayments
Not for
- —Bulk employee data retrieval (single-record endpoint, no batch support evident)
- —Users who need detailed API documentation or guaranteed SLAs
- —Anyone without a Base-compatible wallet and USDC balance
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/employees/153
# Returns 402 with x402 challenge. Include signed payment in X-PAYMENT header:
# curl -X POST https://lowpaymentfee.com/api/v1/employees/153 -H 'X-PAYMENT: <signed_payment>'Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and no description of what employee data is actually returned. The docs pages are empty. This is effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, and API pages all show only 'Connect wallet' with no content
- —No OpenAPI or schema describing request parameters or response fields
- —Unknown what data the employee record actually contains
- —Single hardcoded employee ID (153) — unclear if other IDs are supported or what the broader employees API looks like
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/employees/153
- —All endpoints on the platform are priced at $0.02 per requesthttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/employees/153
- —Platform offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com