x402basequality 0.25

Pay-per-call medical records endpoint on Base via x402 (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/medical/records/54

What it does

This endpoint at lowpaymentfee.com provides access to a specific medical record (record ID 54) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The broader lowpaymentfee.com platform hosts a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. This particular endpoint falls under a "medical/records" path, but no documentation exists describing the schema of the medical record returned, what input fields the POST body expects, or what the record actually contains. The provider's landing page does not list this medical records endpoint among its advertised APIs, which raises questions about its intended use and data provenance.

The endpoint is live and returns a well-formed x402 challenge (HTTP 402) with version 1 of the protocol. The payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base. The maximum timeout for payment settlement is 300 seconds.

Capabilities

x402-paymentusdc-basepay-per-callmedical-recordsjson-responseno-api-key

Use cases

  • —Retrieving a specific medical record (ID 54) via programmatic API call
  • —Demonstrating x402 micropayment flows for health data access
  • —Agent-driven retrieval of structured medical data with crypto payment

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents needing pay-per-call access to medical record data
  • —Crypto-native applications that want keyless API access

Not for

  • —Production healthcare applications requiring HIPAA compliance documentation
  • —Users needing bulk medical records retrieval (only a single record ID is exposed)
  • —Anyone requiring detailed API documentation or input/output schemas before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/54 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_proof>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/medical/records/54
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation on request body schema, response schema, or what the medical record contains. The endpoint is not listed on the provider's own landing page. The medical/health data category raises regulatory concerns with zero compliance documentation available.

Warnings

  • —Medical/health data endpoint with no documentation on data provenance, compliance (HIPAA, GDPR), or consent framework.
  • —Endpoint path (/api/v1/medical/records/54) is not listed among the provider's advertised APIs on the landing page.
  • —No request body schema or response schema available — callers cannot know what to send or what they will receive.
  • —No OpenAPI spec, README, or detailed docs were accessible (pages returned only 'Connect wallet').
  • —Regulated data category (medical records) with no visible compliance or licensing information.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/nzYwZR
Pay-per-call medical records endpoint on Base via x402 (USDC). — Clawmart · Clawmart