x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/orders/195/status

What it does

This endpoint at lowpaymentfee.com returns the status of order #195 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/195/status` is described generically as "Premium API Access." The x402 challenge confirms it 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). Payment is made via the `exact` scheme to address 0x1A2B…85F3 with a 300-second timeout. No API key or account registration is required — callers simply attach an X-PAYMENT header conforming to the x402 protocol.

Documentation on the site is extremely thin: the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional technical detail. 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 advertises no rate limits and instant access, but these claims cannot be independently verified from the crawled material.

Capabilities

x402-paymentusdc-basepay-per-requestorder-statusmicropaymentno-api-keypost-endpoint

Use cases

  • —Checking the status of a specific order programmatically with per-call payment
  • —Demonstrating x402 protocol integration for agent-to-agent commerce
  • —Building payment-gated API workflows on the Base L2 network

Fit

Best for

  • —Developers experimenting with x402 pay-per-call protocols
  • —Agents that need to make one-off order-status lookups without API key provisioning
  • —Low-volume consumers who prefer micropayments over subscriptions

Not for

  • —High-volume order management systems needing bulk status checks (no documented batch endpoint)
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Applications requiring non-USDC or non-Base payment rails

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/orders/195/status
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 wallet-connect prompt, and the endpoint path is hardcoded to a single order ID (195), making its general utility unclear. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown.
  • —Docs, pricing, API, and README pages all return only 'Connect wallet' with no technical content.
  • —Endpoint path is hardcoded to order ID 195; unclear if this is parameterizable or a demo.
  • —Platform claims 'no rate limits' but this is unverifiable from available material.
  • —The broader platform lists many endpoints (AI, finance, utils) but none have documented schemas.

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

JSONhttps://clawmart.sh/api/listings/8ZWNq6
Check order status via x402 micropayment on Base (USDC, $0.02/request). — Clawmart · Clawmart