Everything a developer needs, in one place.
Quickstart, SDK reference, the gRPC surface, the agent crates and the security model. Links out to docs.silvana.one — this page exists so you do not have to hunt.
Zero to a running agent.
First run
The shortest path from an empty directory to an agent placing orders.
- SDK quickstartRunning agent, start to finish. Begin here if you are not sure where to begin.
- PrerequisitesToolchain, keys and accounts you need before the quickstart will work.
- Agent onboardingRegistering an agent identity and getting it authorised to trade.
- Sample agentThe smallest complete agent, annotated — a reference to copy from.
SDK or the raw API?
Both reach the same ledger. The difference is how much of the plumbing you want to own.
Silvana SDK
Use this if you are building an agent. It carries signing, key handling, order lifecycle, config and the CLI — and every catalogue agent is written against it, so a template is a working starting point rather than a sketch.
Rust crates, with local signing and no custody handover.
Agentic API (gRPC)
Use this if you are connecting an existing system. One typed interface for payments, transfers, DvP, multicall and settlement streams, callable from any language with a gRPC client.
You own the signing and the retry logic that the SDK would otherwise have handled.
The rest of it.
Silvana SDK
Building and configuring an agent.
- SDK introductionWhat the SDK covers, and the shape of an agent built on it.
- Silvana Book agentThe trading-specific layer: orders, fills, the book.
- Configuration referenceEvery setting an agent reads, and its default.
- Full CLI referenceEvery command, flag and subcommand.
- Trading modesHow an agent places into the book — and where RFQ fits.
Agentic API
Talking to Canton through one typed gRPC interface.
- Agentic API introductionThe typed gRPC surface: payments, transfers, DvP, multicall, settlement streams.
- Getting startedFirst call, with a working request.
- gRPC API typesMessage and service definitions.
- gRPC reflectionDiscover the surface from your own tooling instead of reading it here.
- Transaction flowPrepare, sign, execute — what happens between your call and settlement.
- Operation referenceEvery operation the API exposes, one page.
Keys, auth and hosting
Who can sign what, and where the agent runs.
Source and catalogue
Sixty-eight agents, every one a readable crate.
The fastest way to understand the SDK is to read an agent built on it. Each catalogue entry ships a crate, a doc.md and a running demo.
Full documentation.
Platform architecture, Silvana Book internals, proving, EarnHub rules and the parts of Silvana that have nothing to do with agents — all of it lives in the docs.
Open docs.silvana.one