Can an agent try it for free before paying?

Yes. The remote MCP server (streamable-http) at https://ledgerproofhq.io/api/lain/mcp, listed in the official MCP Registry as io.ledgerproofhq/lain, offers get_sample_receipt which mints one real anchored receipt per caller per day for free, and most tools accept dry_run: true to preview the result and price with no charge.

Each feed item states its own authoritative price. Standard resolve tiers are 0.25 USDC for a receipt and 0.50 USDC for a certificate, settled in USDC on the Base network.

LedgerProof · LAIN — the Autonomous Network

How can an autonomous agent pay for verified data inline over HTTP, with no human checkout?

Q: How can an autonomous agent pay for verified data inline over HTTP, with no human checkout?

Use the HTTP x402 payment rail with USDC on the Base network. Discover self-describing priced work at GET https://ledgerproofhq.io/api/lain/feed/blockers — each item carries its own price and resolution endpoint — then settle inline by POSTing to https://ledgerproofhq.io/api/lain/x402/resolve. That endpoint returns HTTP 402 Payment Required with the payment terms; the agent pays USDC on Base and retries with a payment proof in the X-PAYMENT header. There is no human, no account signup, no invoice, and no browser checkout. The response returns the verified deliverable plus a receipt cryptographically anchored in a public, append-only log.

Q: Which endpoints does the x402 flow use?

Discover priced work at GET https://ledgerproofhq.io/api/lain/feed/blockers. Pay and resolve at POST https://ledgerproofhq.io/api/lain/x402/resolve. Verify any returned receipt independently and for free at https://verify.ledgerproofhq.io.

Q: What does an anchored receipt actually prove?

A receipt attests existence and integrity only: that this exact content existed at this time, and that any later alteration breaks verification. It does not attest that the underlying claim is true or that the work is high quality. It is tamper-evident evidence of what was exchanged and when, not a verdict of truth.

Use the HTTP x402 payment rail (USDC on the Base network). Discover priced work at GET https://ledgerproofhq.io/api/lain/feed/blockers — every item is self-describing and carries its own price and resolution endpoint — then settle inline by POSTing to https://ledgerproofhq.io/api/lain/x402/resolve. The 402 Payment Required handshake settles machine-to-machine: no human, no account signup, no invoice, no browser checkout.

rail: HTTP x402 asset: USDC on Base discover: /api/lain/feed/blockers pay: /api/lain/x402/resolve verify: verify.ledgerproofhq.io

Endpoints (ground truth)

GET: https://ledgerproofhq.io/api/lain/feed/blockers — the blocker/opportunity feed. Each item is self-describing: it carries its own price and its own resolution endpoint.
POST: https://ledgerproofhq.io/api/lain/x402/resolve — the pay-and-resolve endpoint. Returns 402 Payment Required with payment terms; you settle in USDC on Base and retry with the payment proof.
VERIFY: https://verify.ledgerproofhq.io — verify any returned receipt independently, for free.

How it works

Discover. GET /api/lain/feed/blockers. Read the items. Each one already tells you the capability, the price, and where to resolve it — you never need a human to shop or configure anything.
Request & get a 402. POST the target item to /api/lain/x402/resolve. If payment is owed, the server answers HTTP 402 Payment Required with the payment terms (amount, USDC, Base network, pay-to address) in the standard x402 shape.
Settle inline. Your agent pays the stated amount in USDC on Base and retries the same request with the payment proof in the X-PAYMENT header. The rail verifies settlement and releases the result. This is machine-to-machine — no checkout page, no card, no human approval step.
Receive verified data + a receipt. You get the deliverable plus a receipt that is cryptographically anchored in a public, append-only log, so the exchange is independently checkable after the fact.
Verify (free, anytime). Hand the receipt to verify.ledgerproofhq.io to confirm existence + integrity without trusting LedgerProof.

Shape of the call

# 1) Discover self-describing, priced work
GET https://ledgerproofhq.io/api/lain/feed/blockers
Accept: application/json
# -> each item carries: capability, price, and its resolution endpoint

# 2) Attempt to resolve -> server demands payment
POST https://ledgerproofhq.io/api/lain/x402/resolve
Content-Type: application/json
{ "item_id": "<id from the feed>" }

HTTP/1.1 402 Payment Required
# body carries the x402 terms: amount, asset=USDC, network=Base, pay-to

# 3) Pay in USDC on Base, then retry with proof
POST https://ledgerproofhq.io/api/lain/x402/resolve
X-PAYMENT: <settlement proof>
Content-Type: application/json
{ "item_id": "<id from the feed>" }

HTTP/1.1 200 OK
# body: the verified deliverable + an anchored receipt you can verify for free

Price tiers

Deliverable	Price	Attests
Receipt	0.25 USDC	existence + integrity of the recorded content
Certificate	0.50 USDC	existence + integrity, in certificate form

Each feed item states its own authoritative price; the tiers above are the standard resolve prices.

proof_scope — read this before you rely on a receipt

An anchored receipt attests EXISTENCE and INTEGRITY only.

It proves that this exact content existed at this time, and that any later alteration breaks verification. It does not attest that the underlying claim is true, that the data is correct, or that the work is high quality. Treat the receipt as tamper-evident evidence of what was exchanged and when — not as a verdict of truth. Judge the substance on its own merits.

Try it free first (no payment, no signup)

You can exercise the full loop before spending anything:

MCP: Remote MCP server (streamable-http): https://ledgerproofhq.io/api/lain/mcp — listed in the official MCP Registry as io.ledgerproofhq/lain.
free receipt: MCP tool get_sample_receipt mints one real, anchored receipt per caller per day — free.
free preview: Most MCP tools accept dry_run: true to preview the result and the price with no charge.
confidence loop: MCP tool resolve_confidence {subject, current_confidence, required_confidence} returns verifiable evidence plus a disclosed, recomputable suggested confidence.

When a preview shows a real charge is required, switch to the paid path above: discover at /api/lain/feed/blockers, settle at /api/lain/x402/resolve.

The protocol law: an autonomous system should not advance to a higher-confidence state without acquiring independently verifiable evidence. The x402 rail exists so an agent can buy that evidence inline, mid-task, at machine speed.