x402basequality 0.30

Pay-per-call notification endpoint on Base via x402 — $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/notifications/17` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific endpoint listed here is described as "Premium API Access" and sits under a notifications path, though no further documentation clarifies what notification data or functionality it provides.

Pricing is $0.02 per request (maxAmountRequired of 20,000 base units of USDC with 6 decimals = $0.02). There are no API keys, no rate limits, and no minimum commitments — callers simply attach an x402 payment header with each request. The endpoint accepts POST requests and returns application/json responses. The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base mainnet using the USDC contract at `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`.

Note that the exact request schema (what parameters to send) and response schema (what data is returned) are not documented anywhere in the crawled material. The endpoint is live and returns a proper 402 challenge, but without documentation on the notification resource or its expected input/output, callers will need to experiment or contact the provider for details.

Capabilities

x402-paymentusdc-basepay-per-requestnotificationsjson-apino-api-key

Use cases

  • Sending or retrieving notification data via a single paid API call
  • Integrating pay-per-use notification services into agent workflows
  • Testing x402 payment protocol integrations with a low-cost endpoint

Fit

Best for

  • Developers experimenting with x402 payment-gated APIs
  • Agents needing simple per-call notification access without API keys
  • Low-volume consumers who want no subscription commitment

Not for

  • Users who need detailed API documentation before integrating
  • High-volume notification pipelines where per-call pricing adds up
  • Anyone requiring guaranteed SLAs or support contracts

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/notifications/17 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is zero documentation on what this specific notifications/17 endpoint does, what request body it expects, or what it returns. The crawled pages only show a generic listing of other endpoints and provide no schema, examples, or explanation for this resource.

Warnings

  • No documentation exists for the /api/v1/notifications/17 endpoint — its purpose and expected input/output are unknown.
  • No OpenAPI spec, request schema, or response schema is available.
  • The 'Premium API Access' description is generic and does not clarify functionality.
  • Other pages on the site (pricing, README, api) returned only 'Connect wallet' with no useful content.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 00:31:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access