x402basequality 0.35

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 #84 via a POST request, gated by an x402 payment challenge. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.

The specific resource `/api/v1/orders/84/status` is labeled "Premium API Access" in the x402 challenge. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 "exact" scheme to the payTo address. No API keys or rate limits are required; access is instant once payment is included in the X-PAYMENT header.

Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no usage examples. The endpoint is confirmed live (402 challenge returned), but the actual response payload after successful payment is unknown.

Capabilities

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

Use cases

  • Checking the status of a specific order (#84) via programmatic micropayment
  • Demonstrating x402 payment-gated API access on Base
  • Agent-driven order tracking with per-call USDC settlement

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need to pay-per-call for order status checks
  • Projects already using USDC on Base network

Not for

  • Production order management systems (endpoint is hardcoded to order 84)
  • Users who need detailed API documentation or response schemas before integrating
  • High-volume polling where per-request fees would accumulate quickly

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is essentially nonexistent — no OpenAPI spec, no request/response schemas, no examples. The endpoint path is hardcoded to a single order ID, making its general utility unclear.

Warnings

  • Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no usable content.
  • No OpenAPI or response schema available — the actual payload after payment is unknown.
  • Endpoint is hardcoded to order #84; unclear if other order IDs are supported or how to discover them.
  • The broader platform lists many endpoints but none have documented schemas or examples.

Citations

Provenance

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

Agent access