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

# Agent OS

> Build agents that can retrieve context, choose tools, and take action across your users' connected apps.

Agent OS is Paragon's integration layer for AI agents. It combines permission-aware context retrieval with dynamic tool discovery and execution, so agents can work across the SaaS apps your users already rely on.

There are 2 APIs included in Agent OS:

> **[Context API](https://docs.useparagon.com/agent-os/context/overview.md)**
>
> Give agents the information they need before acting.
>
> Connect sources through Setup Links, sync files and permissions through Managed Sync, and get indexed results from your users' knowledge sources.

> **[Tools API](https://docs.useparagon.com/agent-os/tools/overview.md)**
>
> Give agents the capabilities they need to act.
>
> Allow your agent to search through Paragon's pre-built library of thousands of actions and get fast results with preview output that your agent can re-query to optimize context.

## Base URL

Agent OS requests are sent to the base URL for your region. Each API has its own path prefix:

**US Cloud**

| API | Base URL |
| - | - |
| Context API | `https://agentos.useparagon.com/api/context` |
| Tools API | `https://agentos.useparagon.com/api/tools` |

**EU Cloud**

| API | Base URL |
| - | - |
| Context API | `https://agentos.eu.paragon.so/api/context` |
| Tools API | `https://agentos.eu.paragon.so/api/tools` |

Include your Project ID in the path of each request. For example, to search context for a project:

```http theme={null}
POST https://agentos.useparagon.com/api/context/projects/{projectId}/search
```

You can find your Project ID (a UUID) in the Paragon dashboard.

## Authentication

Agent OS APIs use the same Connected User identity model as the rest of Paragon. Your backend mints a Paragon User Token for the user and sends it as a Bearer token:

```http theme={null}
Authorization: Bearer <Paragon User Token>
```

ActionKit and Context API both use this token to scope requests to a Connected User. Context API also requires the token `aud` claim to include the Paragon host and Project ID, matching the Managed Sync auth model.

```json JWT Payload theme={null}
{
  "sub": "your-connected-user-id",
  "aud": "useparagon.com/{your-project-id}",
  "exp": 1752000000,
  "iat": 1751000000
}
```