Run your first task
Go from API key to completed browser run.
Build an ordered workflow
Combine deterministic browser steps with AI-assisted actions.
Run a published Blueprint
Execute a version-pinned automation with typed inputs.
Explore the REST API
Review authentication, resources, statuses, and every public endpoint.
Choose an interface
One runtime, three automation modes
Free-form browser tasks
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.
Ordered workflows
Ordered workflows
Define each navigation, interaction, extraction, and completion step. Workflows are portable JSON and are ideal when ordering and output names matter.
Published Blueprints
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.
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.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.
Security boundary
Workspace API keys are server credentials. They are revealed once, stored hashed, and limited by scopes. Never ship anig_live_ key in browser JavaScript, URLs, logs, or source control.
Create a scoped API key
Choose the minimum scopes your integration needs, then store the key in your server-side secret manager.