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

The x402 challenge confirms the endpoint is live and accepts exact-scheme payments to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The maxAmountRequired is 20000 base units, which equals $0.02 (USDC uses 6 decimals). No API keys are needed; access is granted immediately upon payment. The platform advertises no rate limits and no minimum commitments.

Note that this specific endpoint path (/api/v1/orders/54/status) is not listed among the publicly advertised APIs on the landing page, which focus on analytics, AI, finance, and utility categories. It may be a demo or internal order-tracking endpoint. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the request/response schema for this endpoint is unknown beyond the x402 outputSchema indicating it accepts HTTP POST and returns application/json.

Capabilities

x402-paymentusdc-basepay-per-callorder-statusjson-apino-api-key

Use cases

  • Checking the status of a specific order programmatically via micropayment
  • Demonstrating x402 payment-gated API access on Base
  • Integrating pay-per-call order lookups into agent workflows

Fit

Best for

  • Developers exploring x402 protocol integrations
  • Agents that need on-demand order status without API key management
  • Micropayment-based API consumption on Base L2

Not for

  • Bulk order status polling (each call costs $0.02)
  • Users who need detailed API documentation before integrating
  • Production order management systems requiring authenticated sessions

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, and the specific order-status path is not listed among the provider's advertised APIs. All doc pages returned only 'Connect wallet' with no content.

Warnings

  • This specific endpoint (/api/v1/orders/54/status) is not listed among the provider's publicly advertised APIs — it may be a demo or internal endpoint.
  • No documentation is available: /docs, /pricing, /api, and /README all return only a 'Connect wallet' prompt with no substantive content.
  • Request body schema and response schema are completely unknown — no OpenAPI spec or examples are provided.
  • The endpoint path is hardcoded to order ID 54; it is unclear whether other order IDs are supported or how to parameterize.

Citations

Provenance

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

Agent access