x402basequality 0.30

Pay-per-call medical records 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 x402-enabled endpoint at `/api/v1/medical/records/85` is part of a broader suite of pay-per-request APIs hosted on lowpaymentfee.com. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The x402 challenge was successfully captured, confirming the endpoint is live.

The provider offers a wide catalog of APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced uniformly at $0.02 per request. The specific endpoint in this listing appears to serve medical records data (resource path `/api/v1/medical/records/85`), though the provider's landing page does not list a dedicated "medical" category, and no documentation, schema, or example payloads are available for this particular route. The endpoint's description is simply "Premium API Access," which is generic and uninformative about the actual data returned.

Because no OpenAPI spec, request/response schema, or detailed documentation exists for this endpoint, the exact input parameters and output format are unknown. The provider advertises no API keys, no rate limits, and instant access. Agents should send a POST request with an `X-PAYMENT` header containing a valid x402 payment proof to receive the response.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestmedical-recordsjson-responseno-api-key

Use cases

  • Retrieving medical record data on a per-request payment basis
  • Integrating health data into agent workflows without subscription commitments
  • Programmatic access to medical records via crypto-settled micropayments

Fit

Best for

  • Agents needing on-demand medical record lookups without API key management
  • Developers exploring x402 pay-per-call patterns on Base
  • Low-volume or sporadic access to health data where subscriptions are overkill

Not for

  • Production healthcare applications requiring HIPAA-compliant, audited data pipelines
  • High-volume bulk medical data retrieval (no documented batch endpoints)
  • Users who need detailed documentation or guaranteed SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/85 \
  -H "X-PAYMENT: <x402_payment_proof>" \
  -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 for this specific medical records route, and the endpoint path is not listed on the provider's own landing page. The "medical records" label raises regulatory concerns with zero supporting detail.

Warnings

  • No documentation or schema available for /api/v1/medical/records/85 — input parameters and response format are entirely unknown.
  • This endpoint is not listed in the provider's public API catalog on the landing page, raising questions about its status and legitimacy.
  • Medical/health data may be subject to regulatory requirements (e.g., HIPAA, GDPR health data provisions). No compliance information is provided.
  • The generic description 'Premium API Access' gives no indication of what data is actually returned.
  • No examples, no OpenAPI spec, and no README content available (pages behind wallet connect).

Citations

Provenance

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

Agent access