Insurance claims data endpoint on Base, pay-per-request via x402 with USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves insurance claims data (specifically claim ID 21) behind a per-request USDC micropayment on the Base network. The endpoint accepts POST requests and returns JSON. Payment is settled on-chain using USDC (contract 0x8335…2913 on Base) with a cost of $0.02 per request (20,000 base units at 6 decimals). No API keys, rate limits, or subscriptions are required — callers simply attach an x402 payment header to each request.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. This particular endpoint falls under an insurance claims category, though the provider's landing page does not list it among the featured APIs. No OpenAPI schema, request/response examples, or detailed documentation were found for this specific endpoint, so the exact request body format and response structure are unknown.
The endpoint is confirmed live: it returns a well-formed x402 version 1 challenge (HTTP 402) with a 300-second payment timeout. The payment recipient address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. Because no documentation describes the expected POST body or the shape of the claims data returned, callers will need to experiment or contact the provider for integration details.
Capabilities
Use cases
- —Retrieving insurance claim details programmatically with per-call payment
- —Integrating on-chain micropayments for insurance data access
- —Agent-driven insurance claim lookups without API key provisioning
Fit
Best for
- —Developers needing on-demand insurance claims data without subscriptions
- —AI agents that can settle x402 USDC payments on Base
- —Prototyping pay-per-use insurance data integrations
Not for
- —Bulk insurance data exports (no batch endpoint documented)
- —Users who cannot transact USDC on the Base network
- —Production use cases requiring well-documented request/response schemas
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/21 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge, but there is no OpenAPI schema, no request/response examples, and no documentation for this specific insurance claims endpoint. The landing page doesn't even list this endpoint among its featured APIs, making it effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —This specific endpoint (/api/v1/insurance/claims/21) is not listed on the provider's landing page among featured APIs
- —Request body format and response structure are completely unknown
- —Hardcoded claim ID (21) in the URL — unclear if other claim IDs are supported or how to discover them
Citations
- —The endpoint returns a valid x402 version 1 challenge with HTTP 402, confirming it is livehttps://lowpaymentfee.com/api/v1/insurance/claims/21
- —Payment is in USDC on Base network at 20,000 base units ($0.02) per requesthttps://lowpaymentfee.com/api/v1/insurance/claims/21
- —The provider advertises uniform $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/insurance/claims/21