Connect
Create the local identity and configuration required to access the selected Silvana environment.
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.

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.
Create the local identity and configuration required to access the selected Silvana environment.
Set the market, strategy, size, limits, and signing behavior in one visible configuration.
Start a supported agent flow such as grid, market making, RFQ, taker, or LP mode.
Prepare sensitive actions before signing and keep authorization inside the approved environment.
Follow order, transaction, and settlement status through structured responses and event streams.
Move through environment selection, tooling, identity, onboarding, configuration, and the first verified run with links to the maintained docs.
Select the Silvana environment, endpoint, credentials, and asset context for the guide.
Install the supported CLI and SDK package for the current release.
Generate or provide the signing identity required by the onboarding flow.
Register the agent and write the local configuration used by the runtime.
Set the market, strategy, spread, size, limits, and signing behavior.
Start the agent, confirm connectivity, and follow the first execution or settlement events.
Keep the agent's environment, market, strategy, limits, signing mode, and runtime behavior visible in one reviewable configuration.
[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"The assets, pair, endpoints, and service environment the agent uses.
The operating mode and parameters that shape behavior.
The size, exposure, price, frequency, and timing boundaries.
Where authorization happens before state changing actions execute.
Logging, persistence, reconnect behavior, and event handling where supported.
The SDK reduces the amount of market, execution, signing, settlement, and runtime plumbing a team needs to rebuild before focusing on strategy logic.
Read market state, submit supported orders, manage order state, and receive execution events.
Request, receive, evaluate, and respond to quotes inside supported trading flows.
Run configured strategies that maintain orders as market conditions change.
Coordinate settlement so delivery and payment complete together when conditions are met.
Follow proposals, readiness, lifecycle events, and final outcomes.
Inspect prepared transactions before signing inside the approved environment.
Build beyond included flows with SDK components, typed clients, and signing helpers.
Once the first agent works, teams can move in one of four directions.
Use the Playground to test strategy behavior against mock market conditions.
Use the API Reference to understand services, transaction flow, streams, and response models.
Replace the included strategy with your own rules, models, data sources, or orchestration.
Run the same agent logic in the infrastructure model that matches your control boundary.
Complete the first working flow, adjust the configuration, then decide whether to customize the strategy, integrate through the API, or plan deployment.