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 39) behind a per-request USDC micropayment on the Base network. The endpoint accepts POST requests and returns JSON. Payment is handled via the x402 protocol — no API keys, accounts, or rate limits are required. The caller simply includes an X-PAYMENT header with a valid payment proof.
The endpoint charges a maximum of 0.02 USDC per request (20,000 base units of USDC with 6 decimals). The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 on Base using the USDC contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. The x402 challenge specifies a 300-second timeout window.
The broader lowpaymentfee.com platform advertises a wide range of API categories including data & analytics, AI & ML, finance & Web3, and infrastructure utilities — all at the same $0.02/request price point. However, the specific endpoint being listed here (/api/v1/insurance/claims/39) is not explicitly mentioned on the landing page's catalog, and no documentation, request schema, or response schema is available for it. The actual data returned by this insurance claims endpoint is unknown beyond the stated mime type of application/json.
Capabilities
Use cases
- —Retrieving insurance claim details programmatically with per-request payment
- —Integrating insurance claims data into automated workflows without managing API keys
- —Agent-driven insurance data retrieval settled via on-chain USDC micropayments
Fit
Best for
- —Developers needing keyless, pay-as-you-go access to insurance claims data
- —AI agents that can settle x402 payments on Base
- —Prototyping insurance data integrations without subscription commitments
Not for
- —Bulk retrieval of many insurance claims (only a single claim ID endpoint is documented)
- —Users who need detailed API documentation or response schemas before integrating
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/39 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no documentation, no request/response schema, and the specific insurance claims endpoint is not listed on the provider's own landing page catalog. The actual data content and expected POST body are entirely unknown, making this effectively a stub listing.
Warnings
- —No documentation or schema available for this specific endpoint
- —The /api/v1/insurance/claims/39 path is not listed in the provider's own API catalog on the landing page
- —No request body schema or response schema provided — callers cannot know what to send or what to expect
- —The endpoint appears to serve a single hardcoded claim ID (39); unclear if other IDs are supported
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/insurance/claims/39
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/insurance/claims/39