x402basequality 0.30

x402-gated medical records endpoint on Base, paid per-request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com serves medical record data behind an x402 paywall. The specific resource `/api/v1/medical/records/32` returns JSON content upon payment. It is part of a broader platform (lowpaymentfee.com) that hosts dozens of pay-per-call API endpoints across categories including data analytics, AI/ML inference, finance, and infrastructure utilities.

The endpoint accepts POST requests and settles payments on the Base network using USDC (contract 0x8335…2913). The x402 challenge advertises a maximum amount of 20,000 base units, which at 6 decimals for USDC equals $0.02 per request — consistent with the site's uniform $0.02/request pricing. No API keys or rate limits are advertised; access is granted purely via the x402 payment header. The payment timeout is 300 seconds.

Important caveat: the endpoint path suggests it returns medical records, which is a regulated data category. No documentation, OpenAPI schema, or example responses are available, so the actual content, data provenance, and compliance posture of this endpoint are unknown. The broader site's crawled pages (pricing, README, /api) all resolve to a minimal "Connect wallet" page with no further documentation.

Capabilities

x402-paymentper-request-billingusdc-settlementbase-networkmedical-datajson-responsepost-method

Use cases

  • Retrieving medical record data on a per-request payment basis
  • Agent-driven access to health records without API key provisioning
  • Programmatic medical data retrieval settled in USDC on Base

Fit

Best for

  • Agents that need on-demand medical record access with crypto micropayments
  • Developers exploring x402 payment protocol integrations
  • Use cases requiring keyless, pay-as-you-go API access

Not for

  • Production healthcare applications requiring HIPAA-compliant, audited data pipelines
  • Users who need detailed API documentation or schema guarantees before integration
  • High-volume batch retrieval where per-request pricing is inefficient

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/32 \
  -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 zero documentation on request/response schemas, no OpenAPI spec, no example payloads, and the medical records domain raises regulatory concerns with no compliance information available.

Warnings

  • Medical/health data category — no HIPAA compliance or data provenance information provided
  • No OpenAPI schema, request body schema, or response schema available
  • No documentation beyond the landing page listing; /README, /pricing, /api pages are empty
  • Actual content and data source behind /api/v1/medical/records/32 is completely unknown
  • The record ID '32' is hardcoded in the path — unclear if other IDs are available or how to discover them

Citations

Provenance

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

Agent access