morphon

An evidence layer for agent payments.

AI agents are starting to move money. Morphon records why each payment was allowed or refused, in a form a regulator can read a year later.

prev_hash sha256:9f3c1e…

{ "seq": 10427, "type": "decision", "agent": "treasury-rebalancer-v3", "rail": "x402", "amount": "1.25 USD", "counterparty": "known_vendor", "purpose": "compute.inference", "policy": "sha256:7d21a0…" @ cedar, "decision": allow_with_obligations, "rules_fired": ["amount.single_txn_cap"] }

hash sha256:41abd7…

One event per decision. Immutable, linked to the one before it, and to the one after.

Three questions, answered at the moment of payment

Is this agent allowed to spend?: Morphon consumes the identity credentials the agent already carries, whichever scheme issued them, and resolves them to the legal person who is accountable.
Is this payment within policy?: Limits, allowlists, velocity, jurisdiction and purpose, evaluated in Cedar against a rule set identified by its own hash. You can prove which rules were in force on any date.
Can anyone reconstruct it later?: Every decision, including every refusal, is written to a hash-chained log with field-level commitments, so you can disclose part of it without breaking the proof.

Install

npm install morphon

import { seal, verifyChain } from "morphon";

const event = seal(decision, previousHash);
const failures = verifyChain(events);   // [] when intact

Apache 2.0, and the specification is open for anyone to implement, including competitors. A record format is only worth having if everyone uses the same one.

What Morphon does not do

Hold funds, keys or cryptoassets
Sign or broadcast a transaction
Initiate a payment on anyone's behalf
Sit in the critical path unless you explicitly put it there

Morphon returns a verdict. Your own code signs. New integrations run in advisory mode, where the verdict is recorded and your systems are not bound by it, until you choose otherwise.

Why the log cannot be edited

UK record-keeping rules require that a record be reconstitutable, and that changes, corrections and prior contents remain identifiable. Most payment audit logs fail that, because they update rows.

Morphon has no update and no delete. A correction is a new event that references the original and commits to the value it replaces. The chain keeps both.

Payments carry a counterparty class, and one value is self. Most agent payment volume observed in public is circular. A monitoring product that cannot separate real third-party spend from an operator moving money between its own addresses is not monitoring anything.

Read the specification

MAE 0.2 is a draft. It covers the event envelope, the vocabulary of purpose codes and counterparty classes, chain and checkpoint integrity, selective disclosure, and export profiles that render the log into the evidence a given regulator expects.

Specification · Source · npm