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

# Engine

> Activate headless document automation, connect integrations, and monitor usage.

Engine is Autype's workspace for **API, MCP, and automated document jobs**.
Workspace is the visual document editor. Both use the selected organization's
resources and billing, but activating Engine does not unlock the editor.

## Activate Engine

1. Sign in to [Autype](https://app.autype.com) and select the organization you want to use.
2. Choose **Engine** in the product selector.
3. If offered, start the one-time **50-credit, 14-day Engine test** without a payment method. Otherwise activate with a permanent credit top-up or an eligible subscription.
4. Connect an integration and start with a read-only request before rendering your first document.

Test credits expire. Purchased credits do not. Pro and Team include monthly
automation credits, and the separate Pro trial includes a one-time allowance.
See [Pricing](/getting-started/pricing) for costs and eligibility.

## Find your resources

| Page | Use it to |
| - | - |
| **Overview** | Check access, balance, and the starting points for your automation workflow. |
| **Documents** | Find the projects and documents used by API and MCP workflows. |
| **Resources** | Manage reusable styles, blocks, templates, and files/images. Available actions depend on your permissions. |
| **Integrations** | Manage API keys, MCP OAuth connections, and reusable job webhook endpoints. |
| **Usage** | Inspect automation usage and recent activity for the organization. |
| **Docs** | Open API and integration documentation. |

## Connect an integration

* **ChatGPT or Claude:** follow the dedicated [ChatGPT](/automation/integrations/mcp/chatgpt) or [Claude](/automation/integrations/mcp/claude) OAuth guide. Select the intended organization on the consent screen.
* **Direct API, n8n, or Make:** create a scoped API key as an organization Owner or Admin, then follow the [API introduction](/api-reference/introduction).
* **Job notifications:** configure a reusable endpoint under Integrations when you need signed notifications. Keep its signing secret private. Request-specific `webhookUrl` callbacks are documented separately in [Webhooks](/api-reference/webhooks).

A successful single render costs **1 credit**; each successful document in a
batch costs **1 credit**. Other processing operations have their own rates.
Reading resources or checking a job's status does not incur a render charge.
Download generated output promptly; a job history entry is not permanent file storage.

## Workspace tools versus automation

The browser tools under **Workspace → Tools** are included with an active
editor subscription, subject to service limits. The same kind of operation
through the Developer API or MCP uses the published automation credit rates.
Check which route you are using before estimating usage.

To open the visual editor, switch to **Workspace** and activate an appropriate
plan or Pro trial. To revoke a client, open **Settings → Connected Apps**; this
does not cancel billing or delete documents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.