Skip to main content

Infragrid Python SDK

Build ordered browser workflows with the same small API as the JavaScript SDK:

from infragrid import Infragrid

client = Infragrid()  # reads INFRAGRID_API_KEY
result = (
    client.workflow("account-review")
    .navigate("https://example.com")
    .type("#account-search", "%account_id%", submit=True)
    .extract("extract the account risk details", name="risk")
    .run(variables={"account_id": "acct_123"})
)

Install locally with pip install -e packages/python-sdk.

This sends native workflow JSON; it does not generate Brick or compile the steps into a prompt. Named extractions are available in run["result"]["outputs"].

Configuration and failures

The client reads INFRAGRID_API_KEY and optional INFRAGRID_BASE_URL. Explicit constructor arguments take precedence over environment variables. GET requests retry transient connection, timeout, rate-limit, and server failures up to max_retries; create requests retry only when an idempotency_key makes replay safe, including a bounded server response while the original idempotency claim is still completing.

HTTP failures raise status-specific InfragridError subclasses and preserve the server request ID when one is available. Invalid successful JSON, malformed run envelopes, and unexpected transport failures are surfaced as APIConnectionError instances. Responses are capped at 1 MiB; oversized successful payloads fail closed and oversized error bodies are discarded before status-specific classification.

Published Blueprints

blueprint = client.blueprints.list()["data"][0]
run = client.blueprints.runs.create(
    blueprint["id"],
    {"account_id": "acct_123"},
    revision_id=blueprint["latestRevision"]["id"],
    idempotency_key="account-review-acct-123",
)
events = client.blueprints.runs.events(run["id"])
finished = client.blueprints.runs.wait(run["id"])

Omit revision_id to pin the latest published revision at run creation. The SDK does not expose draft graph authoring. blueprints.run() remains a compatibility alias for blueprints.runs.create().

Metadata

Release files for infragrid 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for infragrid 0.1.0
File Size Uploaded Provenance Actions
infragrid-0.1.0.tar.gz 12.4 kB With provenance Details for infragrid-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for infragrid 0.1.0
File Interpreter ABI Platform Actions
infragrid-0.1.0-py3-none-any.whl Python 3 none any Details for infragrid-0.1.0-py3-none-any.whl

Total release size: 25.3 kB

Release files / infragrid-0.1.0.tar.gz

Download URL infragrid-0.1.0.tar.gz
Size 12.4 kB
Tags Source
SHA-256 checksum
How to use checksums
dd1a9d08c0bc27eb613a27f419a1789c7145eb4b0bad78637f02f430e159da67
BLAKE2b-256 checksum
How to use checksums
c6df173f1a61bceee13f02f53939bce10b2c8db59534fd31d6e3217303917565
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release files / infragrid-0.1.0-py3-none-any.whl

Download URL infragrid-0.1.0-py3-none-any.whl
Size 12.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
106f95de2fd4e612f4be6fe697cfba5b5f7ab8d1c932069fbfd34e4acac576ee
BLAKE2b-256 checksum
How to use checksums
134d189a5830db61d6bb7312bfc155901f757bc51040237007f62a801be9bc89
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Security for infragrid 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for infragrid-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page