For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Action Gateway connects applications and agents to catalog tools, with session-scoped access and provider credentials resolved at execution time.

• Managed MCP endpoint: Connect a coding agent or application to a session-specific MCP URL, or use the Python or TypeScript SDK.

• Tool catalog: Discover tools for external services and DigitalOcean resources with action_search, or register your own MCP server.

• Tool and code execution: Invoke tools individually or in parallel with action_invoke. Use action_code for Python computation and workflows combining tools.

• Credential isolation: Credentials for tools accessed through Action Gateway never enter the model context. Secrets and tokens are stored in DigitalOcean Secrets Manager and resolved when the tool executes.

• Toolbelts: Group tools into a versioned Toolbelt for session selection, group permissions, and preloading. Pin the Toolbelt version to keep its member selection stable.

• Session controls: Set tool policies, actor identity, instructions, preloaded tools, and an optional VPC attachment for code execution and the region of private tool calls. Use output views to trim tool results.

• Private tools: Connect providers in a VPC using connections with explicit destination hosts and ports. VPC networking must be enabled for your team and is available in ric1.

• Reliable execution: Apply bounded retries and provider idempotency according to each tool’s supported execution policy.

• Insights: Every tool call is traced. View request volume, success rate, tool usage, and provider latency on the Insights tab under Action Gateway in the Control Panel.