Know Your Agent
Know which agents a run records, inspect its steps, and check the signed receipt yourself. Metaorcha provides an open format, an offline verifier and a local playground for exploring that evidence.
What you can do today
Connect agents and tools
Register an agent with the SDK and route work through MCP, A2A and computer-use handlers. Run the stack locally with configured model access; the bundled finance and browser examples use simulated outputs.
Check a portable receipt
A run envelope binds ordered step hashes, a Merkle root and an Ed25519 signature. Download the JSON and verify it independently of the runtime that produced it.
Test a settlement gate
When enabled, the settlement gate requires a valid receipt matching the expected run, charter and signer profile. The local demonstration uses mock payments: a valid run settles and a tampered receipt is refused.
Change a receipt.
See verification fail.
Install Python 3.12+ and uv, then run this local simulation from source. It needs no model key, database or running harness.
- Open 127.0.0.1:8040 and confirm the mode is sim.
- Choose Golden: valid, then Golden: tampered to compare the verdicts.
- Run agent to build a simulated step chain. Choose Copy → verifier, change a step value, and verify again.
- Download the original envelope. Run the CLI command in a second terminal to check the same receipt offline.
Start the local playground
git clone https://github.com/solvent-labs-org/metaorcha.git
cd metaorcha
uv sync --all-packages
cd apps/attestation-playground
PLAYGROUND_MODE=sim uv run uvicorn playground.main:app --host 127.0.0.1 --port 8040Verify a downloaded receipt
# From the cloned metaorcha repository, in a second terminal:
uv run --package orcha-sdk orcha-sdk verify /path/to/envelope.jsonUse the SDK from this checkout for the new verifier. Dependency installation may use the network; verification itself does not. Exit code 0 means valid, 1 means invalid, and 2 means an input or usage error.
What a receipt proves
Use it for reproducible integrity checks, integration tests and reviewing an agent run with another person. Define your outcome and acceptance criteria separately, then collect the evidence needed to judge them.
- Integrity is not correctness. A valid receipt does not prove the answer is true, the task succeeded, or all real-world activity was recorded.
- The offline verifier checks the embedded public key. It does not resolve the signer DID or independently establish who controls that key; signer trust must be checked separately.
- The playground quickstart runs a local simulation. It performs no real agent task and moves no real money. Running the full harness needs service configuration and model access.
- Run attestation and settlement gating are opt-in. This release is a developer toolkit; hosted execution, production readiness and a public agent network are not promised.