​

Overview

Use the Execution (Orderbook) API through gRPC OrderbookService to discover markets, place and manage orders, request quotes, and monitor settlement-related activity in the orderbook. Execution API powers these user flows:

• buy CC via RFQ;
• sell CC via RFQ;
• run as an LP or market-maker;
• monitor settlement-related execution activity.

​

API Surface

Below are the Execution (Orderbook) API sections.

​

Instruments and Markets

Start every trading flow by loading instruments and markets. This is the standard initialization path for takers, LPs, and custom agents. It is also the natural first step before quoting, placing orders, or building routing logic.

​

Use cases:

• populate market selectors in the UI;
• validate tradable pairs such as CC-USDC .

initialize trading agents with supported markets.

​

Endpoint:

​

Orders

Use the Orders endpoints to place and manage orderbook orders. This is the core execution path for maker strategies and long-running LP agents. In long-running mode, the cloud agent places grid orders on configured markets and continuously manages them.

​

Use cases:

• submit maker quotes as resting orders;
• review filled, open, or canceled orders;
• update strategy state after order changes.

​

Endpoints:

​

Orderbook Depth and Streams

Use market data endpoints to read Silvana Book’s live state. The standard pattern is snapshot plus stream:

1. fetch a current depth snapshot;
2. subscribe to updates;
3. maintain an in-memory live book view.

​

Use cases:

• render live orderbook depth in a UI;
• feed strategy engines and market-making bots;
• track execution conditions before sending orders or RFQs.

​

Endpoints:

​

RFQ

RFQ is the primary taker execution flow in the repo. The CLI buy and sell flows are built on this model. For example, buying CC on CC-USDC requests quotes, selects the best offer, and continues into settlement. The repo also notes that the buy flow repeats until the full requested amount is filled.

​

Use cases:

• one-off taker execution;
• best-quote selection across LPs;
• RFQ monitoring and trade audit trails.

​

Endpoints:

​

Settlement Proposals

Execution continues beyond quote acceptance. After a trade is agreed, clients can inspect the settlement-related execution state through the settlement proposal endpoints. This is useful for agents that need to react to proposed settlements, automate post-trade handling, or surface trade progress in a UI.

​

Use cases:

• monitor execution progress after RFQ acceptance;
• trigger downstream post-trade logic;
• power execution status views.

​

Endpoints:

​

Liquidity Providers and Rounds

The Execution API also exposes metadata about the network environment. These endpoints are useful for analytics, routing decisions, and understanding how liquidity is distributed across the execution environment.

​

Use cases:

• discover available quoting counterparties;
• enrich execution dashboards;
• drive market-maker or taker routing logic.

​

Endpoints:

​

Parties

The orderbook tracks a party record for each authenticated trading entity. Use these endpoints to onboard, edit, deactivate, and inspect parties.

​

Use cases:

• onboard a new party before its first order;
• edit display metadata or settings;
• inspect counterparty info for execution and audit views;
• review historical activity tied to a party.

​

Endpoints:

​

Invites and Waiting List

Onboarding into the orderbook is gated by invites and a waiting list during the early-access phase.

​

Use cases:

• queue a new user for access via the waiting list;
• look up an invite issued to the authenticated user;
• redeem an invite to complete onboarding.

​

Endpoints:

​

Example flow

A typical taker flow looks like this:

1. Call GetInstruments and GetMarkets to load tradable markets.
2. Call RequestQuotes for a market such as CC-USDC.
3. Review the returned quotes and call AcceptQuote on the best one.
4. Track settlement using settlement proposal endpoints and hand off completion to the ledger-backed settlement flow.