SDK Guide

Build your first agent.

Follow one guided path from local setup to a working agent that can observe a market, act within defined limits, and follow execution through settlement.

Build an agent visual

From agent.toml to a running strategy.

What you will build

A functioning agent, not a disconnected demo.

By the end, the agent can connect to Silvana, read supported market state, apply configured strategy logic, submit supported actions, and track execution and settlement events.

Connect

Create the local identity and configuration required to access the selected Silvana environment.

Configure

Set the market, strategy, size, limits, and signing behavior in one visible configuration.

Run

Start a supported agent flow such as grid, market making, RFQ, taker, or LP mode.

Verify

Prepare sensitive actions before signing and keep authorization inside the approved environment.

Track

Follow order, transaction, and settlement status through structured responses and event streams.

Quickstart

From setup to first run.

Move through environment selection, tooling, identity, onboarding, configuration, and the first verified run with links to the maintained docs.

01

Choose the environment

Select the Silvana environment, endpoint, credentials, and asset context for the guide.

Open Environment Docs
02

Install the tooling

Install the supported CLI and SDK package for the current release.

Open CLI Reference
03

Create the local identity

Generate or provide the signing identity required by the onboarding flow.

Review Signing
04

Onboard the agent

Register the agent and write the local configuration used by the runtime.

Open Onboarding
05

Configure the mandate

Set the market, strategy, spread, size, limits, and signing behavior.

Open Configuration
06

Run and verify

Start the agent, confirm connectivity, and follow the first execution or settlement events.

Start Quickstart
Agent.toml

One file. Clear intent.

Keep the agent's environment, market, strategy, limits, signing mode, and runtime behavior visible in one reviewable configuration.

Example structureagent.toml
[environment]
network = "[SUPPORTED_NETWORK]"

[market]
pair = "CC/USDC"

[strategy]
mode = "grid"
levels = 6
spread = 0.004
size = 250

[limits]
max_order_size = "[VALUE]"
max_position = "[VALUE]"

[signing]
mode = "local"
01

Market

The assets, pair, endpoints, and service environment the agent uses.

02

Strategy

The operating mode and parameters that shape behavior.

03

Limits

The size, exposure, price, frequency, and timing boundaries.

04

Signing

Where authorization happens before state changing actions execute.

05

Runtime

Logging, persistence, reconnect behavior, and event handling where supported.

Included

Start with the infrastructure already solved.

The SDK reduces the amount of market, execution, signing, settlement, and runtime plumbing a team needs to rebuild before focusing on strategy logic.

Orderbook access

Read market state, submit supported orders, manage order state, and receive execution events.

RFQ trading

Request, receive, evaluate, and respond to quotes inside supported trading flows.

Grid and market making

Run configured strategies that maintain orders as market conditions change.

DvP settlement

Coordinate settlement so delivery and payment complete together when conditions are met.

Settlement streams

Follow proposals, readiness, lifecycle events, and final outcomes.

Local signing

Inspect prepared transactions before signing inside the approved environment.

Reusable components

Build beyond included flows with SDK components, typed clients, and signing helpers.

Next step

Keep the working path. Replace the strategy.

Once the first agent works, teams can move in one of four directions.

01

Simulate behavior

Use the Playground to test strategy behavior against mock market conditions.

02

Integrate directly

Use the API Reference to understand services, transaction flow, streams, and response models.

03

Build custom logic

Replace the included strategy with your own rules, models, data sources, or orchestration.

04

Choose deployment

Run the same agent logic in the infrastructure model that matches your control boundary.

Start building

Move from guide to your own agent.

Complete the first working flow, adjust the configuration, then decide whether to customize the strategy, integrate through the API, or plan deployment.