Add External Agents to your Graph
Copy page
Learn how to configure and use external agents using the A2A protocol
External agents let you integrate agents built outside of Inkeep—using other frameworks or platforms—into your Graph. They communicate over the A2A (Agent‑to‑Agent) protocol so your Inkeep agents can delegate tasks to them as if they were native.
Any agent that exposes an A2A‑compatible HTTP endpoint can be integrated by providing its baseUrl
plus headers/auth (static or dynamic).
Learn more about A2A:
- A2A overview on the Google Developers Blog: A2A — a new era of agent interoperability
- A2A protocol site: a2a.how
Examples of platforms exposing agents via A2A (non‑exhaustive):
- LangGraph — listed among A2A‑compatible platforms: Partners and platforms
- CrewAI — listed among A2A‑compatible platforms: Partners and platforms
- Salesforce Agentforce — listed among A2A‑compatible platforms: Partners and platforms
Creating an External Agent
Every external agent needs a unique identifier, name, description, base URL for A2A communication, and optional authentication configuration:
External Agent Relationships
Agents can be configured to delegate tasks to external agents.
External Agent Options
Configure authentication and custom headers as needed (static values or dynamic context variables).
Parameter | Type | Required | Description |
---|---|---|---|
id | string | Yes | Stable agent identifier used for consistency and persistence |
name | string | Yes | Human-readable name for the external agent |
description | string | Yes | Brief description of the agent's purpose and capabilities |
baseUrl | string | Yes | The A2A endpoint URL where the external agent can be reached |
headers | object | No | HTTP headers to include with every request to the external agent. See Context Fetchers for details about dynamic variables. |
credentialReference | CredentialReference | No | Reference to dynamic credentials for authentication. See Credentials for details |