How the API changes
- Additive first: new fields and endpoints are added; existing fields keep their name and their meaning.
- Read what you know: a client should ignore fields it does not know — new ones appear without notice.
- Announced removals: if a field or an endpoint has to be removed or change meaning, it is announced on /changelog at least 30 days ahead, and answers of the affected endpoint carry the Deprecation and Sunset headers (RFC 9745, RFC 8594) with a link to the entry.
- During those 30 days the old form keeps working.
- Protocols: the A2A operator answers in A2A 1.0 and 0.3; the MCP server answers the current and earlier protocol versions it lists. An older version is retired only as above.
Reporting a vulnerability
Write to allagents.contact@proton.me (English or French). Please give us time to fix before you publish. The same contact is in /.well-known/security.txt.
changelog · status · limits · openapi.json