x402basequality 0.35

Pay-per-call notification endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a "Premium API Access" notification resource at `/api/v1/notifications/72`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network via the x402 protocol.

The specific `/api/v1/notifications/72` endpoint accepts POST requests and returns `application/json`. Payment is handled inline: callers attach an `X-PAYMENT` header containing a signed x402 payment for up to 20,000 base units of USDC (i.e., $0.02) to the payee address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. No API keys, accounts, or rate limits are advertised — access is gated purely by micropayment.

Because the endpoint path includes a numeric ID (`/72`), it likely addresses a specific notification resource, but no further documentation or schema details are available beyond the x402 challenge and the landing page. The platform's other listed endpoints (sentiment analysis, text summarization, price feeds, geocoding, etc.) follow the same pricing and payment model. Without deeper docs or an OpenAPI spec, the exact request body format and response shape for this particular endpoint remain unknown.

Capabilities

x402-paymentusdc-basepay-per-callnotification-apijson-responseno-api-keyno-rate-limit

Use cases

  • Triggering or retrieving a specific notification via a single paid API call
  • Integrating pay-per-use notification delivery into agent workflows
  • Demonstrating x402 micropayment flows on the Base network

Fit

Best for

  • Agents that need simple, keyless API access gated by micropayment
  • Developers experimenting with x402 payment protocol on Base
  • Low-volume, on-demand notification retrieval without subscription commitments

Not for

  • High-volume notification streaming where per-call fees add up quickly
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Users without a Base-network USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page listing, and the purpose of the /notifications/72 resource is unexplained. Effectively a stub listing.

Warnings

  • No OpenAPI or schema documentation available — request body format and response shape are unknown
  • The specific purpose of /api/v1/notifications/72 is undocumented; the numeric ID suggests a resource-specific endpoint but details are absent
  • Landing page lists many endpoints but /api and /pricing pages only show 'Connect wallet' with no further content
  • No SLA, rate-limit, or uptime guarantees documented

Citations

Provenance

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

Agent access