x402basequality 0.30

x402-gated premium API access on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall on the Base network. The provider operates a suite of pay-per-call APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.

The specific endpoint `/api/v1/benefits/28` is listed as "Premium API Access" and accepts POST requests. Payment is settled in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on the Base L2 network using the x402 exact payment scheme. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a timeout of 300 seconds.

However, the exact functionality behind the `/api/v1/benefits/28` path is not documented in the crawled material. The provider's landing page lists many other endpoints (analytics, AI, finance, utilities) but does not describe what "benefits/28" specifically returns. The docs, pricing, and API pages all rendered only a "Connect wallet" prompt with no additional documentation. Without clearer documentation, agents should treat this as an opaque premium endpoint whose response schema is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestpost-methodno-api-keyjson-response

Use cases

  • Accessing premium data or services behind a per-request paywall
  • Agent-driven API consumption with automatic USDC micropayments on Base
  • Integrating pay-as-you-go endpoints without managing API keys or subscriptions

Fit

Best for

  • AI agents that can settle x402 payments in USDC on Base
  • Developers wanting zero-commitment, per-request API access
  • Applications needing keyless, rate-limit-free API calls

Not for

  • Users who need detailed documentation or a well-defined response schema before integrating
  • Applications that cannot settle USDC payments on the Base network
  • High-volume use cases where per-request pricing may be inefficient compared to subscription models

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/benefits/28 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-header>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, the specific functionality of /api/v1/benefits/28 is entirely undocumented — no request schema, no response schema, no description beyond the generic 'Premium API Access' label. The docs/pricing/API pages are empty (wallet-connect only). This is effectively a stub listing.

Warnings

  • The exact purpose and response format of /api/v1/benefits/28 is undocumented; the 'Premium API Access' label is generic.
  • All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' prompt with no usable content.
  • No OpenAPI spec, no request/response schema, and no examples are available.
  • The endpoint path '/api/v1/benefits/28' does not appear in the provider's listed API catalog on the landing page.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 16:37:17Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access