MEMORA
ACCOUNTABILITY INFRASTRUCTURE FOR AI AGENTS

AI agents act.Memora proves what happened.

Memora gives every important agent run a verifiable receipt — showing who authorized it, what it acted on, and whether the captured record changed. Add it without replacing your existing stack.

Create your first receiptVerify this receipt

Mission Control

Sample execution

Receipt recorded

Activity

Approve supplier payment

Built around your stack, not instead of it.

Six months later, someone asks

Who approved this payment?

A log is what your system says happened. Evidence is a record another person can check.

production.logfragment
10:42:31INFOrequest received
10:42:32INFOchecking policy
10:42:33INFOpayment approved
10:42:34INFOpayment submitted
10:42:34INFOdone

Logs still help your team debug. But when a customer, auditor, or partner challenges an action, “our database says so” may not be enough.

Receipt anatomy

A verifiable record around the run.

An execution receipt preserves the agent identity, authorization context, inputs, outputs, timing, and links to earlier actions. Ask a question and Memora points to the captured evidence.

Agent identity and signer evidence highlighted.

Treasury Agent

Execution Receipt

Just now

Verification: verifiedAnchoring: externally anchored
TaskApprove supplier payment
SupplierNorthstar Cloud Ltd.
Amount$12,500
Agent IDtreasury-agent
Policysupplier-payment-v3
Payload hash9f2a7c1d56...693d3d20
Parent eventevt_e5a728...77fe28a1

Agent identity

treasury-agent

Signer 0x71C84a70...8918c4A7

Authorization

Policy passed

$12,500 was within the configured $25,000 threshold.

Lineage

5 linked events

Integrity

Verified intact

Tamper lab

Change the receipt. Verification fails.

Edit the sample locally and watch Memora detect where the receipt no longer matches the signed execution record.

Editable sample receipt

Local verification demonstration using sample data. No external anchor is queried.

Verification

01Payload hashValid
02Event digestValid
03Agent signatureValid
04Operator signatureValid

Verification passed

This receipt matches the recorded execution and its signature checks.

Use the evidence level the action deserves.

Workspace and agent policy choose the required behavior. The SDK does not silently change it.

Provenance

Supplier payment receipt

Northstar Cloud Ltd.

$12,500 · treasury-agent

verified

Operator-signed record

The operator signs the captured execution record.

Agent signer verified

The agent signer is cryptographically verified.

External ordering

Ordering remains inside Memora's internal provenance boundary.

Externally checkable anchor

Verification does not rely on a public external anchor.

Selected policy

VERIFIED receipt using internal provenance without an external network dependency.

This verifies properties of the captured record. It does not prove model correctness or an uncompromised runtime.

When the action is challenged, reconstruct the trail.

Select an event to inspect the evidence preserved at that point in the execution.

Selected event

Request received

1 / 9

Northstar Cloud Ltd. requested $12,500.

Replay reconstructs and verifies the recorded trail. It does not rerun the model or prove runtime integrity.

SDK integration

  1. 01import { Memora } from "@smritheon/memora-core";
  2. 02 
  3. 03const memora = new Memora({
  4. 04 agentId: process.env.MEMORA_AGENT_ID!,
  5. 05 apiKey: process.env.MEMORA_API_KEY!,
  6. 06});
  7. 07 
  8. 08const run = memora.wrap("supplier-payment", approvePayment);
  9. 09const result = await run(request);

Keep your runtime. Add an evidence layer.

The SDK records workflow events and returns the original result. Tool input and output hashes require tool or receipt instrumentation.

SDK wrappers and the optional OpenTelemetry span bridge are available today.

Create your first receipt Read the quickstart

Evidence, not endorsements

Know exactly what Memora proves.

Memora verifies the integrity, identity, and lineage of the captured execution record. It does not claim that the model was correct or that an uncompromised runtime captured every real-world event.

  1. Published SDK

    @smritheon/memora-core

    Inspect package

  2. Public trust model

    Claims, boundaries, and known limitations are documented in public.

    Inspect trust model

  3. Dual signatures

    The verified path binds agent and operator signatures to the execution record.

    Inspect protocol

  4. Merkle provenance

    Batch inclusion proofs connect individual events to a recorded Merkle root.

    Inspect provenance model

  5. Hosted developer preview

    The hosted surface is available for evaluation; APIs and schema may change before v1.0.

    Read documentation

  6. Optional external anchoring

    Hedera testnet ordering and registry commits are available when configured. No mainnet deployment exists.

    Inspect anchoring boundary

Can you prove what your agents did?

Give your next consequential run a receipt that developers, investigators, and reviewers can verify.

Create your first receiptRead the quickstart

Need to evaluate Memora with your team? Talk to us