x402basequality 0.35

x402-gated medical records endpoint on Base, pay-per-request with 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/24` returns JSON content upon payment. It is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, and utility services, all settled via USDC on the Base network.

The x402 challenge confirms the endpoint is live and accepts exact-scheme payments in USDC (contract 0x8335…2913 on Base). The maximum amount required is 20,000 base units, which at 6 decimals for USDC equals $0.02 per request — consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is made via the X-PAYMENT header; no API keys or accounts are needed.

No OpenAPI schema, request body documentation, or response examples are available for this specific medical records endpoint. The provider's landing page lists it under a generic "Premium API Access" label. The nature of the data returned (whether synthetic, anonymized, or otherwise) is not documented. Given the "medical/records" path, consumers should exercise caution regarding data provenance and regulatory compliance (HIPAA, GDPR, etc.). The lack of documentation about what this endpoint actually returns is a significant gap.

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 API key management
  • Testing x402 payment flows against a live endpoint

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents needing on-demand medical record data with no subscription
  • Projects requiring keyless, pay-as-you-go API access

Not for

  • Production healthcare applications requiring HIPAA-compliant, audited data sources
  • Bulk retrieval of large medical datasets (pay-per-request model becomes costly at scale)
  • Users who need detailed API documentation or guaranteed SLAs

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no documentation on request parameters, response schema, or the nature of the medical data returned. The crawl pages beyond the landing page are empty (wallet-connect gates). This is effectively a stub listing.

Warnings

  • No documentation exists for the /api/v1/medical/records/24 endpoint — request format and response schema are unknown.
  • The path suggests medical/health data; no information is provided about data provenance, whether it is synthetic, anonymized, or real. Regulatory compliance (HIPAA, GDPR) is unaddressed.
  • The provider site gates most pages behind a wallet-connect flow, making documentation inaccessible to crawlers.
  • No OpenAPI spec or AI plugin manifest is available.

Citations

Provenance

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

Agent access