x402basequality 0.30

Order status lookup via x402 micropayment on Base (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides order status information for a specific order (order ID 38) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/38/status` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The x402 challenge confirms the endpoint is live, requesting up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 on Base. The payment scheme is "exact" with a 300-second timeout.

Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no usage examples. The endpoint path suggests it returns the status of a particular order, but the actual response format and the meaning of "order" in this context are unknown. The broader platform advertises no API keys, no rate limits, and instant access.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-callmicropayment

Use cases

  • Checking the status of an order via a single micropayment call
  • Integrating pay-per-request order lookups into agent workflows
  • Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • Agents needing on-demand order status without API key registration
  • Developers experimenting with x402 micropayment protocols
  • Low-volume, pay-as-you-go API consumption

Not for

  • High-volume order management requiring bulk queries or subscriptions
  • Users who need detailed API documentation or guaranteed SLAs
  • General-purpose order tracking across multiple order IDs (this endpoint is hardcoded to order 38)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documented request/response schema, no examples, and the endpoint is scoped to a single hardcoded order ID (38). Documentation pages return only a wallet-connect prompt with no useful content.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown.
  • Endpoint path is hardcoded to order ID 38; unclear if other order IDs are supported or how to discover them.
  • All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no substantive content.
  • The broader platform advertises many endpoints but none have documented schemas or examples.

Citations

Provenance

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

Agent access