# Tilde

Tilde is a cloud API for agents, MCP servers, managed credentials, tool calling, ChatKit messaging, signals, and team-scoped runtime agents.

## Primary Docs For Agents

- [Organization, team, auth](https://api.tilde.test/.agent/skills/org-team-auth.md)
- [Tool provider integration](https://api.tilde.test/.agent/skills/tool-provider-integration.md)
- [ChatKit, signals, messaging](https://api.tilde.test/.agent/skills/chatkit-signals-messaging.md)
- [Create and deploy an agent](https://api.tilde.test/.agent/skills/create-deploy-agent.md)
- [Slack bot agent](https://api.tilde.test/.agent/skills/slackbot-agent.md)
- [GitHub agent](https://api.tilde.test/.agent/skills/github-agent.md)
- [Agent-to-agent communication](https://api.tilde.test/.agent/skills/agent-to-agent-communication.md)
- [AI SDK compatible agent](https://api.tilde.test/.agent/skills/ai-sdk-compatible-agent.md)
- [Agent-maintained wiki](https://api.tilde.test/.agent/skills/agent-wiki.md)

## Machine Interfaces

- OpenAPI: `/api-docs/openapi.json`
- Global MCP: `/mcp`
- Team MCP: `/api/v1/team/{team_id}/mcp/mcp-server/{mcp_server_instance_id}/mcp`

Tilde exposes many third-party toolkit providers, reverse proxies, and proxied/custom MCP integrations. Do not hardcode a provider list. Discover provider and tool options at runtime with `tilde_search_available_capabilities`, inspect returned provider ids, credential source ids, schemas, and human approval requirements, then enable the selected provider with `tilde_enable_toolkit_provider` or the relevant custom/proxied MCP registration tool. Search configured team tools and reverse proxies with `tilde_search_enabled_capabilities` before creating or modifying MCP server exposure.

MCP server functions may run in the background. An asynchronous function call returns a function ticket immediately; call the built-in `tilde_poll_async_function_call` function with `function_ticket_id` to retrieve `processing`, `complete`, or `failed` status and its response data or error.

For `custom_json_schema` provider auth, render the returned server-authored schema as form fields and submit the resulting JSON object. Tilde validates and encrypts the complete credential payload.

Custom HTTP backend registration returns a one-time webhook signing key. Configure that key in the backend and redeploy it, then refresh discovery; initial registration can succeed before tools are discovered.

For personal MCP client onboarding, use a user-owned API key from User settings > API Keys or global MCP `tilde_generate_api_key`. Use Team settings > AI Agent API keys only for server agents that should authenticate as team-scoped machine users.

## Reverse Proxy

Reverse Proxy, formerly credential proxy, gives a team-scoped base URL for forwarding HTTP requests to an upstream API using Tilde-managed credentials. Common provider credentials can auto-create disabled reverse proxy profiles when the upstream credential can be injected safely into headers, cookies, or query parameters. Use `tilde_list_reverse_proxies` to find profiles and `tilde_set_reverse_proxy_enabled` to enable or disable traffic. Disabled profiles do not forward requests. GitHub, Stripe, and Google Workspace reverse proxies use bearer-token style credentials; OAuth profiles require a linked user credential, not only the OAuth client credential.

## Signals And Wallets

Use `tilde_list_signal_providers`, `tilde_create_signal_provider`, `tilde_create_signal_rule`, `tilde_list_signal_deliveries`, and `tilde_retry_signal_delivery` for event routing workflows. Use wallet tools such as `tilde_create_wallet_customer`, `tilde_create_wallet`, `tilde_get_wallet_balances`, and the explicit payment tools only when the user asks for wallet or payment actions.

## Web Browser And Secure Credentials

Use global MCP `/mcp` or a team Tilde MCP server to configure Web Browser automation. Call `tilde_create_browser` to create a browser and its `Tilde Browser - {name}` tool provider. Call `tilde_create_browser_credential_approval` to get a secure approval URL for the human to enter credential values; never ask the agent to collect passwords, payment cards, or TOTP seeds in tool arguments. After the human completes the approval, call `tilde_link_browser_credentials` with the returned managed credential id to surface that credential in the browser.

## Agent Wikis

Create a team wiki with `tilde_create_wiki`, map selected functions from its private `Tilde Wiki - {name}` provider to an MCP server, and give that server to an agent. Wiki page writes use optimistic revisions; relationship types give graph edges forward, inverse, or symmetric meaning; asset Markdown uses stable `tilde://wiki/assets/{asset_id}` references. Built-in Code and Company Brain ontology templates install coherent page and relationship schemas, and wiki definitions are portable through Tilde state. Read [agent-maintained wiki](https://api.tilde.test/.agent/skills/agent-wiki.md) before automating wiki maintenance.

## Temporary Agent Accounts

Create one without human interaction with `POST /api/v1/identity/temporary-accounts`. It returns a 24-hour temporary org/team, temporary machine API key, 1-hour claim URL, and 6-digit PIN. Humans claim at `/temporary-accounts/claim/{token}` while signed in; claim transfers the temporary team/resources into the human org and revokes temporary credentials.