x402basequality 0.35

Pay-per-call lab results endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a "lab results" resource (ID 31) behind an x402 paywall. The provider operates a broad suite of pay-per-request 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. No API keys, rate limits, or subscriptions are required; callers simply attach an x402 payment header to each request.

The specific endpoint `/api/v1/lab/results/31` is listed under the title "Premium API Access" but its exact data payload is not documented in the crawled material. The x402 challenge confirms it is live, accepts POST requests, and requires up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The response MIME type is `application/json`.

Because the provider's site offers no detailed documentation for this particular path (the /api, /pricing, and /README pages all resolve to a wallet-connect stub), the actual schema of the returned JSON is unknown. The endpoint appears to be part of a larger catalog of similarly priced endpoints, but without further docs or example responses, callers should treat this as an exploratory integration.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responseno-api-keylab-results

Use cases

  • Retrieving lab result data (ID 31) on demand with per-call USDC payment
  • Integrating pay-per-request data access into autonomous agent workflows
  • Testing x402 payment flows against a live, low-cost endpoint

Fit

Best for

  • Agents or developers exploring x402 payment protocol integrations
  • Low-volume, on-demand data retrieval without subscription commitments
  • Crypto-native applications that can settle in USDC on Base

Not for

  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • High-volume batch processing where per-call pricing may add up
  • Non-crypto workflows that cannot produce x402 payment headers

Quick start

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

Example

Request

{
  "url": "https://lowpaymentfee.com/api/v1/lab/results/31",
  "method": "POST",
  "headers": {
    "X-PAYMENT": "<x402-payment-token>",
    "Content-Type": "application/json"
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and confirms pricing and payment details, but there is no documentation, no response schema, and no example output for this specific endpoint. The endpoint path ('lab/results/31') is not listed on the provider's homepage catalog, making its purpose unclear. Effectively a stub listing.

Warnings

  • No documentation exists for the /api/v1/lab/results/31 path — its data payload is unknown.
  • The provider's /api, /pricing, and /README pages all return only a 'Connect wallet' stub with no useful content.
  • This specific endpoint does not appear in the provider's homepage API catalog, raising questions about its intended use.
  • Output schema is not provided; response structure must be discovered empirically.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 22:26:18Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access