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 #155 via a POST request, gated behind 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 and settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/155/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 (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which uses 6 decimals), equating to $0.02 USD per call. Payment is made via the X-PAYMENT header per the x402 protocol, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is instant upon payment.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the order status response contains. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know the exact response format or what inputs (if any) the POST body should contain.

Capabilities

x402-paymentusdc-base-networkorder-statuspay-per-requestno-api-keymicropayment

Use cases

  • Checking the status of a specific order (#155) via a paid API call
  • Demonstrating x402 micropayment integration for order management
  • Agent-driven order status polling with per-request USDC settlement

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing pay-per-call order status without API key management
  • Low-volume order status checks where subscription pricing is unnecessary

Not for

  • High-volume order management systems needing bulk status queries
  • Users who need detailed API documentation and response schemas before integrating
  • Checking arbitrary order IDs (this endpoint is hardcoded to order 155)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/155/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 and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the endpoint path is hardcoded to a single order ID (155), making its general utility unclear. The platform advertises many endpoints but provides no substantive documentation for any of them.

Warnings

  • Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no actual content
  • No OpenAPI or schema available — request body format and response structure are unknown
  • Endpoint path is hardcoded to order 155; unclear if other order IDs are supported or how to discover them
  • The broader platform lists many API categories (AI, finance, analytics) but none have documented schemas

Citations

Provenance

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

Agent access