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

# Welcome to AutoSage

> Build grounded AI agents on top of your own knowledge, data, and tools.

AutoSage is a platform for building **grounded AI agents** — assistants that answer from *your* documents and databases, use *your* connected apps and tools, remember what matters across conversations, and can run on a schedule or be called through an API.

You can use AutoSage two ways, and this documentation is split to match:

<CardGroup cols={2}>
  <Card title="Product docs" icon="sparkles" href="/product/concepts">
    Configure knowledge bases, agents, chat, and memory from the dashboard. No code required.
  </Card>

  <Card title="Developer docs" icon="code" href="/developers/introduction">
    Integrate AutoSage into your own product with the REST API, streaming, and API keys.
  </Card>
</CardGroup>

## What you can build

<CardGroup cols={2}>
  <Card title="Knowledge assistants" icon="book-open">
    Upload documents and connect databases, then ask questions and get cited, grounded answers.
  </Card>

  <Card title="Autonomous agents" icon="robot">
    Give an agent a goal, tools, and a schedule, and let it run tasks on its own.
  </Card>

  <Card title="Customer-facing bots" icon="comments">
    Embed a chat experience for your end users, isolated per customer through a single API key.
  </Card>

  <Card title="Agent networks" icon="diagram-project">
    Let agents delegate to other specialized agents to answer questions outside their own knowledge base.
  </Card>
</CardGroup>

## How AutoSage fits together

Everything in AutoSage lives inside a simple hierarchy. Understanding it once makes the rest of the platform click:

<Steps>
  <Step title="Organization">
    Your company or team account. Holds billing, members, and everything below.
  </Step>

  <Step title="Environment">
    An isolation boundary — like `dev`, `staging`, and `production`. API keys belong to one environment.
  </Step>

  <Step title="Tenant">
    A resource owner with its own credits and quotas. In a customer-facing product, a tenant often maps to one of *your* customers.
  </Step>

  <Step title="Knowledge base">
    The container for a set of documents, database connections, prompts, and the agents that use them.
  </Step>
</Steps>

<Card title="Learn the concepts" icon="compass" href="/product/concepts">
  Start with the core concepts to see how knowledge bases, agents, chat, and memory relate.
</Card>

## Popular topics

<CardGroup cols={3}>
  <Card title="Create an agent" icon="wand-magic-sparkles" href="/agents/overview" />

  <Card title="Upload documents" icon="file-arrow-up" href="/knowledge-bases/documents" />

  <Card title="Set up memory" icon="brain" href="/memory/overview" />

  <Card title="Authenticate the API" icon="key" href="/developers/authentication" />

  <Card title="Stream a chat" icon="bolt" href="/developers/guides/chat-and-stream" />

  <Card title="Invite your team" icon="users" href="/teams/invites" />
</CardGroup>
