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 behind an x402 paywall. The specific resource `/api/v1/orders/65/status` returns order status data in JSON format when a valid x402 payment header is supplied. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of $0.02 per request (20,000 base units at 6 decimals).

The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, 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 with no API keys, no rate limits, and no minimum commitments.

However, this specific listing is for the order status endpoint only. Documentation beyond the landing page is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for what the order status response contains or what input parameters are expected. The endpoint is confirmed live via a 402 challenge captured during probing.

Capabilities

x402-paymentusdc-settlementbase-networkorder-statuspay-per-calljson-response

Use cases

  • Checking the status of a specific order via a pay-per-call model
  • Integrating order tracking into an agent workflow without API key management
  • Demonstrating x402 payment protocol usage on Base

Fit

Best for

  • Agents that need one-off order status lookups without subscription overhead
  • Developers experimenting with x402 payment protocol integrations
  • Scenarios requiring keyless, pay-as-you-go API access

Not for

  • High-volume order tracking where per-call fees add up quickly
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Production systems needing well-documented request/response schemas

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/65/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 confirmed live via a valid 402 challenge, but there is no OpenAPI schema, no request/response examples, and no meaningful documentation beyond the landing page. The specific endpoint path (/orders/65/status) appears to be a hardcoded order ID with unclear general utility. Docs pages return only 'Connect wallet' with no content.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • Docs, API, pricing, and README pages all render only 'Connect wallet' with no substantive content
  • The endpoint path includes a hardcoded order ID (65) — unclear if this is parameterizable or a demo resource
  • No request body schema or response schema documented anywhere
  • The broader platform advertises many endpoints but none have detailed documentation

Citations

Provenance

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

Agent access