x402basequality 0.30

Order status lookup via x402 micropayment on Base network, $0.02 per request in 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/37/status` returns order status data in JSON format when called via POST with a valid X-PAYMENT header. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of $0.02 per request (20,000 base units with 6 decimals).

The provider, lowpaymentfee.com, operates a broader platform offering multiple x402-gated API categories including data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced uniformly at $0.02 per request with no API keys, no rate limits, and no minimum commitments required. The platform uses the x402 protocol version 1 with the "exact" payment scheme.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the order status response contains. The endpoint path suggests it retrieves status for a specific order (ID 37), but it is unclear whether this is a demo/sample order or whether callers can query arbitrary order IDs via different paths.

Capabilities

x402-paymentusdc-base-networkorder-statusjson-responseper-request-micropaymentno-api-key

Use cases

  • Checking the status of a specific order via a single paid API call
  • Demonstrating x402 protocol micropayment integration on Base
  • Agent-driven order tracking workflows that pay per query

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing pay-per-call order status lookups
  • Low-friction API access without API key management

Not for

  • Bulk order status monitoring (no documented batch endpoint)
  • Users who need detailed API documentation or response schema guarantees
  • Production systems requiring SLA or uptime guarantees

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/37/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 402 with a valid x402 challenge), but documentation is essentially nonexistent — docs/pricing/API pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the specific endpoint path (/orders/37/status) is not listed on the homepage. The purpose and response format must be entirely inferred from the URL path.

Warnings

  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no usable content.
  • No OpenAPI or response schema available — response format is unknown.
  • The endpoint path references a hardcoded order ID (37); it is unclear if this is a demo or if other order IDs are queryable.
  • The specific /orders/37/status endpoint is not listed among the provider's advertised APIs on the homepage.

Citations

Provenance

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

Agent access