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

# Overview

> How declarative agents fit into Hyperterse and how to navigate the agent guides.

Hyperterse agents are declarative A2A workloads you define next to tools. You describe behavior in config; Hyperterse validates it and serves each agent on its own HTTP prefix—no separate agent service required.

## What you get

* Declarative setup — agents are config-first, like tools
* Up-front permission checks for which tools an agent may call
* Per-agent HTTP — agent card, JSON-RPC, streaming, tasks, and push settings
* Multi-provider models — Gemini, Vertex AI, and OpenAI-compatible APIs

## How the system fits together

Tools and agents live in the same project. When you build or start the server, Hyperterse loads both, applies tool-access policy, and exposes MCP for tool-style calls and per-agent routes when you want conversational or task-style behavior.

Rough flow:

1. Hyperterse discovers tools and agents from your project.
2. Tool access policy is resolved (`inherit` / `allow_*`).
3. Agent definitions are ready to serve.
4. A2A endpoints are available under `/agent/{agentName}`.

## Endpoint shape per agent

Each agent gets:

* `GET /agent/{agentName}/.well-known/agent-card.json`
* `POST /agent/{agentName}`

<Tip>
  Agent routes are separate from MCP `/mcp`. Use MCP when the client is
  tool-centric; use `/agent/*` when you need agent protocol behavior.
</Tip>

## Reading path

1. [Quickstart](/agents/quickstart) — create and run your first agent.
2. [Tool access](/agents/tool-access) — lock down permissions correctly.
3. [Runtime API](/agents/runtime-api) — A2A methods and response shapes.
4. [Model providers](/agents/model-providers) — provider-specific setup.

## References

* [Agent config reference](/reference/agent-config)
* [OpenAI compatibility](/agents/model-providers#openai-compatibility)
* [Configuration schemas](/reference/configuration-schemas)
* [Project structure](/concepts/project-structure)