x402basequality 0.35

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 lowpaymentfee.com provides a "Premium API Access" notification resource at `/api/v1/notifications/24`, payable per request using the x402 protocol. Payment is settled in USDC on the Base network at $0.02 per call (20,000 base units with 6 decimals). No API keys, rate limits, or upfront commitments are required — callers simply attach an x402 payment header to each POST request.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs across categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. The specific functionality of the `/api/v1/notifications/24` endpoint is not documented beyond the label "Premium API Access"; it likely delivers or triggers a notification resource identified by ID 24, but the exact request/response schema is not published.

The x402 challenge was successfully captured (HTTP 402 with a valid accepts block), confirming the endpoint is live. The payment is routed to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The maximum timeout for payment settlement is 300 seconds.

Capabilities

x402-paymentper-call-billingusdc-basenotificationspost-endpointno-api-key

Use cases

  • Triggering or retrieving a notification resource via a single paid API call
  • Integrating pay-per-use notification delivery into agent workflows
  • Testing x402 micropayment flows against a live endpoint

Fit

Best for

  • Agents needing simple pay-per-call notification access without API keys
  • Developers experimenting with x402 protocol integrations on Base
  • Low-volume, on-demand notification retrieval

Not for

  • High-volume notification streaming where per-call pricing is inefficient
  • Users who need detailed API documentation or OpenAPI schemas before integrating
  • Non-crypto workflows that cannot settle payments in USDC on Base

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no documented request/response format, and the specific purpose of the /notifications/24 endpoint is unexplained. Effectively a stub listing.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • The exact functionality of /api/v1/notifications/24 is undocumented — 'Premium API Access' is the only label
  • No example request or response bodies are published
  • The /api, /pricing, and /README pages all returned only a 'Connect wallet' prompt with no useful content

Citations

Provenance

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

Agent access