> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aixy-gateway.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Aixy fits together

> Organizations, projects, credentials, models, and tools.

An **organization** owns your gateway configuration and members. A **project** groups the traffic
for an application, environment, or team. Select the project in the dashboard before configuring
or testing it; organization administrators can select **All projects** to manage shared settings.

## From an application to a provider

1. The application sends a model request with a project-scoped Aixy API key.
2. Aixy identifies the project and key owner, resolves the provider connection, and applies model
   access, guardrails, and applicable budgets.
3. Aixy calls the selected provider directly or uses the project's routing model to choose a target.
4. The response returns to the client, with a request ID for investigation. Usage and Activity
   metadata arrive asynchronously in the dashboard.

| Resource | What it controls |
| - | - |
| Provider connection | The upstream account, endpoint, region, and provider credential |
| Aixy API key (`gak_…`) | Who owns a request and which project supplies its configuration |
| Direct model (`provider/model`) | The specific provider and model to call |
| Routing model (`aixy/alias`) | A project-owned name with configured targets and a selection strategy |
| MCP connection | The external tool server and the account used to execute actions |
| Personal MCP token | An external agent's access to the user's authorized tools |

## Choose the configuration scope

Provider connections can be shared at organization scope or overridden for a project. A project
connection takes precedence for that provider. Removing the override restores inheritance.

Model blocks and guardrails combine organization and project protection. A project can add
restrictions but cannot remove an organization block or weaken an organization guardrail.
Applicable hard budgets must all admit a request. Content capture has its own inheritance rule:
a project setting overrides the organization default, including an explicitly disabled setting.

## Choose where to work

* Use the **dashboard** to configure connections, access, policies, and reporting.
* Use **Playground** to test a project under its actual model policies and budgets.
* Use the **gateway API** from a trusted backend or an authorized coding client.
* Use **Agent tools** to connect external accounts and configure MCP access independently of
  the model connection.

Provider credentials stay in Aixy. Store project keys in your backend's secret manager or your
coding client's local credential store. Start with the [quickstart](/quickstart), then follow
[API key management](/authentication) for rotation and lifecycle controls.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.