> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/admin-guide/change-log/api-agent.md).

# API Agent

{% hint style="info" %}
The API Agent versions can be downloaded [here](/admin-guide/agent-download.md).
{% endhint %}

The change log of each recent agent versions is available in the pages below.

{% content-ref url="/pages/KJccnfPuARpmhZdnExqc" %}
[Agent - 26.3 (LTS)](/admin-guide/change-log/api-agent/agent-26.3-lts-1.md)
{% endcontent-ref %}

{% content-ref url="/pages/lVvv4qifVTARNe9VSYuL" %}
[Agent - 26.2](/admin-guide/change-log/api-agent/agent-26.2.md)
{% endcontent-ref %}

{% content-ref url="/pages/diZoZE6UJgyxbrzG8t4N" %}
[Agent - 26.1](/admin-guide/change-log/api-agent/agent-26.1.md)
{% endcontent-ref %}

{% content-ref url="/pages/G32ym8DazAZfL2MylOsW" %}
[Agent - 25.12 (LTS)](/admin-guide/change-log/api-agent/agent-25.12-lts.md)
{% endcontent-ref %}

## Agent Release Cycle

#### Release cycle

The Agent is released monthly, and the version number follows a year.month.patch convention. Occasionally, a release may be skipped.

#### Long Term Support (LTS) versions

The releases of March, June, September and December are Long Term Support versions (e.g. releases named yy.3, yy.6, yy.9, and yy.12) and the last 3 LTS releases are supported.

The other versions don't benefit from our Long Term Support and are out of support as soon as a new LTS version is released.

#### Compatibility with SBE versions

The **last three LTS versions are supported** and are always compatible with the production supported SBE versions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.developers.symphony.com/admin-guide/change-log/api-agent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.