x402basequality 0.20

x402-gated EHR endpoint on Base, pay $0.02 per request in USDC with no API keys.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at `/api/v1/ehr/52` is part of the lowpaymentfee.com platform, which offers a broad catalog of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. The specific resource at path `/ehr/52` is listed under the generic title "Premium API Access" with no further documentation about what EHR data it returns. The "ehr" path segment suggests Electronic Health Records, but no schema, sample response, or field-level documentation is available.

The endpoint is live and returns a valid x402 challenge on POST. Payment is settled on the Base network using USDC (contract `0x8335…2913`, 6 decimals). The `maxAmountRequired` of 20000 base units equals $0.02 per request. No API keys, rate limits, or subscription commitments are required — callers simply attach an `X-PAYMENT` header with a valid x402 payment proof.

Because the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" stub with no substantive content, there is effectively zero documentation for this specific endpoint. The input schema, expected POST body, and response format are entirely unknown. Prospective callers should treat this as an exploratory or experimental endpoint until the provider publishes proper documentation.

Capabilities

x402-paymentpay-per-requestusdc-settlementbase-networkehr-datano-api-keypost-endpoint

Use cases

  • Retrieving electronic health record data for a specific resource (ID 52)
  • Programmatic access to health data without API key management
  • Agent-driven pay-per-call health data retrieval on Base

Fit

Best for

  • Developers exploring x402-gated health data endpoints
  • Agents that need keyless, per-call access to EHR-style data
  • Prototyping pay-per-request health data integrations

Not for

  • Production healthcare applications requiring documented, HIPAA-compliant APIs
  • Use cases needing bulk or batch EHR data retrieval at scale
  • Anyone who needs clear response schemas before integrating

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.20/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation for this specific resource. No input schema, no response schema, no examples, and the docs pages are all empty stubs. The 'ehr' path is suggestive but unconfirmed. This is effectively a stub listing.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README all return empty 'Connect wallet' pages
  • The 'ehr' path suggests Electronic Health Records, which is a regulated data category (HIPAA, GDPR); no compliance information is provided
  • No input or output schema is documented; callers must experiment to discover the expected POST body and response format
  • The specific resource ID '52' is opaque with no explanation of what it references

Citations

Provenance

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

Agent access