Overview

Integrator's entry point — what you can build, and which surface to use

Chamber is a set of onchain vaults plus supporting infrastructure. Everything a manager or depositor does through the app is also available to integrators. This section is the developer reference.

If you're building a product that creates vaults, composes trades, reads vault state, or automates a strategy, you're in the right place.

What you can build

• Vault-backed products — consumer apps, yield strategies, and managed portfolios that wrap a Chamber vault. This is how Toros Finance is built.

• Automated managers — bots or agents that trade a vault within the Guard System's rules. See AI-assisted management for the product framing; the MCP server is the integration surface.

• Analytics and dashboards — vault discovery, performance tracking, leaderboards. The subgraph (per-chain, indexed) is the primary data source; the Data API is a lighter hosted GraphQL that aggregates across chains.

• Deposit and withdrawal flows — if you're embedding Chamber in another app, the SDK handles quoting and transaction construction in TypeScript; for other languages or lightweight clients, call the contracts directly.

The surfaces

Surface	Purpose	When to use
Contracts	The vault contracts themselves	Direct integration, custom tooling
SDK (@dhedge/v2-sdk)	TypeScript wrapper over the contracts	Building a full manager or wallet flow
Subgraph	Indexed vault, position, and transaction data	Analytics, UIs, leaderboards
Data API	Hosted GraphQL for cross-chain vault lists, prices, analytics	Lightweight read access without running a subgraph
MCP server	Model Context Protocol server for AI agents	AI-driven vault management

Before you start

Three things to know up front:

1. Everything flows through the Guard System. Your integration can only compose calls that a whitelisted contract guard will approve. If you're trying to interact with a protocol Chamber doesn't already support, the call will revert at the vault entrypoint. The integrator-facing guard page covers how to check what's supported on a given chain.

2. Chains are not uniform. The set of supported protocols, assets, and guards differs across chains. Always check the deployment matrix and contract addresses for the chain you're targeting before writing chain-specific logic.

3. Fees are settled in vault shares. Performance, management, entry, and exit fees are all minted as shares to the manager and DAO — not deducted from the deposit asset. If your UI shows fee impact, model it as share dilution. See fees & performance.

Quick start

The fastest path depends on what you're building:

• "I want to create and manage a vault programmatically" → SDK.

• "I want to query vault data" → Subgraph.

• "I want my users to deposit into an existing vault from my app" → SDK if TypeScript, or call the vault's deposit function directly (see contract addresses).

• "I want an AI agent to trade a vault" → MCP server.

• "I want end-to-end examples" → Integration examples.

Repositories

All integrator-facing code is open source:

• Contracts: github.com/dhedge/V2-Public

• SDK: github.com/dhedge/dhedge-v2-sdk (@dhedge/v2-sdk)

• Subgraphs: github.com/dhedge/dhedge-v2-subgraphs

• MCP server: @dhedge/chamber-mcp on npm

Support

• Discord — #developers channel

• GitHub issues on the relevant repo

• Security disclosures: see bug bounty

See also

• Guard system — the integrator-facing rules for what calls will succeed

• Concepts: vaults as guardrails — the model your integration is operating inside