Pay-per-call insurance claims API on Base, settled in USDC via x402.
What it does
This endpoint at lowpaymentfee.com provides access to an insurance claims resource (claim ID 84) behind an x402 paywall. It accepts HTTP POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge requiring up to 0.02 USDC per request (maxAmountRequired of 20,000 base units at 6 decimals).
The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint (/api/v1/insurance/claims/84) is not listed on the site's public catalog, so its exact response schema and data content are unknown. The x402 challenge was successfully captured (HTTP 402), confirming the endpoint is live.
Because no OpenAPI spec, documentation, or example responses are available for this particular endpoint, the actual fields returned for an insurance claim are unclear. Users should expect a JSON object but will need to inspect the response after payment to understand the schema. The endpoint's timeout is 300 seconds.
Capabilities
Use cases
- —Retrieving insurance claim details programmatically with per-request USDC payment
- —Integrating insurance claim data into automated agent workflows without API key management
- —Accessing structured claim information for auditing or analytics pipelines
Fit
Best for
- —Agents or services that need on-demand insurance claim data without subscription commitments
- —Developers experimenting with x402 pay-per-call protocols on Base
- —Workflows requiring frictionless, keyless API access to claim records
Not for
- —Bulk retrieval of many insurance claims (each call costs $0.02 individually, no batch endpoint documented)
- —Users who need detailed documentation or guaranteed schema stability before integrating
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/84 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is no OpenAPI spec, no documentation, no example responses, and this specific endpoint is not even listed on the provider's public catalog. The actual data returned is entirely unknown.
Warnings
- —This specific endpoint (/api/v1/insurance/claims/84) is not listed in the provider's public API catalog — its purpose and response schema are unverified.
- —No OpenAPI specification or endpoint documentation is available.
- —No example response data exists; the JSON schema of the returned claim object is unknown.
- —The endpoint targets a single hardcoded claim ID (84); it is unclear whether other claim IDs are accessible or what the broader resource model looks like.
- —Insurance data may be subject to regulatory requirements depending on jurisdiction.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units in USDC on Base network with a 300-second timeout.https://lowpaymentfee.com/api/v1/insurance/claims/84
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/insurance/claims/84