Live today

Preflight

Before a transaction is signed, Metera reads the exact bytes, simulates them, and returns one verdict with the reasons behind it.

What it does

Your agent hands Metera the transaction it is about to sign, the intent behind it (the pool, the output token, exact in or exact out, the minimum it accepts) and the policy it must meet. Metera checks the transaction against all three and answers with a single decision.

The three verdicts

• allow: everything checked out; sign it.
• allow_with_caveat: nothing failed, but something is worth knowing before signing. The reason is attached.
• refuse: something did not hold up. Every refusal names its reason and the layer that raised it.

What comes back

The decision, the reasons (from the checks and from your policy), the level each read reached, the scope of what the verdict covers and does not cover, and a self-contained proof of what was simulated: the message hash, the slot, and what each node returned.

What it covers today

Solana swap transactions on direct Raydium CPMM and Meteora DAMM V2 pools. Jupiter-routed transactions and Transaction v1 are not covered yet and are refused rather than guessed at.