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

# Using Your Agent

> Four ways to put your Agentheya agent to work — chat link, REST API, MCP server, and scheduled runs.

Once your agent is configured, you have four ways to use it:

| Method                                   | Best for                                               |
| ---------------------------------------- | ------------------------------------------------------ |
| [**Chat link**](/sidebar-menu/web)       | Sharing with users — no code required                  |
| [**REST API**](/openai-compatible-api)   | Apps, bots, and workflows that speak the OpenAI API    |
| [**MCP server**](/mcp-server)            | Claude Desktop, Cursor, Zed, and other AI coding tools |
| [**Schedules**](/sidebar-menu/schedules) | Recurring tasks that run on a timer                    |

All four share the same agent — the same configuration, tools, memory, and activity log. They differ only in how the conversation is initiated.

<CardGroup cols={2}>
  <Card title="Chat link" icon="link" href="/sidebar-menu/web">
    A hosted URL your users open in a browser. No code required.
  </Card>

  <Card title="REST API" icon="code" href="/openai-compatible-api">
    OpenAI-compatible. Works with any `openai` SDK, LangChain, and more.
  </Card>

  <Card title="MCP server" icon="plug" href="/mcp-server">
    Call your agent as a tool from Claude Desktop, Cursor, Zed, and similar.
  </Card>

  <Card title="Schedules" icon="clock" href="/sidebar-menu/schedules">
    Set a time or a cron expression. The agent runs itself.
  </Card>
</CardGroup>

## API keys

The REST API and MCP server authenticate with the same API key format. Generate one from your agent's **Details** page in the dashboard.

* Keys start with `sk_ah_`
* Each key is bound to one agent
* You see the full key once at creation — we only store a hash
* Both agent owners and subscribers can generate keys; subscriber keys scope access to that user's own data

To expose multiple agents across multiple integrations, generate one key per agent and configure each separately.