> For the complete documentation index, see [llms.txt](https://anyint.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anyint.gitbook.io/docs/features/overview.md).

# overview

AnyInt is not only a transport layer. The platform also changes how applications behave once they are in production: how output is streamed, how keys are limited, how routing is applied, and how model output is shaped for downstream systems.

## Feature map

| Feature area          | What it affects                                  |
| --------------------- | ------------------------------------------------ |
| Streaming             | how fast users see output                        |
| Structured outputs    | how safely you can feed model output into code   |
| Tool calling          | how models interact with external systems        |
| Prompt caching        | how repeated context can reduce cost and latency |
| Routing and fallbacks | how traffic moves across models and providers    |
| Guardrails            | how keys, teams, and policies control usage      |

Some of these are model-dependent. Others are account, key, or organization features. Use the linked pages below to decide where a behavior actually lives.

## How to read this section

* read [Streaming](/docs/features/streaming.md) if your UI depends on low-latency output
* read [Structured Outputs](/docs/features/structured-outputs.md) and [Tool Calling](/docs/features/tool-calling.md) if model output feeds code or workflows
* read Routing, [models](/docs/models-and-modalities/models.md), and Model Fallbacks if reliability and cost control matter