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 #78 via a POST request, gated by the x402 payment protocol. It is one of many endpoints offered by the lowpaymentfee.com platform, which provides a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility/infrastructure services — all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint `/api/v1/orders/78/status` is labeled "Premium API Access" in the x402 challenge. The challenge confirms the endpoint is live, accepting POST requests, and requires an exact-scheme x402 payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The payment timeout is 300 seconds. No API keys or rate limits are advertised; access is purely payment-gated.

Documentation is extremely sparse — 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 outputSchema stub, and no examples of what the order status response looks like. The endpoint path is hardcoded to order 78, which raises questions about whether this is a demo/sample endpoint or a production resource. Use with caution until more documentation is available.

Capabilities

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

Use cases

  • Checking the status of a specific order (#78) behind a micropayment wall
  • Demonstrating x402 payment-gated API access on Base
  • Agent-driven order tracking with per-request USDC settlement

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents that need to pay per call without API key management
  • Micropayment-gated order status lookups

Not for

  • Bulk order management or querying arbitrary order IDs (endpoint is hardcoded to order 78)
  • Users who need detailed API documentation or response schemas before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/78/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 and returns a valid x402 402 challenge, confirming pricing and network. However, documentation is effectively absent (all pages show only 'Connect wallet'), there is no OpenAPI spec, no request/response schema, and the endpoint path is hardcoded to a single order ID, making its general utility unclear. This is essentially a stub listing.

Warnings

  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no usable content.
  • Endpoint path is hardcoded to order 78 — unclear if other order IDs are supported or if this is a demo.
  • No request body schema or response schema is documented anywhere.
  • No OpenAPI or ai-plugin manifest available.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 06:21:14Z · 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