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
Endpoint
https://lowpaymentfee.com/api/v1/notifications/59

What it does

This endpoint at `/api/v1/notifications/59` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs settled via the x402 protocol on the Base network using USDC. The specific endpoint is labeled "Premium API Access" and accepts POST requests. Payment is 20,000 base units of USDC (6 decimals), which equals $0.02 per call. No API keys or rate limits are advertised; callers pay per request with an x402 payment header.

The broader lowpaymentfee.com platform lists endpoints across several categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request. However, this particular endpoint (`/api/v1/notifications/59`) is not listed on the homepage's catalog, and its exact functionality beyond the generic "Premium API Access" label is unclear. The path suggests it relates to notifications (possibly retrieving or triggering a specific notification resource with ID 59), but no documentation, request schema, or response schema is available to confirm this.

The endpoint is live: it returns a well-formed 402 challenge with x402 version 1, settling on Base to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the canonical Base USDC contract (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum timeout is 300 seconds. No OpenAPI spec, AI plugin manifest, or detailed documentation was found during crawling.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestnotificationspost-endpoint

Use cases

  • —Triggering or retrieving notifications via a paid API call
  • —Integrating pay-per-use notification delivery into agent workflows
  • —Testing x402 payment flows with a low-cost endpoint

Fit

Best for

  • —Agents needing a simple pay-per-call notification endpoint
  • —Developers experimenting with x402 protocol on Base
  • —Low-cost API access without API key management

Not for

  • —Use cases requiring detailed documentation or guaranteed SLAs
  • —High-volume notification delivery where per-call pricing is impractical
  • —Users who need to understand the exact notification payload before paying

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/notifications/59
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the specific purpose of /api/v1/notifications/59 is unknown. The endpoint does not appear in the provider's own homepage catalog, making it effectively a stub listing.

Warnings

  • —No documentation or schema available for this specific endpoint
  • —Endpoint /api/v1/notifications/59 is not listed on the provider's homepage catalog — its exact functionality is unclear
  • —No example request or response bodies available
  • —The /pricing, /api, and /README pages returned only a 'Connect wallet' prompt with no useful content

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/5xAjh8
Pay-per-call notification endpoint on Base via x402 — $0.02 per request in USDC. — Clawmart · Clawmart