x402-gated premium API access on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" via the x402 payment protocol on the Base network. The specific resource at `/api/v1/benefits/91` is one of many endpoints offered by the provider, which spans categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities. All endpoints are priced at $0.02 per request (20,000 base units of USDC with 6 decimals), settled on-chain via Base using USDC (contract 0x8335…2913).
The endpoint accepts POST requests and returns application/json responses. Payment is handled through the x402 protocol: callers receive a 402 challenge with payment details, submit an X-PAYMENT header with a signed transaction, and receive the API response upon settlement. There are no API keys, no rate limits, and no upfront commitments — access is purely pay-per-call.
However, the specific functionality of `/api/v1/benefits/91` is unclear. The provider's landing page lists numerous categorized endpoints (analytics, AI, finance, utilities), but this particular path does not appear in any of those categories. The description field in the x402 challenge simply reads "Premium API Access" with no further detail on what data or computation is returned. Documentation pages (docs, pricing, README) all rendered as minimal "Connect wallet" stubs with no additional content.
Capabilities
Use cases
- —Programmatic access to a premium API resource with per-request USDC micropayments
- —Agent-driven workflows that need keyless, on-demand API access settled on Base
- —Testing x402 payment protocol integrations against a live endpoint
Fit
Best for
- —Developers experimenting with x402 payment flows
- —Agents that need keyless pay-per-call API access on Base
- —Low-volume consumers who want no subscription commitments
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —High-volume use cases where per-request on-chain settlement adds latency or cost overhead
- —Anyone needing to understand the exact response payload before paying
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/benefits/91
# Returns 402 with x402 challenge. Include X-PAYMENT header with signed USDC payment on Base to access.Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but the actual functionality of /api/v1/benefits/91 is undocumented. No OpenAPI schema, no example request/response, and all doc pages are empty stubs. The listing is effectively a stub with known payment terms but unknown utility.
Warnings
- —The specific functionality of /api/v1/benefits/91 is not documented anywhere in the crawled material — it does not appear in the provider's listed API categories.
- —All documentation pages (/docs, /pricing, /README, /api) returned only 'Connect wallet' with no substantive content.
- —No request or response schema is available; callers cannot know what to send or what they will receive before paying.
- —The provider lists many endpoint categories (AI, analytics, finance, utilities) but this specific path ('benefits/91') doesn't match any of them.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/benefits/91
- —All endpoints are priced at $0.02 per request 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/benefits/91
- —Documentation pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs