x402basequality 0.30

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

What it does

This endpoint at `/api/v1/notifications/31` is part of the lowpaymentfee.com platform, which offers a broad catalog of pay-per-request APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints use the x402 payment protocol, settling in USDC on the Base network. The specific endpoint probed here is labeled "Premium API Access" and accepts POST requests.

The x402 challenge confirms the endpoint is live, requesting a maximum of 20,000 base units of USDC (asset `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). Since USDC uses 6 decimals, this translates to $0.02 per request — consistent with the site-wide pricing of $0.02/request advertised on the landing page. Payment is made via the `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a 300-second timeout.

Documentation is minimal: the landing page lists available API paths and pricing, but there is no OpenAPI spec, no request/response schema documentation, and no usage examples. The `/api`, `/pricing`, and `/README` pages all resolve to a "Connect wallet" prompt with no additional content. The exact functionality of the `/notifications/31` endpoint is unclear — the description is simply "Premium API Access" with no further detail on what notification data it returns or what input it expects. Because of this opacity, agents should treat this as a low-documentation endpoint where the actual behavior must be discovered empirically.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestnotifications-apipost-method

Use cases

  • —Retrieving notification data via a single paid POST request
  • —Programmatic access to notification resources without API keys or subscriptions
  • —Agent-driven workflows that need on-demand notification lookups with crypto micropayments

Fit

Best for

  • —Developers wanting keyless, pay-per-use API access settled in USDC on Base
  • —AI agents that can handle x402 payment challenges natively
  • —Users who prefer no-commitment, no-rate-limit API consumption

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume consumers who would benefit from bulk pricing or subscriptions
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no usage examples, and the actual functionality of '/notifications/31' is undocumented. The listing is effectively a stub with confirmed liveness and pricing.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —The exact purpose and expected input/output of /api/v1/notifications/31 is undocumented
  • —All non-root pages (/api, /pricing, /README) returned only a 'Connect wallet' prompt with no useful content
  • —No request body schema or response schema could be determined

Citations

Provenance

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

Agent access

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