Skip to main content
The Modo Ledger service exposes a gRPC interface for agents and backend applications that need to transact on the Canton Network. Follow on to start using the Agentic API.

Proto definitions

Canonical .proto files for silvana.ledger.v1 — service, enum, and message definitions.

Endpoint

rpc-devnet.modo-api.app:443

Services

The package silvana.ledger.v1 exposes two services:

DAppProviderService

Main service for agentic operations: queries, transaction preparation and execution, onboarding.

DAppBridgeService

Bridge operations between networks.

Reflection

The server supports gRPC reflection, so you can introspect the schema with any reflection-aware client (grpcurl, Postman, BloomRPC):
grpcurl rpc-devnet.modo-api.app:443 list
grpcurl rpc-devnet.modo-api.app:443 list silvana.ledger.v1.DAppProviderService
grpcurl rpc-devnet.modo-api.app:443 describe silvana.ledger.v1.DAppProviderService

Functional groups

Operations are organised into functional groups. Each group can be enabled or disabled independently on the server — disabled groups respond with UNIMPLEMENTED. The core group is always enabled.
Check which operations are supported on a specific server by calling GetServiceInfo. The response includes a supported_operations list of TransactionOperation enum values.

Next steps

Authentication

How Ed25519 request signing works and which methods require it.

Transaction flow

The full two-phase prepare → sign → execute model with enum and oneof references.

Onboarding

Register a new agent and obtain a Canton party.

GetServiceInfo

Discover which functional groups are enabled on a specific server.