Production · REST API live at irl.macropulse.live

Immutable Reasoning Log
for Autonomous Agents

IRL puts a cryptographic seal on every autonomous trading decision before it reaches the exchange. Pre-execution policy enforcement, bitemporal audit ledger, post-trade verification. Bring your own model and signal, or use MacroPulse as a turnkey Market Truth Anchor.

The Ownership Gap

Current observability infrastructure captures what autonomous agents did and when. It cannot prove why — or what the agent knew at the moment of decision. This is the gap that regulators are asking about, and that no existing tool closes.

Capability Current state With IRL
What action was takenLoggedLogged + sealed
When the action occurredSingle timestampBitemporal (valid_time + txn_time)
Why the action was takenApproximate / inferredDeterministic CognitiveSnapshot
What the agent knew at decision timeNot provableCryptographically proven via L_t fingerprint
Whether constraints were enforcedNot guaranteedPre-execution hard halt on violation
Which model produced the decisionNot verifiableModel hash in Multi-Agent Registry
Whether execution matched reasoningNot trackedPost-trade verifier with divergence detection

The Audit Chain

Every trade produces a cryptographic chain from regime attestation to exchange confirmation. No party can alter any link without breaking the chain.

MacroPulse MTA
Ed25519-signed regime broadcast. Cryptographic proof of the macro state at the exact moment of decision.
IRL Engine — POST /irl/authorize
Agent submits reasoning snapshot. IRL runs all pre-execution checks atomically.
MAR check Policy enforce L_t fingerprint Bitemporal gate SHA-256 seal
Agent receives
reasoning_hash + trace_id — embedded in exchange order metadata before submission.
Exchange execution
Order hits the market. Execution report returned to agent with exchange_tx_id.
IRL Engine — POST /irl/bind-execution
final_proof = SHA-256(reasoning_hash ‖ exchange_tx_id) — chain closed.
MATCHEDChain closed. Regulator can verify independently.
DIVERGENTFlagged. Reason recorded permanently.

Try it now — no setup

Three demo agents are pre-seeded. Use Swagger UI to run a full authorize → bind-execution cycle in-browser. No API key, no registration.

Three Editions

Each layer is independently deployable. Start with L1 in under a day. Upgrade when your regulatory requirements escalate.

L2 IRL Audit Platform
Enterprise compliance with anti-replay and signed market truth.
  • Everything in L1, plus:
  • Signed heartbeats — monotonic sequence + Ed25519, binds each request to a specific MTA broadcast
  • Replay prevention — an agent cannot use a historical regime to authorise a present-day action
  • Forensic replay API — any historical trade reconstructable from its sealed snapshot
L3 IRL Sovereign Gateway
For clients where compliance cannot reveal alpha.
  • Everything in L2, plus:
  • TEE execution — policy enforced inside a hardware-attested enclave (Intel TDX / AMD SEV)
  • Wasm policy modules — hot-reloadable sandboxed policies, no engine changes required
  • ZK compliance proofs — prove policy adherence to a regulator without revealing model or strategy
  • Double-Green signing — exchange API key inaccessible unless both MTA and MAR checks pass

Bring Your Own Signal — or Use Ours

IRL depends on an abstract MTA interface, not on any specific operator. Any cryptographically signed regime source can serve as the MTA for your deployment.

MacroPulse MTA — turnkey

Zero additional infrastructure. MacroPulse's HMM/PCA pipeline produces Ed25519-signed regime broadcasts with version hashes. Plug in your URL and public key — IRL verifies signatures and caches state automatically. Recommended for firms without a proprietary regime model.


Custom MTA — one implementation

Quant firms running their own regime pipelines implement a single Rust trait (MtaClient) and pass it at startup. IRL seals against your signal with the same cryptographic guarantees. Your model stays private. Your compliance chain is identical.

Built for the Regulations That Are Coming

IRL produces evidence that maps directly to specific regulatory requirements — not general "auditability," but the specific proof each framework asks for.

Requirement IRL mechanism
Decision auditability — EU AI Act Art. 12reasoning_hash = SHA-256(canonical snapshot)
Transparency to regulators — Art. 13ZK proof: compliance verified without alpha disclosure
Pre-trade risk controls — SEC Rule 15c3-5Policy Engine blocks non-compliant intents before execution
Contemporaneous recordkeeping — MiFID IIBitemporal timestamps: valid_time + txn_time, immutable
Fleet governance — DORA, AI ActMulti-Agent Registry: per-agent identity and risk controls

Per-Agent, Not Per-Trade

Compliance value is in the seal existing — not in counting seals. L1 is operational in under a day. Upgrade when your regulatory requirements escalate.

L2
IRL Audit Platform
$1,200 / agent / month
Minimum 3 agents
  • Everything in L1, plus:
  • Signed heartbeats — anti-replay enforcement
  • MacroPulse MTA integration — or custom MtaClient
  • Compliance dashboard — read-only regulator view
  • Forensic replay API — any historical trade reconstructable from its sealed snapshot
  • Merkle anchoring — period root hashes anchored to Bitcoin via OpenTimestamps
  • 99.9% uptime SLA
L3
IRL Sovereign Gateway
Enterprise
Quoted per engagement · $8k–$25k/mo typical
  • Everything in L2, plus:
  • TEE execution — Intel TDX / AMD SEV
  • Wasm policy modules — hot-reloadable, sandboxed
  • ZK compliance proofs — prove adherence without revealing alpha
  • Double-Green signing — API key inaccessible until both checks pass
  • Dedicated support + quarterly review

Volume discounts — L1 and L2

Fleet sizeDiscount
1–5 agentsList price
6–15 agents−15%
16–30 agents−25%
31+ agents−35% (negotiated)

Custom MTA deployments (proprietary signal) pay standard L1/L2/L3 pricing — no additional fee for signal-agnostic configurations. MacroPulse MTA as an L1 add-on: $300/month.

Start With the Sandbox

The API is live. Three demo agents are pre-seeded. Try authorize + bind-execution in Swagger UI before committing to a deployment conversation.

Open Swagger UI → Contact for Licensing
gabriel.veron134@gmail.com