> For the complete documentation index, see [llms.txt](https://docs.oortech.com/oort/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oortech.com/oort/aion/aion-multi-ai-agent-system.md).

# AION Multi AI Agent System

OORT AION is a multi-agent system built to automate the operational layer of a Web3 project — social media, community management, internal collaboration, and paid media — without sacrificing human control over what gets published.

Each agent runs its own continuous loop. Operators stay in the decision seat: every outward-facing action requires a human click before it goes live.

### Core Design Principles

* **Human-in-the-loop by default** — nothing goes public without an operator action (approve / reject / rewrite).
* **Honest over hallucinated** — if data is missing or stale, AION says so rather than filling gaps.
* **One loop, not ten tools** — each module handles the full cycle (monitor → judge → draft → distribute → report) so operators only deal with decisions, not logistics.


---

# 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.oortech.com/oort/aion/aion-multi-ai-agent-system.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.