---
title: Action Gateway API Reference (public)
description: |-
    The Action Gateway API endpoints are organized into the following groups:
    Action Gateway (43 endpoints): Action Gateway gives AI agents governed …
product: Managed Agents
url: https://docs.digitalocean.com/products/managed-agents/action-gateway/reference/api/
last_updated: "2026-08-10"
---

> **For AI agents:** The documentation index is at [https://docs.digitalocean.com/llms.txt](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 API Reference (public)

Action Gateway gives applications and AI agents governed access to tens of thousands of tools through a managed MCP endpoint or SDK. See [What You Can Build](https://docs.digitalocean.com/products/managed-agents/agent-harness-runtime/details/what-you-can-build/index.html.md) for example use cases of Action Gateway with Harness Runtime.

The Action Gateway API endpoints are organized into the following groups:

- [**Action Gateway**](action-gateway/) (43 endpoints): Action Gateway gives AI agents governed access to tools over the Model Context Protocol (MCP). The `/v2/action-gateway` endpoints manage the tool catalog and the resources that control how agents use it:

  - **Tools** browse and search the catalog, its providers, and global provider and tool health.
  - **Toolbelts** are versioned, team-owned sets of tools that sessions and policies reference as `toolbelt:<name>@<version>`.
  - **Output views** reshape a tool’s output before it reaches the agent.
  - **MCP servers** register your own remote MCP servers and choose which of their tools to enable.
  - **Connections** authorize one of your end users to use a provider’s tools, for example through OAuth.
  - **Sessions** bind a tool selection and permission policy to an MCP URL that an agent connects to.
  - **Users** and **end user limits** show and limit activity per end user, identified by a session’s `actorId`.
- [**Action Gateway Data Plane**](action-gateway-data-plane/) (6 endpoints): The Action Gateway data plane finds and runs tools in a session. These endpoints are the REST forms of the session’s MCP meta tools:

  - `POST /tools/search` is `action_search`.
  - `POST /tools/invoke` is `action_invoke`.
  - `POST /code/execute` is `action_code`.