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 #82 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 across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request 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 maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys or rate limits are advertised; access is instant once payment is included in the X-PAYMENT header.

Note that this specific endpoint is scoped to a single order ID (82) and its status. The broader platform lists many other endpoints (sentiment analysis, text summarization, embeddings, price feeds, geocoding, etc.) at the same $0.02 price point, but documentation beyond the landing page is extremely thin — the /docs, /api, /pricing, and /README pages all render only a wallet-connect prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available.

Capabilities

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

Use cases

  • Checking the status of a specific order programmatically with per-call USDC payment
  • Demonstrating x402 protocol integration for micropayment-gated endpoints
  • Agent-driven order tracking without API key provisioning

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents needing keyless, pay-per-call access to simple endpoints
  • Low-volume order status checks without subscription overhead

Not for

  • High-volume order management systems (no bulk/batch support documented)
  • Users needing detailed API documentation or OpenAPI specs
  • Production workflows requiring well-documented request/response schemas

Quick start

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

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 OpenAPI spec, no request/response schema, no documentation beyond a landing page, and the endpoint is narrowly scoped to a single order ID. The docs/pricing/README pages are all empty wallet-connect stubs.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown
  • All documentation pages (/docs, /api, /pricing, /README) render only a wallet-connect prompt with no content
  • This endpoint is hardcoded to order ID 82; unclear if it generalizes to other order IDs
  • The platform lists many other endpoints but none have documented schemas or examples

Citations

Provenance

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

Agent access