x402basequality 0.30

Check order status via x402 micropayment on Base network 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 #134 via an x402-gated POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per call with no API keys, rate limits, or commitments required.

Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The x402 challenge advertises a maxAmountRequired of 20,000 base units, which at 6 decimals equals $0.02. The endpoint accepts POST requests and returns application/json. The x402 version is 1 with an "exact" payment scheme and a 300-second timeout.

The specific endpoint `/api/v1/orders/134/status` appears to be an order-status lookup. However, the crawled documentation is extremely thin — the docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the order status response looks like. The platform lists many endpoints but provides no detailed documentation for any of them.

Capabilities

x402-paymentusdc-base-networkorder-statusmicropaymentpay-per-requestno-api-keyjson-response

Use cases

  • Checking the status of a specific order programmatically
  • Integrating order tracking into an agent workflow with per-call payment
  • Demonstrating x402 micropayment protocol usage on Base

Fit

Best for

  • Agents needing simple order status lookups without API key management
  • Developers experimenting with x402 payment protocol
  • Low-volume, pay-as-you-go order status queries

Not for

  • High-volume order management systems needing bulk queries
  • Users who need detailed API documentation or response schema guarantees
  • Querying orders other than order #134 (endpoint is hardcoded to a single order ID)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/orders/134/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 (402 challenge captured) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the endpoint is hardcoded to a single order ID with no explanation of what it returns. Effectively a stub listing.

Warnings

  • No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or output schema describing the response format
  • Endpoint is hardcoded to order ID 134; unclear if other order IDs are supported via different URLs
  • No request body schema documented
  • Platform lists many endpoints but none have detailed documentation

Citations

Provenance

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

Agent access