> 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/archives/agent-22.7.md).

# Agent - 22.7

## Agent Download

{% hint style="info" %}
To download the Agent, click [here](https://storage.googleapis.com/sym-platform/developers/rest-api/agent-22.7.1.zip).

For a list of Agent x SBE compatibilities, click [here](/admin-guide/agent-guide/sbe-x-agent-compatibility-matrix.md).
{% endhint %}

## Announcement

{% hint style="warning" %}
Since Agent 22.6, a new Release Cycle has been put in place for the Agent.

Agent 20.14 was the last agent to be released via the same schedule as SBE. Starting with the next version, Agent 22.6, agents release cadence will not be coupled to SBE's anymore, and its release version number will follow a year.month.patch pattern.

Please refer to the [main page](/admin-guide/change-log/api-agent.md) for more information (release cadence, new Long Term Support)
{% endhint %}

## Agent Changes

### Agent 22.7.1

* [Datahose - Read Events](https://developers.symphony.com/restapi/reference/datahose-read-events) now supports `eventTypes`, which will allow to restrict the payload to the only [Real Time Events](/bots/datafeed/real-time-events.md) requested.\
  \&#xNAN;*Please note that this is a breaking change from the version that was released with the 22.6 Agent: indeed the* `filters` *parameter is no longer supported.*\
  *Note also that Datahose still remains as beta.*
* The agent does not store the authentication token in clear in cache anymore.
* Fixed some logging security vulnerability.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.