Integrations · Steel
Guild agents use Steel to open isolated cloud browsers, scrape pages, capture screenshots, render PDFs, and send computer-use actions against live sessions. Guild stores the Steel API key server-side so agent code never sees it. Credential policies let you restrict which operations each agent can call, and every request runs through Guild’s audit trail.
Book a demo
See how teams govern agents that use Steel.
Talk to sales
Get access to Guild, then connect Steel to your first agent.
What the Steel integration exposes
The integration provides tools to create and release browser sessions, list and inspect them, and retrieve live viewer URLs and open pages. Separate tools scrape a URL and return content with metadata and links, capture a hosted PNG, render a hosted PDF, retrieve cookies and storage for a session, and send a single computer-use action against a running session.How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in Guild. Click Connect, select steel, and paste your Steel API key into the API Key field.
2
Import and wire the tools
Import SteelTools from the guildai~steel package and spread it into your agent’s tools object. Guild sends the key as the steel-api-key header on every request.
3
Select only what you need
Tools use the steel_ prefix. Use pick() from the Agent SDK to include only the specific tools your agent requires, as documented on the tool sets page.
Why Steel session access needs governing
Steel tools can launch browsers, scrape arbitrary URLs, capture screenshots, render PDFs, retrieve session cookies and storage, and send computer-use actions against live sessions. Guild stores the API key server-side through its credential proxy, so agent code never handles it directly. You can scope a credential to one workspace, one member, or one agent so access stays as narrow as the job requires. See Credentials for scoping options. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Steel. You can restrict an agent to read-only operations like steel_scrape and steel_screenshot while blocking session creation or computer actions entirely. A DENY rule always overrides a matching ALLOW rule. Agents cannot evaluate or bypass policies themselves. Without scoped rules the credential falls back to allow-all; delete that default once your rules cover everything agents should reach. See Credential policies for rule syntax.About the Steel integration
This integration lets agents launch and manage isolated Steel cloud browser sessions. Agents can scrape web content, capture screenshots, render PDFs, and inspect session state including cookies and storage. They can also send computer-use actions against running sessions. The integration isguildai~steel.
Authentication
- Type: API key
- Header: Guild sends the key as
steel-api-key: <key>
Setup
1
Connect Steel
In Guild, go to Access & setup > Credentials, click Connect, select steel, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thesteel_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~steel:
Frequently asked questions
Does Guild expose webhook events from Steel?
Does Guild expose webhook events from Steel?
No. The catalog entry for guildai~steel lists no webhook events, so event-triggered workflows based on Steel activity are not available.
Can I limit one agent to scraping only, without letting it launch or release sessions?
Can I limit one agent to scraping only, without letting it launch or release sessions?
Yes. Write a credential policy that ALLOW-lists steel_scrape and steel_screenshot and DENY-lists steel_create_session, steel_release_session, and steel_release_all_sessions, then scope the policy to that agent. See Credential policies.
How does Guild authenticate requests to Steel?
How does Guild authenticate requests to Steel?
Guild sends the key as the steel-api-key header on every request. The key is stored as a Guild credential and injected server-side by the credential proxy; the agent never sees it.
Put a governed agent on Steel this week
Book a demo
See how teams govern agents that use Steel.
Talk to sales
Get access to Guild, then connect Steel to your first agent.