x402basequality 0.30

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 #163 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 across data analytics, AI/ML inference, finance/Web3, and utility categories — all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/163/status` is labeled "Premium API Access" by the provider. The x402 challenge confirms it is live, accepting exact-scheme payments of up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B…85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.

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 beyond the x402 challenge's outputSchema stub, and no explanation of what fields the order status response contains. The platform lists many other endpoints (sentiment analysis, summarization, geocoding, gas estimates, etc.) at the same $0.02 price point, but none have documented schemas either. Use with caution: the actual response payload is unknown.

Capabilities

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

Use cases

  • Checking the status of a specific order (#163) via automated agent
  • Demonstrating x402 micropayment integration on Base
  • Building payment-gated API workflows without API key management

Fit

Best for

  • Developers experimenting with x402 protocol payments
  • Agents that need keyless, pay-per-call API access on Base
  • Prototyping micropayment-gated service architectures

Not for

  • Production order management systems (endpoint is hardcoded to order 163)
  • Users needing documented response schemas or SLA guarantees
  • Non-crypto users who cannot settle USDC on Base

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/163/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 (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no explanation of what the endpoint returns. The endpoint path is hardcoded to a single order ID (163), making its general utility unclear. This is effectively a stub listing.

Warnings

  • No documentation available — docs, pricing, and API pages all show only 'Connect wallet' with no content.
  • No request or response schema provided; actual payload structure is unknown.
  • Endpoint is hardcoded to order ID 163; unclear if other order IDs are supported or how to discover them.
  • Platform lists many endpoints but none appear to have documented schemas.

Citations

Provenance

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

Agent access

Check order status via x402 micropayment on Base (USDC, $0.02/request). — Clawmart · Clawmart