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

# Forward Mode overview

> A mode layer that lowers the barrier to bringing agents into business scenarios, delivering agent capabilities through a three-tier enterprise / template / user configuration model.

Forward Mode is the managed delivery layer built on top of [Build Mode](/cloud-agents/api/agents/list). Administrators predefine the agent shape and available resources through a three-tier configuration model (enterprise / template / identity), and callers simply pass a `template_id` and `identity_id` to use an agent — without managing the underlying runtime.

Forward Mode ships with built-in IM channel integration, scheduled triggers (Schedules), and end-user identity isolation (Identities), making it a good fit for SaaS providers, integrators, and teams serving many end users or a large volume of callers.

## Base URL

All Forward endpoints use the production gateway:

```text theme={null}
https://api.qoder.com/api/v1/forward
```

## Authentication

All Forward endpoints require Qoder PAT authentication:

| Header          | Required | Description    |
| --------------- | -------- | -------------- |
| `Authorization` | Yes      | `Bearer <PAT>` |

Unsafe `POST` endpoints may accept an `Idempotency-Key` header.

## Resource families

| Resource               | Description                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------- |
| **Templates**          | Reusable agent-shape baselines that define default agent and session configuration |
| **Identities**         | End-user identities with per-identity configuration overrides and isolation        |
| **Sessions**           | Conversations or task runs started from a template + identity                      |
| **Schedules**          | Cron or one-time triggered execution                                               |
| **Schedule runs**      | Execution records produced by schedules                                            |
| **Channels**           | Integration with external IM channels                                              |
| **Resources Registry** | Register shared resources into Forward                                             |

## Error envelope

Errors use the Forward error envelope:

```json theme={null}
{
  "type": "error",
  "request_id": "req_xxx",
  "error": {
    "type": "invalid_request_error",
    "code": "invalid_request_body",
    "message": "invalid request body"
  }
}
```

## Related

<CardGroup cols={2}>
  <Card title="Create a template" icon="file-plus" href="/cloud-agents/api/forward/templates/create" />

  <Card title="Create a session" icon="comment" href="/cloud-agents/api/forward/sessions/create" />
</CardGroup>