Iris.

Iris is a Ligate Labs flagship application on the attestation protocol. It gives autonomous AI agents cryptographic attestation of every action they take, with zero blockchain knowledge required from the agent itself. The MCP server is open source (MIT). The relayer is a managed SaaS service that signs and submits attestations on-chain on behalf of the agent's parent organisation, billed in USD or USDC.

Why it exists

AI agents are increasingly autonomous. They execute code, place trades, write content, handle customer interactions, and make regulated decisions. Today, no one can verify what an agent actually did, only what it claims it did. Regulated industries cannot deploy agents without audit trails. Agent-to-agent trust is broken: if agent A passes work to agent B, B has no way to verify A's claim.

Attestation solves this, but agents don't hold wallets, don't hold $LGT, and don't sign transactions. They need a standardised interface. The Model Context Protocol (MCP), an open standard Anthropic introduced, is how modern agents call external tools. Iris ships the canonical MCP attestation server, plus a relayer that handles the on-chain side so agents never have to.

Who uses it

• → Agent framework vendors who want attestation as a product feature (Cursor, Replit Agents, Devin, custom)
• → Regulated industries deploying AI (healthcare, legal, finance, compliance)
• → Autonomous coding tools (Claude Code, Cursor agents) that need auditable diff trails
• → Research agents logging sources consulted and claims extracted
• → Trading agents logging each decision and its evidence
• → Content pipelines logging each transformation step

Two integration paths

1. MCP server (self-hosted)

Clone the open-source repo, plug into any MCP-compatible agent. The server exposes four tools: record, verify, query, schemas. Self-hosting means you bring your own Ligate attestor key, pay $LGT fees directly, and handle submission yourself. Right for teams that already operate blockchain infrastructure.

2. Managed relayer (SaaS, recommended)

Point agents at the Iris hosted MCP endpoint. We sign, submit, and cover on-chain fees. Your organisation is billed monthly in USD or USDC. Same MCP API, zero chain ops on your side. This is the sponsored-gas pattern, applied to attestation.

Tool reference

The MCP server exposes four standard tools.

• record(schema_id, payload) - Post an attestation of an agent action. Returns an attestation ID.
• verify(attestation_id) - Check that an incoming attestation is valid and signed by the schema's attestor set.
• query(filter) - Look up historical attestations by agent, schema, or time range. Paginated.
• schemas() - List available schemas on Ligate (themisra.proof-of-prompt, ligate.agent-action, ligate.code-change, and any others registered).

Example: Claude Code records a refactor

// Before Claude edits files
await ligate.record({
  schema: "ligate.code-change/v1",
  payload: {
    intent: "refactor auth module",
    scope_hash: sha256(filesInScope),
    model: "claude-opus-4-7",
    started_at: "2026-04-24T14:32:00Z"
  }
}) // -> attestation_id: lat1c3a87e…fd9a7c

// After Claude finishes
await ligate.record({
  schema: "ligate.code-change/v1",
  payload: {
    intent_ref: "lat1c3a87e…fd9a7c",
    completed: true,
    diff_hash: sha256(diff),
    files_changed: 14,
    completed_at: "2026-04-24T14:47:00Z"
  }
}) // -> attestation_id: lat1d4f9b2…0e8x3p

// Later, a PR reviewer or auditor
await ligate.verify("lat1d4f9b2…0e8x3p")
// -> "At 14:47 on 2026-04-24, Claude Opus 4.7 signed an
//     attestation that it completed the refactor in
//     lat1c3a87e…fd9a7c, producing diff_hash sha256(...).
//     Signed by the Anthropic-operated attestor."

Pricing

Revenue is the relayer margin on USD billing over $LGT on-chain costs. Recurring SaaS revenue. Margin-positive by design. Independent of $LGT price, which makes it the fastest-to-turn-on line in the Ligate revenue mix.

Not to be confused with the v2 agents chain module

Iris is a developer-facing product that uses the existing attestation module. It is not a new on-chain module. A separate future agents module is planned for v2 of the protocol to give agents on-chain wallets with allowlists, rate limits, and delegation. Both are valuable and complementary; neither is a prerequisite for the other.

Next up

These are the sections we're writing as Iris approaches ship:

1. MCP server installation guide
2. Claude Desktop integration recipe
3. Cursor / LangGraph / OpenAI Agents SDK recipes
4. Relayer API key + Stripe / USDC billing setup
5. Schema reference: ligate.agent-action/v1, ligate.code-change/v1
6. SLA and uptime commitments for Enterprise tier