x402basequality 0.35

Check order status 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 returns the status of order #143 via a POST request, gated by an x402 payment challenge. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.

The specific resource `/api/v1/orders/143/status` accepts POST requests and requires an X-PAYMENT header carrying a valid x402 payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api, /README) all resolve but render only a "Connect wallet" prompt with no substantive content, so the actual response schema and detailed behavior of this endpoint are unknown. The endpoint is live and returning a well-formed x402 v1 challenge.

Capabilities

x402-paymentusdc-baseorder-statuspay-per-requestno-api-key

Use cases

  • Checking the fulfillment or processing status of a specific order programmatically
  • Demonstrating x402 payment-gated API access on the Base L2 network
  • Integrating pay-per-call order tracking into an agent workflow without API key management

Fit

Best for

  • Developers experimenting with x402 protocol micropayments
  • Agents that need on-demand order status checks without subscription overhead
  • Projects already holding USDC on Base looking for frictionless API access

Not for

  • Bulk order-status polling (no documented batch endpoint; per-call cost adds up)
  • Users without a Base-network USDC wallet
  • Anyone needing detailed API documentation or guaranteed SLAs (docs are essentially empty)

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but the specific resource (/orders/143/status) is a single hardcoded order ID with no documented request or response schema. All documentation pages render only a wallet-connect prompt. No OpenAPI spec, no examples, and no description of what the response contains.

Warnings

  • All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no actual content.
  • The endpoint path references a specific order ID (143); it is unclear whether this is a demo or a general-purpose endpoint.
  • No response schema or example response is available — the actual payload returned after payment is unknown.
  • No OpenAPI or machine-readable spec is published.

Citations

Provenance

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

Agent access