> For the complete documentation index, see [llms.txt](https://canary-1.gitbook.io/canary/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canary-1.gitbook.io/canary/pricing.md).

# Pricing

What Canary costs, how the fee is collected, and what it funds.

From 6 October 2026, Canary introduces a $1 onchain verification fee per message.

## What changes for applications

Nothing changes operationally. There are no integration changes, no billing setup, no invoices and no service interruption. The fee is collected onchain as part of the standard message cost.

## What it costs in context

Across Canary-secured traffic indexed on Dune, the average message represents about $33,000 in transaction value ($32,856 as of 7 October 2026). A $1 fee is roughly 0.003% of the value being verified, which is negligible against the financial and reputational cost of a single security incident.

| Measure                         | Figure        |
| ------------------------------- | ------------- |
| Fee per message                 | $1            |
| Average value per message       | About $33,000 |
| Fee as a share of average value | About 0.003%  |

## What the fee funds

Nearly two years of free verification proved the standard. The fee sustains it, and funds what comes next: broader Cipher rollout, custom verification hooks, multi-cloud and multi-hardware resilience, multiple independent TEE technologies, onchain zero-knowledge verification, continuous audits, and the next generation of application-specific security.

## Cipher and Cosigner

Higher-volume teams, protocols that need advanced Cipher capabilities, and issuers adopting Canary Cosigner work directly with Canary on tailored commercial agreements. To start a conversation, book a call at [canaryprotocol.com](https://www.canaryprotocol.com).