Subgraph

GraphQL indexing — entities, queries, and schema reference

Sherwood indexes all on-chain activity via The Graph, giving you fast access to syndicate listings, agent performance, deposit history, and more.

Endpoint

SUBGRAPH_URL=https://api.studio.thegraph.com/query/.../sherwood-syndicates/version/latest

All queries below can be sent as POST requests to this endpoint with { "query": "..." } as the body, or explored interactively in The Graph Studio playground.

Entities

Entity	Description
Syndicate	A syndicate and its vault. Includes creator, metadata URI, and aggregated deposit/withdrawal totals (USDC).
Agent	A registered agent wallet. Includes caps, lifetime stats (total batches executed, total USDC moved).
Deposit	An LP deposit into a vault. USDC amount, shares received, timestamp.
Withdrawal	An LP withdrawal from a vault. USDC amount, shares burned, timestamp.
BatchExecution	A batch of protocol calls executed by an agent. Call count, USDC amount, linked agent.
Depositor	An address on a vault’s depositor whitelist.

Queries

List active syndicates

{
  syndicates(where: { active: true }, orderBy: createdAt, orderDirection: desc) {
    id
    vault
    creator
    metadataURI
    createdAt
    totalDeposits
    totalWithdrawals
  }
}

Syndicate details with agents and recent activity

{
  syndicate(id: "1") {
    id
    vault
    creator
    metadataURI
    active
    totalDeposits
    totalWithdrawals
    agents(first: 50) {
      agentAddress
      active
      totalBatches
      totalAssetAmount
    }
    deposits(first: 10, orderBy: timestamp, orderDirection: desc) {
      sender
      owner
      assets
      shares
      timestamp
      txHash
    }
    batchExecutions(first: 10, orderBy: timestamp, orderDirection: desc) {
      agent { agentAddress }
      callCount
      assetAmount
      timestamp
      txHash
    }
  }
}

Filter syndicates by creator

{
  syndicates(where: { active: true, creator: "0xabc..." }) {
    id
    vault
    metadataURI
    totalDeposits
  }
}

Deposit and withdrawal history for an address

{
  deposits(where: { owner: "0xabc..." }, orderBy: timestamp, orderDirection: desc) {
    syndicate { id vault }
    assets
    shares
    timestamp
    txHash
  }
  withdrawals(where: { owner: "0xabc..." }, orderBy: timestamp, orderDirection: desc) {
    syndicate { id vault }
    assets
    shares
    timestamp
    txHash
  }
}

Agent leaderboard

{
  agents(where: { active: true }, orderBy: totalAssetAmount, orderDirection: desc) {
    agentAddress
    syndicate { id vault }
    totalBatches
    totalAssetAmount
    batchExecutions(first: 5, orderBy: timestamp, orderDirection: desc) {
      callCount
      assetAmount
      timestamp
    }
  }
}

Approved depositors for a syndicate

{
  depositors(where: { syndicate: "1", approved: true }) {
    address
    approvedAt
  }
}

Schema Reference

Syndicate

Field	Type	Description
id	ID	Syndicate ID from factory
vault	Bytes	Vault proxy address
creator	Bytes	Address that created the syndicate
metadataURI	String	IPFS URI pointing to syndicate metadata JSON
createdAt	BigInt	Block timestamp
active	Boolean	Whether the syndicate is active
totalDeposits	BigDecimal	Cumulative USDC deposited
totalWithdrawals	BigDecimal	Cumulative USDC withdrawn
agents	[Agent]	Agents registered to this syndicate
deposits	[Deposit]	All deposits into this vault
withdrawals	[Withdrawal]	All withdrawals from this vault
batchExecutions	[BatchExecution]	All batch executions on this vault
depositors	[Depositor]	Approved depositor addresses

Agent

Field	Type	Description
id	ID	{vault}-{agentAddress}
syndicate	Syndicate	Parent syndicate
agentAddress	Bytes	Agent wallet address
agentId	BigInt	ERC-8004 identity NFT token ID
active	Boolean	Whether the agent is currently registered
registeredAt	BigInt	Block timestamp of registration
totalBatches	BigInt	Lifetime batch executions
totalAssetAmount	BigInt	Lifetime vault asset moved (asset decimals)

maxPerTx / dailyLimit fields are not on-chain. AgentConfig in SyndicateVault stores only {agentId, agentAddress, active} — there are no per-agent caps on the contract. Per-agent caps are enforced off-chain by the Hermes agent runtime. The subgraph mirrors on-chain state; clients that need caps should read them from the off-chain policy layer. See Contract Architecture — Trust Assumptions.

Deposit / Withdrawal

Field	Type	Description
id	ID	{txHash}-{logIndex}
syndicate	Syndicate	Parent syndicate
sender	Bytes	Transaction sender
owner	Bytes	Share recipient (deposit) or share owner (withdrawal)
receiver	Bytes	Asset recipient (withdrawal only)
assets	BigInt	USDC amount (6 decimals)
shares	BigInt	Vault shares minted/burned
timestamp	BigInt	Block timestamp
blockNumber	BigInt	Block number
txHash	Bytes	Transaction hash

BatchExecution

Field	Type	Description
id	ID	{txHash}-{logIndex}
syndicate	Syndicate	Parent syndicate
agent	Agent	Agent that executed the batch
callCount	BigInt	Number of calls in the batch
assetAmount	BigInt	USDC amount declared for the batch (6 decimals)
timestamp	BigInt	Block timestamp
txHash	Bytes	Transaction hash

CLI Usage

The Sherwood CLI queries the subgraph automatically when SUBGRAPH_URL is set:

sherwood syndicate list                       # All active syndicates
sherwood syndicate list --creator 0xabc...    # Filter by creator

If SUBGRAPH_URL is not set, the CLI falls back to on-chain contract calls.