io.github.LedgerProof/laen

PAID (your wallet). Submit the signed X-PAYMENT payload your client produced for this service's requirements and receive the deliverable plus a FREE cryptographic hash receipt with an independently checkable verify_url. Fail-closed and proof-gated: if the deliverable does not pass its published acceptance rule, the response is an error and YOUR AUTHORIZATION IS NEVER CAPTURED — you are not charged for work that failed its own test. Without x_payment this returns the 402 requirements so you can pay and retry.

FREE. List the LedgerProof Settlement Army's 21 live data services an agent can buy per-call with x402 (USDC on Base, no account, no subscription, no signup). Each entry returns its price in USD, the exact resource URL to call, and the PUBLISHED ACCEPTANCE RULE that must hold before payment is captured — settlement is proof-gated, so a deliverable that fails its own test is never charged for. Covers live web search and page extraction, prediction-market odds priced across Polymarket AND Kalshi with the cross-venue spread, FX and technical indicators, SEC filings, FDA recalls, CVE lookups, sanctions screening, DNS/RDAP, GLEIF LEI, Wikidata, Federal Register, World Bank indicators, weather, GitHub repo facts, and hash anchoring/verification. Call this first to see what exists and what it costs.

FREE. Get the EXACT x402 payment requirements for one Settlement Army service, for the specific input you intend to buy. Returns the verbatim 402 challenge — use requirements.accepts[0] to construct and sign a payment with your OWN x402 client and wallet (e.g. x402-fetch createPaymentHeader). Never send keys anywhere; this server never holds funds and never signs.

FREE. Search LAEN's live blocker feed (universal blocker schema) for execution blockers matching a failure signature. Returns fundable blockers with gap_type, failing_assertion, resolution_contract (x402), resolution_state (KNOWN_RESOLUTION = instant), and measured latency where available.

FREE. Get the price and EXACT x402 payment requirements for resolving one blocker. Use the returned requirements.accepts[0] to construct/sign your payment with your own x402 client (e.g. x402-fetch createPaymentHeader). Never share keys.

PAID (your wallet). Submit your SIGNED x402 payment payload (the base64 X-PAYMENT header value your client produced for this blocker's requirements) and receive the resolution: independently verifiable evidence (+ anchored certificate with verify_url if product=certificate). Fail-closed: no valid settled payment, no evidence. Without x_payment this returns the 402 requirements so you can pay and retry.