You can find more info in the docs.

The AI agent space is young. Most developers are building agents in their own way. This creates a challenge: It's hard to communicate with different agents since the interface is often different every time. Because we struggle with communicating with different agents, it's also hard to compare them easily. Additionally, if we had a single communication interface with agents, it'd also make it easier developing devtools that works with agents out of the box.

We present the Agent Protocol - a single common interface for communicating with agents. Any agent developer can implement this protocol. The Agent Protocol is an API specification - list of endpoints, which the agent should expose with predefined response models. The protocol is tech stack agnostic. Any agent can adopt this protocol no matter what framework they're using (or not using).

We believe, this will help the ecosystem grow faster and simplify the integrations.

We're starting with a minimal core. We want to build upon that iteratively by learning from agent developers about what they actually need.

• Ease with which you can use the benchmarks.
• Other people can more easily use and integrate your agent
• Enable building general devtools (for development, deployment and monitoring) that can be built on top of this protocol
• You don’t need to write boilerplate API and you can focus on developing your agent

Set a general simple standard that would allow for easy to use benchmarking of agents. One of the primary goals of the protocol is great developer experience, and simple implementation on the end of agent developers. You just start your agent and that’s all you have to do.

If you'd like to propose a change or an improvement to the protocol. Please follow the RFC template.

The most important part. It specifies which endpoints should the agent expose. The protocol is defined in OpenAPI specification.

Right now the protocol is defined as a REST API (via the OpenAPI spec) with two essential routes for interaction with your agent:

• POST /ap/v1/agent/tasks for creating a new task for the agent (for example giving the agent an objective that you want to accomplish)
• POST /ap/v1/agent/tasks/{task_id}/steps for executing one step of the defined task

It has also a few additional routes for listing the tasks, steps and downloading / uploading artifacts.

This is our implementation of the protocol. It’s a library that you can use to build your agent. You can use it, or you can implement it on your own. It’s up to you.

Using the SDK should simplify the implementation of the protocol to the bare minimum, but at the same time it shouldn't tie your hands. The goal should be to allow agent builders to build their agents and the SDK should solve the rest.

Basically it wraps your agent in a web server that allows for communication with your agent (and in between agents in the future).

This library should be used by the users of the agents. Your agent is deployed somewhere and the users of your agent can use this library to interact with your agent.

Thanks to the standard the users can try multiple agents without the need for any additional adjustments (or very minimal) in their code.

If you're an agent developer, you can use the SDK to implement the protocol. You can find more info in the docs or in the SDK folder.

• e2b
• Auto-GPT

• ✅ Auto-GPT
  • Track PR here
• ✅ Auto-GPT-Forge
• 🚧 babyagi
  • Track PR here. Waiting for merge.
• ✅ smol developer
  • Track PR here.
• 🚧 beebot
  • Might require more features. See issue here.

• Agent-to-agent communication
• Connection to the outside world:
  • 3rd party services (= “Agent I/O”)
  • Authentication on behalf of users
• Protocol Plugins
• Is there anything missing? Please submit an RFC with a proposed feature!

• PRs and issues are welcome!
• Join AIEF Discord and their dedicated agent-protocol channel
• Join Auto-GPT Discord and their dedicated agent-protocol channel
• Join e2b Discord and their dedicated agent-protocol channel