x402basequality 0.30

Check order status via x402 micropayment on Base network for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com returns the status of order #146 via a POST request, gated by the x402 payment protocol. It is part of a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance/Web3, and infrastructure utility categories — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/146/status` is labeled "Premium API Access" in the x402 challenge. The payment scheme is "exact" with a maxAmountRequired of 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base, 6 decimals), which equals $0.02. Payment is made by including an X-PAYMENT header with the x402 payment proof. No API keys, rate limits, or subscriptions are required — each call is independently settled on-chain.

Documentation beyond the landing page is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns HTTP 402 with a valid x402 challenge), but the actual response format after successful payment is unknown.

Capabilities

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

Use cases

  • Checking the status of a specific order (#146) programmatically
  • Demonstrating x402 payment-gated API access patterns
  • Agent-driven order tracking with on-chain micropayments

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need to make small on-chain payments for API access
  • Projects already operating on the Base L2 network with USDC

Not for

  • Production order management systems (endpoint is hardcoded to order 146)
  • Users who need detailed API documentation or OpenAPI specs before integrating
  • High-volume use cases where per-request on-chain settlement adds latency

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — no request/response schemas, no examples, and the endpoint is hardcoded to a single order ID. The broader platform lists many endpoints but provides no docs for any of them.

Warnings

  • Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no technical content
  • No OpenAPI spec or request/response schema available
  • Endpoint is hardcoded to order ID 146 — unclear if this is a demo or a real resource
  • No information about what the response body looks like after successful payment
  • The broader platform advertises many endpoints but none have documented schemas

Citations

Provenance

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

Agent access