API Reference

The Silvana execution surface.

Silvana exposes typed gRPC services for market access, Canton operations, settlement, pricing and agent inputs. Use this page to understand how the pieces fit, then open the full reference for exact methods and schemas.

Agentic API visual

Defined in proto. Streamed to agents. Signed in your environment.

Start at the right layer

Use the interface that matches the work.

SDK

Use the SDK when you want the fastest path to a working agent with configuration, clients, signing helpers and established workflow patterns.

Best for: running an agent quickly

Direct gRPC

Use generated clients and the proto surface when your backend needs direct control over service calls, state, retries and workflow composition.

Best for: custom backend integration

Product integration

Use the Platform and Agentic API pages when you are still deciding which execution capability belongs inside the product.

Best for: product planning

Service surface

Five service families. One operating model.

The public service map reflects the maintained proto definitions and documentation.

Orderbook Service

Submit and manage orders, read market data, initiate private RFQ workflows and subscribe to execution events.

Use when: an agent or application interacts with Silvana Book.

Settlement Service

Coordinate settlement proposals, allocation readiness, lifecycle events and final outcomes for supported DvP workflows.

Use when: the product needs to follow the trade beyond matching.

Ledger and Execution

Read supported Canton state, onboard agents, prepare transactions, execute signed operations and return structured results.

Use when: an agent or backend performs state changing Canton operations.

Pricing Service

Receive supported price and quote data for strategy evaluation, RFQ logic, monitoring and execution decisions.

Use when: the agent requires approved price context.

News and Signal Services

Receive supported product, protocol or event information through feed or streaming interfaces where available.

Use when: informational inputs are part of a wider decision model.

State changing operations

Prepare. Verify. Sign. Execute. Reconcile.

Every material state change follows the same controlled path.

01

Prepare

Send a typed operation and parameters. Silvana returns the prepared payload, hash, identifiers and available estimates.

02

Verify

Confirm the operation, asset, amount, recipient, permissions and expected outcome inside the client environment.

03

Sign

Sign the prepared transaction hash inside the approved environment. Private key material remains there.

04

Execute

Submit the transaction identifier and signature through the relevant execution service.

05

Reconcile

Store the returned update identifier, status, created records, usage information and errors.

Build by outcome

Start with what the integration needs to do.

01

Build a trading agent

Use orderbook access, market data, RFQ, settlement events, transaction preparation and local signing.

Start with: SDK Guide

Also useful: Orderbook Service, Settlement Service

02

Add Canton operations to an application

Use the execution surface to prepare and execute payments, transfers, DvP, multicall and supported application workflows.

Start with: Agentic API docs

Also useful: Ledger and Execution

03

Coordinate DvP settlement

Follow proposals, readiness, authorization and final outcomes across the settlement lifecycle.

Start with: Settlement documentation

Also useful: Transaction flow

04

Build reconciliation into a product

Store update identifiers, status, created records, lifecycle events and structured errors as part of the application data model.

Start with: Response documentation

Also useful: Streaming guides

05

Inspect the live schema

Use service information and gRPC reflection to discover what the selected environment exposes.

Start with: Reflection guide

Also useful: Service information

Start with the surface

Choose the service. Build the first call.

Open the full reference for exact schemas, or follow the SDK Guide when the goal is a running agent rather than a direct service integration.