Skip to main content

Venues

A venue is a single node on the Grid — a self-contained server that hosts operations, runs agents, and persists state. It has a DID identity, a content-addressed asset store, and a job engine, and it exposes the same capabilities over REST, MCP, A2A, and DID. Run one with a single command; see the operator guide.

What a venue hosts​

  • Operations — self-describing, invocable capabilities provided by pluggable adapters (LLMs, HTTP, files, orchestration, cross-venue federation, and more).
  • Agents — persistent, stateful actors that hold sessions, call tools, and produce auditable results.
  • Assets — immutable, content-addressed artifacts and data.
  • Jobs — the execution record for every invocation, poll-able and streamable over SSE.

Governance is per-venue​

Each venue operator decides their own policy. A venue controls its own authentication (public, OAuth, bearer/UCAN tokens), enforces capabilities on every request, and keeps its data where it is governed — other venues see only the results of operations they're permitted to invoke. This is what lets venues federate across organisational and jurisdictional boundaries without centralising control.

Where to go next​

  • Run a venue — get one running locally or in a container
  • Adapters — what a venue can do out of the box
  • Agents — build stateful, tool-using agents
  • Grid — how venues federate