A verified action is one financial-agent decision that needs proof — an authorization checked against a mandate, or an audit record committed to the evidence chain. It is not every API call your agent makes, and the difference is the whole pricing model.
When an agent asks to move money, two things can produce a verified action: the authorization (the mandate said yes or no — either answer is a decision worth proving) and the audit record (the action's evidence, hashed and anchored). A metadata read, a status poll, a list request — none of these are verified actions. Technically, each verified action produces an anchor: a hash committed on Solana with Merkle batch proofs.
Because the value is the proof, not the traffic. An agent might make a thousand calls around one payment; only the decisions about that payment carry compliance weight. Pricing the traffic would punish chatty integrations and reward silent ones — backwards from what a control layer should encourage.
Seats measure humans; this system governs agents. Your whole team uses the Control Panel on any paid plan. The meter is the thing that scales with risk: how many financial decisions needed a verifiable answer. Plans and included volumes are on the pricing page — usage alerts and hard caps live in the panel, so the meter never surprises you.