x402-gated premium API access on Base, paid per-call in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall. It is one of many endpoints offered by the lowpaymentfee.com platform, which hosts a variety of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities. All endpoints on the platform share a uniform pricing model of $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/stripe/charges/29` accepts POST requests and returns JSON. Its exact functionality is not documented beyond the label "Premium API Access" — the platform does not provide OpenAPI specs, detailed parameter documentation, or example responses for this particular route. The x402 challenge confirms the endpoint is live and accepts payment via the "exact" scheme on Base, with a max amount of 20,000 base units of USDC (i.e., $0.02 given USDC's 6 decimals). Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the asset contract is the canonical Base USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`).
The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /api, /README) all resolve to a minimal "Connect wallet" page with no substantive content. Without input/output schema details or usage examples, callers must experiment to discover what this endpoint actually does or returns.
Capabilities
Use cases
- —Programmatic pay-per-call access to a premium API without API key management
- —Agent-driven workflows that need to pay for API calls on-chain via x402
- —Exploring x402 payment protocol integrations on the Base network
Fit
Best for
- —Developers experimenting with x402 payment-gated APIs
- —Agents that settle API costs in USDC on Base
- —Use cases requiring keyless, per-request billing
Not for
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Applications requiring well-defined input/output schemas
- —High-volume use cases where $0.02/request adds up without volume discounts
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/29 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Example
Request
{
"url": "https://lowpaymentfee.com/api/v1/stripe/charges/29",
"body": {},
"method": "POST",
"headers": {
"X-PAYMENT": "<x402-payment-token>",
"Content-Type": "application/json"
}
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, there is no documentation, no OpenAPI schema, no example responses, and the endpoint's actual functionality beyond the label 'Premium API Access' is completely unknown. All doc pages return only 'Connect wallet' with no content.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README pages are all empty stubs showing only 'Connect wallet'.
- —The exact functionality of /api/v1/stripe/charges/29 is undocumented; the name suggests Stripe charge-related operations but this is unconfirmed.
- —No input or output schema is provided beyond the basic outputSchema stub in the x402 challenge.
- —The platform lists many API categories (AI, analytics, finance, etc.) but none have visible documentation.
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/stripe/charges/29
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/charges/29
- —Documentation pages (/docs, /pricing, /api, /README) resolve to minimal 'Connect wallet' contenthttps://lowpaymentfee.com/docs