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 #108 via a POST request, gated by the x402 payment protocol. It is part of a broader platform offering numerous 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/108/status` is labeled "Premium API Access" in the x402 challenge. The payment challenge confirms the endpoint is live, accepting USDC (contract 0x8335…2913 on Base) with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys or rate limits are advertised; access is granted purely through per-request x402 micropayments. The platform emphasizes simplicity: no subscriptions, no minimums, no commitments.

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 spec, no request/response schema documentation, and no examples beyond the landing page's list of available endpoints. The exact response format for this order-status endpoint is unknown. The endpoint path is hardcoded to order 108, which raises questions about whether it is a demo/sample endpoint or intended for a specific use case.

Capabilities

x402-paymentusdc-baseorder-statusper-request-micropaymentno-api-key

Use cases

  • Checking the status of a specific order (#108) via a single micropayment
  • Demonstrating x402 protocol integration for pay-per-call APIs
  • Agent-driven order status lookups without API key management

Fit

Best for

  • Developers experimenting with x402 micropayment protocol
  • Agents needing keyless, pay-per-call API access on Base
  • Quick order status checks without subscription overhead

Not for

  • Querying arbitrary order IDs (endpoint is hardcoded to order 108)
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • High-volume order management systems needing bulk queries

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/108/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), but there is no documentation, no OpenAPI spec, no request/response examples, and the endpoint path is hardcoded to a single order ID. The docs pages are empty beyond a wallet connect prompt, making it impossible to determine what the response looks like or how to use the endpoint meaningfully.

Warnings

  • Documentation pages (/docs, /api, /pricing, /README) are effectively empty — only showing 'Connect wallet'
  • No OpenAPI or schema documentation available for request or response formats
  • Endpoint path is hardcoded to order 108 — unclear if other order IDs are supported
  • The 'Premium API Access' label is generic and does not describe the actual functionality
  • No information about what data the order status response contains

Citations

Provenance

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

Agent access

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