x402basequality 0.35

Insurance claims data endpoint on Base, pay-per-request via x402 with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to insurance claims data (specifically claim ID 88) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. The specific content and schema of the insurance claims response is not documented in the available crawl material, so the exact fields returned are unknown. The endpoint is live and returning a proper 402 challenge.

Note that the endpoint path includes a hardcoded claim ID (88), suggesting it retrieves a specific insurance claim record rather than performing a search or batch operation. Without further documentation or example responses, the precise data structure and use case remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkinsurance-claims-datapay-per-requestno-api-keyjson-response

Use cases

  • Retrieving insurance claim details by ID for processing or auditing
  • Integrating insurance claims data into automated workflows without managing API keys
  • Agent-driven insurance claim verification with micropayment settlement

Fit

Best for

  • Developers needing on-demand insurance claims data without subscription commitments
  • AI agents that can settle USDC payments on Base for per-call API access
  • Prototyping insurance data integrations with zero onboarding friction

Not for

  • Bulk retrieval of many insurance claims (endpoint is per-claim, per-request)
  • Users who cannot transact in USDC on the Base network
  • Production systems requiring documented response schemas and SLAs

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no documentation of the request body schema, response schema, or what insurance claims data is actually returned. The crawl pages beyond the homepage are empty (wallet-connect gates). This is effectively a stub listing with confirmed liveness but minimal usable detail.

Warnings

  • No response schema or example response available — the actual data returned by this endpoint is unknown.
  • The endpoint path contains a hardcoded claim ID (88); it is unclear whether other claim IDs are supported or what the valid range is.
  • No OpenAPI spec, no AI plugin manifest, and no robots.txt or agents.txt found.
  • Documentation pages (/api, /pricing, /README) are gated behind wallet connection and returned no useful content.
  • The nature and source of the insurance claims data is undocumented — data quality and coverage are unknown.

Citations

Provenance

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

Agent access