Documentation
Supported Frameworks
Planned for Support (Contributions Welcome!)
Open Github tickets for new frameworks
Requirements
- Python 3.11 or newer
Quickstart
Refer to pyproject.toml for a list of the options available. Update your pip install command to include the frameworks that you plan on using:
pip install 'any-agent'
To define any agent system you will always use the same imports:
from any_agent import AgentConfig, AnyAgent
For this example we use a model hosted by Mistral, but you may need to set the relevant API key for whichever provider being used. See our Model Configuration docs for more information about configuring models.
export MISTRAL_API_KEY="YOUR_KEY_HERE" # or OPENAI_API_KEY, etc
from any_agent.tools import search_web, visit_webpage
agent = AnyAgent.create(
"tinyagent", # See all options in https://mozilla-ai.github.io/any-agent/
AgentConfig(
model_id="mistral:mistral-small-latest",
instructions="Use the tools to find an answer",
tools=[search_web, visit_webpage]
)
)
agent_trace = agent.run("Which Agent Framework is the best??")
print(agent_trace)
Cookbooks
Get started quickly with these practical examples:
- Creating your first agent - Build a simple agent with web search capabilities.
- Creating your first agent evaluation - Evaluate that simple web search agent using 3 different methods.
- Using Callbacks - Implement and use custom callbacks.
- Creating an agent with MCP - Integrate Model Context Protocol tools.
- Serve an Agent with A2A - Deploy agents with Agent-to-Agent communication.
- Building Multi-Agent Systems with A2A - Using an agent as a tool for another agent to interact with.
Contributions
The AI agent space is moving fast! If you see a new agentic framework that AnyAgent doesn't yet support, we would love for you to create a Github issue. We also welcome your support in development of additional features or functionality.
Running in Jupyter Notebook
If running in Jupyter Notebook you will need to add the following two lines before running AnyAgent, otherwise you may see the error RuntimeError: This event loop is already running. This is a known limitation of Jupyter Notebooks, see Github Issue
import nest_asyncio
nest_asyncio.apply()
Release files for any-agent 1.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| any_agent-1.18.0.tar.gz | 366.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| any_agent-1.18.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 478.4 kB
Release files / any_agent-1.18.0.tar.gz
| Download URL | any_agent-1.18.0.tar.gz |
|---|---|
| Size | 366.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d1014a8f21f28d50d3f2c56cad73c2637f32836491f9bf15b03bfaa0701ff99
|
|
BLAKE2b-256 checksum How to use checksums |
3391740723684a55af0df26fdf898a091901ae3c7340743e4f37857d21676c7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 18, 2026.
Transparency logRelease files / any_agent-1.18.0-py3-none-any.whl
| Download URL | any_agent-1.18.0-py3-none-any.whl |
|---|---|
| Size | 112.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76f31c8ba4f4d7dbf7b2e7d1fa13f7dd48d041c8960fbf3c36523dea5a184138
|
|
BLAKE2b-256 checksum How to use checksums |
6fc1c5ec0e6389e092a5a183688e44d13cce94f3a470cfacaef1a863157d0670
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 18, 2026.
Transparency log
