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

# Infragrid overview

> Run cloud browser tasks, ordered workflows, and published Blueprints through one durable developer platform.

Infragrid gives server-side applications a durable way to automate the web. Start an exploratory browser task, execute an ordered workflow, or run an immutable published Blueprint—then recover the result by run ID.

<CardGroup cols={2}>
  <Card title="Run your first task" icon="rocket" href="/get-started/quickstart">
    Go from API key to completed browser run.
  </Card>

  <Card title="Build an ordered workflow" icon="diagram-project" href="/guides/ordered-workflows">
    Combine deterministic browser steps with AI-assisted actions.
  </Card>

  <Card title="Run a published Blueprint" icon="blueprint" href="/guides/published-blueprints">
    Execute a version-pinned automation with typed inputs.
  </Card>

  <Card title="Explore the REST API" icon="brackets-curly" href="/reference/overview">
    Review authentication, resources, statuses, and every public endpoint.
  </Card>
</CardGroup>

## Choose an interface

| Interface                          | Best for                                             |
| ---------------------------------- | ---------------------------------------------------- |
| [REST API](/reference/overview)    | Any server environment and direct protocol control   |
| [TypeScript SDK](/sdks/typescript) | Node.js services and typed workflow builders         |
| [Python SDK](/sdks/python)         | Python services and synchronous automation           |
| [CLI](/tools/cli)                  | Shell scripts, smoke tests, and one-off tasks        |
| [MCP server](/tools/mcp)           | Giving MCP-compatible agents bounded Infragrid tools |

## One runtime, three automation modes

<AccordionGroup>
  <Accordion title="Free-form browser tasks">
    Send one natural-language goal when the route through a site is exploratory. Infragrid plans and executes the browser work, while your application polls a durable run resource.
  </Accordion>

  <Accordion title="Ordered workflows">
    Define each navigation, interaction, extraction, and completion step. Workflows are portable JSON and are ideal when ordering and output names matter.
  </Accordion>

  <Accordion title="Published Blueprints">
    Publish an automation in Infragrid, expose only its input contract, and let integrations run an immutable revision. Draft graphs and raw browser observations stay private.
  </Accordion>
</AccordionGroup>

## Durable by default

Every accepted run receives an ID immediately. Use that ID to recover status after a process restart, wait for a terminal result, or cancel work. Mutation requests can carry an idempotency key so safe retries resolve to the original run instead of creating duplicates.

<Note>
  The TypeScript SDK, Python SDK, CLI, and MCP adapter are implemented at version 0.1.0 in the source workspace. Registry publication is a separate release gate; use the source-checkout instructions until the package release is announced in the [changelog](/changelog).
</Note>

## Security boundary

Workspace API keys are server credentials. They are revealed once, stored hashed, and limited by scopes. Never ship an `ig_live_` key in browser JavaScript, URLs, logs, or source control.

<Card title="Create a scoped API key" icon="key" href="/authentication">
  Choose the minimum scopes your integration needs, then store the key in your server-side secret manager.
</Card>


## Related topics

- [API overview](/reference/overview.md)
- [CLI](/tools/cli.md)
- [TypeScript SDK](/sdks/typescript.md)
- [MCP server](/tools/mcp.md)
- [Python SDK](/sdks/python.md)