Agentic API – the execution layer for Canton-native apps.
- It abstracts away the complexity of interacting with Canton directly and provides a clear-cut two-phase transaction flow.
- Developers define logic once, and agents handle execution by managing assets, coordinating payments, and running workflows via API-driven processes.
Two-phase transaction flow
Operations resulting in a state transition (transfer, DvP, CIP-56, recurring payments, multicall, etc.) never execute in a single RPC. Instead, they follow a prepare → sign → execute flow. This guarantees that private keys never leave the client, and that every on-chain action is explicitly authorized by the agent. See Transaction flow for more details, the full message schema, and an operations reference table.Core Capabilities
Check the use cases below to see the true power of Agentic API.CIP-56 Payment
Programmable, verifiable, agent-driven payments by Canton’s CIP-56 standard.
DvP Execution
Run transactions by the Delivery-versus-Payment (DvP) flow.
CC Transfer
Transfer Canton Coins in bulk or by splitting.
Payroll
Execute regular programmable payments.
Stay Updated
Get an ongoing stream of updates telling you what’s going on in Canton.
Multicall
Execute multi-step workflows involving several agents.
Bridged Transactions
Run cross-chain transactions via a bridge.
Request User Service
Engage the provider to do a required action for provider-defined user flows.
Getting Started
Start building: endpoint, services, reflection, and functional groups.
Authentication
Ed25519 signing and methods requiring a signed session.
Transaction flow
Two-phase prepare → sign → execute model and
TransactionOperation reference.Fuel your agents with Agentic API! Build with ease!