> ## Documentation Index
> Fetch the complete documentation index at: https://trytilde.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Registry

> Register agents built in any framework, and route every request, tool call, and LLM request through the gateway. Centralise agent governance through predictable policy management.

## Supported frameworks

You build agents in the framework you already use. Tilde provides a core SDK in TypeScript and Python, plus an adapter package for all major frameworks. See [Framework integrations](/docs/frameworks/overview) for how each one works, and which features it supports.

<Tabs>
  <Tab title="TypeScript">
    | Framework | Adapter package |
    | - | - |
    | Vercel AI SDK | `@trytilde/sdk-vercel-ai-node` |
    | OpenAI Agents SDK | `@trytilde/sdk-openai-agents-node` |
    | Mastra | `@trytilde/sdk-mastra-node` |
    | LangChain and LangGraph | `@trytilde/sdk-langchain-node` |
  </Tab>

  <Tab title="Python">
    | Framework | Adapter package |
    | - | - |
    | LangChain and LangGraph | `trytilde-langchain` |
    | Agno | `trytilde-agno` |
    | OpenAI Agents SDK | `trytilde-openai-agents` |
    | Pydantic AI | `trytilde-pydantic-ai` |
    | CrewAI | `trytilde-crewai` |
  </Tab>
</Tabs>

<Info>
  Tilde is framework agnostic. If your framework is not on this list, you can still use the core SDK today, and we can add an adapter for it.
</Info>

Each adapter converts Tilde message history, tools, and skills into the framework's own types, and registers the framework's prompts at deploy time. The core SDK has one contract, `run(context)`, and depends on no agent framework.

## What the SDK does

The Tilde SDK wraps your agent and turns it into a deployable unit. You can ship it in two ways:

* **A standalone container** that runs on any platform that supports Docker containers, such as Kubernetes or Amazon ECS.
* **An AWS Lambda function** that the gateway invokes on demand.

Once you register the agent, Tilde acts as a secure proxy and central hub. Three kinds of data start flowing through it:

* Every request to the agent, from any [chat channel](/docs/chat-channels).
* Every sensitive side effect, such as [tool calls](/docs/tools/overview) and requests to [LLM providers](/docs/inference-providers).
* The [prompts](/docs/prompts/overview) and [skills](/docs/skills/overview) the agent uses, versioned with each deployment.
* All logs, traces, and other instrumentation that describe the agent's health. See [Sessions](/docs/sessions) and [Traces](/docs/traces).

## Agent lifecycle

<img src="https://mintcdn.com/tilde/UIZH9VuZaVUMv6QU/images/agent-lifecycle.drawio.svg?fit=max&auto=format&n=UIZH9VuZaVUMv6QU&q=85&s=d9625e9157ecf61e5c25a9886eb91a7e" alt="Sequence of an agent connecting to the Tilde gateway, registering, receiving an invocation with a short-lived token, and proxying tool calls, LLM requests, and telemetry back through the gateway" width="1463" height="793" data-path="images/agent-lifecycle.drawio.svg" />

<div className="zoom-hint"><Icon icon="magnifying-glass-plus" size={13} /> <em>Click to zoom</em></div>

<Steps>
  <Step title="The agent connects out">
    On deployment, your agent exposes no endpoints. It opens a secure HTTP/2 stream to the Tilde gateway, or to its [sidecar](/docs/deployment/sidecar-agents).
  </Step>

  <Step title="Tilde registers the deployment">
    When the stream is established, Tilde marks the deployment as connected. After the agent reports healthy, [routing](/docs/routing) sends new conversations to it.
  </Step>

  <Step title="The gateway issues a token for each invocation">
    Every request to your agent reaches the gateway first. The gateway issues a short-lived, signed token and forwards the token and the request to the agent over the HTTP/2 stream.
  </Step>

  <Step title="The agent works through the gateway">
    The agent uses the token to proxy all tool calls and LLM inference requests, and to send OpenTelemetry logs and traces. The token lasts minutes, and the SDK renews it while the invocation is active.
  </Step>

  <Step title="Responses stream back">
    All responses stream back through the gateway to the end user.
  </Step>
</Steps>

## Why Tilde works this way

The agent container never exposes an HTTP endpoint, so there is nothing on it to attack. The agent also holds no provider credentials.

That leaves one place to govern [IAM](/docs/iam), [security middleware](/docs/security/middleware), [secrets](/docs/security/secret-encryption), and [budgets](/docs/inference-providers#budgets): the gateway. A policy change applies to every agent at once, whatever framework it uses.

## Next steps

<Columns cols={2}>
  <Card title="Deploy a direct agent" href="/docs/deployment/direct-agents">
    Connect your first agent to the gateway.
  </Card>

  <Card title="Release from CI" href="/docs/deployment/ci-cd">
    Register deployments from your pipeline.
  </Card>
</Columns>