by agi-inc
Common interface for interacting with AI agents. The protocol is tech stack agnostic - you can use it with any framework for building agents.
# Add to your Claude Code skills
git clone https://github.com/agi-inc/agent-protocolMaintained by <a href="https://agi.tech" target="_blank">AGI, Inc.</a>
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.
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 [OpenA...