x402basequality 0.30

Check order status via x402 micropayment on Base 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 #200 (and presumably other orders at similar paths) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs 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 probed — `/api/v1/orders/200/status` — is listed under the title "Premium API Access" and accepts POST requests. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the payment details (asset, network, amount) and must attach an `X-PAYMENT` header with a valid payment proof. The max 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 gated purely by micropayment.

Documentation is extremely sparse. The landing page lists available API categories and pricing, but the /docs, /pricing, /api, 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 usage examples. The endpoint is live (returns a valid 402 challenge), but the actual response format after successful payment is unknown.

Capabilities

x402-paymentorder-statususdc-micropaymentbase-networkpay-per-callno-api-key

Use cases

  • Checking the status of a specific order programmatically via micropayment
  • Integrating order tracking into an agent workflow without API key management
  • Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • Agents that need on-demand order status checks without subscription commitments
  • Developers experimenting with x402 micropayment protocol on Base
  • Workflows requiring keyless, pay-per-use API access

Not for

  • Bulk order status polling (no documented batch endpoint; $0.02 per call adds up)
  • Use cases requiring detailed response schema guarantees (no documentation available)
  • Users who need non-crypto payment options

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/200/status
# Returns 402 with x402 challenge. Attach X-PAYMENT header with valid USDC payment proof on Base to receive the order status.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and is operational. However, documentation is essentially nonexistent — all doc/pricing/readme pages show only 'Connect wallet'. There is no OpenAPI spec, no response schema, no examples, and the specific purpose of this 'orders/200/status' endpoint is unclear beyond its title. The listing is effectively a stub.

Warnings

  • No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet'
  • No OpenAPI or response schema provided; actual response format after payment is unknown
  • The endpoint path '/api/v1/orders/200/status' is not listed on the landing page among the advertised APIs — its purpose and behavior are unclear
  • Cannot verify what data is actually returned after successful payment

Citations

Provenance

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

Agent access