> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-integrations/textual-a2a-agent/configuring-textual-settings-for-a2a.md).

# Configuring Textual settings for A2A

On a self-hosted instance of Tonic Textual, to configure how A2A calls to your instance work, use the following [environment variables](/textual/textual-install-administer/configuring-textual/textual-env-var-configure.md):

<table><thead><tr><th width="323.73828125" valign="top">Variable</th><th width="123.953125" valign="top">Default value</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><code>SOLAR_API_URL</code></td><td valign="top"></td><td valign="top"><p>Public origin of the API (<code>https://textual.example.com</code>).</p><p></p><p>Published in the agent card as the absolute interface URL.</p><p></p><p>Must be reachable by clients.</p></td></tr><tr><td valign="top"><code>SOLAR_A2A_PROTOCOL_MODE</code></td><td valign="top"><code>both</code></td><td valign="top"><p>The allowed A2A protocol. Allowed values are:</p><p></p><ul><li><code>both</code> - Accepts v0.3 and v1 clients on the same endpoint.</li><li><code>v1_only</code> - Rejects v0.3.</li><li><code>v03_only</code> - Rejects v1.</li></ul></td></tr><tr><td valign="top"><code>SOLAR_A2A_MAX_TEXT_LENGTH</code></td><td valign="top"><code>500000</code></td><td valign="top"><p>The maximum number of characters in a string sent for detection or redaction.</p><p></p><p>When set to <code>0</code> , the text detection and redaction skills are disabled.</p></td></tr><tr><td valign="top"><code>SOLAR_A2A_MAX_FILE_SIZE_MB</code></td><td valign="top"><code>100</code></td><td valign="top"><p>The maximum size in megabytes of a file sent for redaction.</p><p></p><p>When set to <code>0</code> , the file redaction skill is disabled.</p></td></tr><tr><td valign="top"><code>SOLAR_A2A_MAX_CONCURRENT_TASKS_PER_ORG</code></td><td valign="top"><code>5</code></td><td valign="top"><p>The number of active A2A tasks that are allowed for each organization.</p><p></p><p>When set to <code>0</code> , the A2A agent is disabled.</p></td></tr><tr><td valign="top"><code>SOLAR_A2A_JOB_TIMEOUT_IN_MINUTES</code></td><td valign="top"><code>30</code></td><td valign="top">The number of minutes before a <code>file-redact</code> job times out and is marked as failed.</td></tr><tr><td valign="top"><code>SOLAR_A2A_TASK_TTL_HOURS</code></td><td valign="top"><code>72</code></td><td valign="top"><p>The number of hours to retain completed, failed, and canceled tasks.</p><p></p><p>When set to <code>0</code> , the tasks are not purged.</p></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tonic.ai/textual/textual-integrations/textual-a2a-agent/configuring-textual-settings-for-a2a.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 `build a script that syncs our docs to a CMS` 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.
