x402basequality 0.30

x402-gated order status endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides order status information via a pay-per-request x402 protocol. The specific resource `/api/v1/orders/81/status` is gated behind an x402 payment challenge requiring USDC on the Base network. The cost per request is $0.02 (20,000 base units of USDC with 6 decimals). Payment is made inline via the X-PAYMENT header with no API keys or rate limits required.

The broader lowpaymentfee.com platform advertises a suite of endpoints spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request, settled in USDC on Base. The platform emphasizes simplicity: no API keys, no rate limits, no minimums, and instant access.

However, the specific endpoint being listed here (`/api/v1/orders/81/status`) appears to be an order status lookup for a particular order ID (81), which is a narrow resource. There is no OpenAPI schema, no documentation beyond the landing page, and no example request/response payloads available. The docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. The actual behavior and response format of this endpoint remain unknown.

Capabilities

x402-paymentusdc-settlementbase-networkorder-statuspay-per-requestno-api-keyno-rate-limit

Use cases

  • Checking the status of a specific order (ID 81) via programmatic pay-per-call access
  • Demonstrating x402 payment protocol integration for agent-to-API commerce
  • Building workflows that consume paid API endpoints without pre-registration

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing pay-per-call API access without API key management
  • Testing USDC micropayment flows on Base

Not for

  • Production order management systems (endpoint is scoped to a single order ID)
  • Users who need detailed API documentation or response schemas before integrating
  • High-volume batch processing where per-request pricing may add up

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge), but the resource is narrowly scoped to a single order ID with no documentation, no OpenAPI schema, no example responses, and no substantive content on any of the crawled pages beyond the landing page. The actual utility and response format are unknown.

Warnings

  • Endpoint is scoped to a single order ID (/api/v1/orders/81/status) — unclear if this is a demo or a real resource
  • No OpenAPI schema or response examples available
  • All documentation pages (docs, API, pricing, README) returned only 'Connect wallet' with no content
  • The broader platform lists many endpoints but none have documented schemas or examples
  • Cannot verify what data this endpoint actually returns

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 06:19:53Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access