Steel Browser is live in Stripe Projects
Steel Browser is live in Stripe Projects
Steel Browser is live in Stripe Projects
/
/
San Francisco
San Francisco
/
/
Nikola Balic
Nikola Balic
Today, Steel joins the Stripe Projects developer preview as a co-design and launch partner.
If you haven't used Stripe Projects yet, it provisions the services your app needs, things like databases, auth, hosting, and analytics, from the terminal or your coding agent. One command creates the account, provisions the resource, and syncs the credentials to your environment: no signing up for each service by hand, no copy-pasting keys between dashboards. Your whole stack comes from one place, and every account and resource stays in an account you own.
Steel is the piece that reaches past those services to the rest of the web.
Run stripe projects add steel/browser and your projects get cloud browser sessions for the live web. Start one session or run many in parallel.
The command creates a Steel project, writes Steel API key, and gives your agents browser sessions they can use for real web work: login flows, site verification, vendor workflows with no API, and runs you need to inspect when they break.
The hard part is giving agents the things they need around the code: credentials, state, a browser session, and evidence when something goes wrong.
That is what Steel adds.
"Agents are becoming the newest and soon-to-be biggest users of the web. We'll be able to delegate any task that we can do online to our agents so we can focus on the biggest needle movers. With Steel in Stripe Projects, agents can get access to browser environments as a true utility to work, research, and purchase for us without a human in the loop."
— Hussien Hussien, CEO & co-founder, Steel
Steel Browser in Stripe Projects
We built the Steel provider integration for the Agentic Provisioning Protocol, so an agent can provision cloud browser sessions the same deterministic way it provisions a database or an auth service.
The credentials point at a Steel org that's yours: your sessions and API keys live in your own Steel account, billed through the payment method you authorized in Stripe Projects.
"Agents need deterministic setup as much as deterministic execution. In Stripe Projects, adding Steel creates the org, project, scoped key, and dashboard handoff in one path, so browser sessions are provisioned like infrastructure, not handled as a manual setup step."
— Nasr Mohamed, CTO & co-founder, Steel
How Stripe Projects provisions Steel browser sessions
Two handoffs happen.
First: Stripe Projects gives your app a Steel key and writes it into .env.
Second: Steel gives the run a browser session with memory: a session that can stay logged in, a live view while it runs, and a recording when it breaks. Your agent can run one session or many in parallel when the job needs more than one browser. For login-walled sites, Steel's Credentials API can inject secrets into the session while keeping them out of the model's context and off the live viewer.
With Steel you can watch the click, the page, the pause, and the exact place where the web pushed back.
Agent workflows that need a real browser
Steel is useful when the work has to happen inside a website.
Think vendor portals, invoices behind dashboards, login flows with site verification steps, and internal tools that were never built for agents.
In those cases, the browser is the integration.
Steel is the open browser you actually own
Steel is built on ownership, transparency, and openness: an Apache-2.0 runtime you can inspect and self-host, with your sessions, profiles, and credentials living in an account you control.
Add Steel Browser to a Stripe project
Steel is in the Stripe Projects developer preview on a free pay-as-you-go plan and a paid plan for higher limits. See pricing and limits for current rates, or follow the Stripe Projects setup guide for provisioning, credentials, and SDK usage.
Now your agents can reach the rest of the web, one command inside Stripe Projects.
Today, Steel joins the Stripe Projects developer preview as a co-design and launch partner.
If you haven't used Stripe Projects yet, it provisions the services your app needs, things like databases, auth, hosting, and analytics, from the terminal or your coding agent. One command creates the account, provisions the resource, and syncs the credentials to your environment: no signing up for each service by hand, no copy-pasting keys between dashboards. Your whole stack comes from one place, and every account and resource stays in an account you own.
Steel is the piece that reaches past those services to the rest of the web.
Run stripe projects add steel/browser and your projects get cloud browser sessions for the live web. Start one session or run many in parallel.
The command creates a Steel project, writes Steel API key, and gives your agents browser sessions they can use for real web work: login flows, site verification, vendor workflows with no API, and runs you need to inspect when they break.
The hard part is giving agents the things they need around the code: credentials, state, a browser session, and evidence when something goes wrong.
That is what Steel adds.
"Agents are becoming the newest and soon-to-be biggest users of the web. We'll be able to delegate any task that we can do online to our agents so we can focus on the biggest needle movers. With Steel in Stripe Projects, agents can get access to browser environments as a true utility to work, research, and purchase for us without a human in the loop."
— Hussien Hussien, CEO & co-founder, Steel
Steel Browser in Stripe Projects
We built the Steel provider integration for the Agentic Provisioning Protocol, so an agent can provision cloud browser sessions the same deterministic way it provisions a database or an auth service.
The credentials point at a Steel org that's yours: your sessions and API keys live in your own Steel account, billed through the payment method you authorized in Stripe Projects.
"Agents need deterministic setup as much as deterministic execution. In Stripe Projects, adding Steel creates the org, project, scoped key, and dashboard handoff in one path, so browser sessions are provisioned like infrastructure, not handled as a manual setup step."
— Nasr Mohamed, CTO & co-founder, Steel
How Stripe Projects provisions Steel browser sessions
Two handoffs happen.
First: Stripe Projects gives your app a Steel key and writes it into .env.
Second: Steel gives the run a browser session with memory: a session that can stay logged in, a live view while it runs, and a recording when it breaks. Your agent can run one session or many in parallel when the job needs more than one browser. For login-walled sites, Steel's Credentials API can inject secrets into the session while keeping them out of the model's context and off the live viewer.
With Steel you can watch the click, the page, the pause, and the exact place where the web pushed back.
Agent workflows that need a real browser
Steel is useful when the work has to happen inside a website.
Think vendor portals, invoices behind dashboards, login flows with site verification steps, and internal tools that were never built for agents.
In those cases, the browser is the integration.
Steel is the open browser you actually own
Steel is built on ownership, transparency, and openness: an Apache-2.0 runtime you can inspect and self-host, with your sessions, profiles, and credentials living in an account you control.
Add Steel Browser to a Stripe project
Steel is in the Stripe Projects developer preview on a free pay-as-you-go plan and a paid plan for higher limits. See pricing and limits for current rates, or follow the Stripe Projects setup guide for provisioning, credentials, and SDK usage.
Now your agents can reach the rest of the web, one command inside Stripe Projects.
Today, Steel joins the Stripe Projects developer preview as a co-design and launch partner.
If you haven't used Stripe Projects yet, it provisions the services your app needs, things like databases, auth, hosting, and analytics, from the terminal or your coding agent. One command creates the account, provisions the resource, and syncs the credentials to your environment: no signing up for each service by hand, no copy-pasting keys between dashboards. Your whole stack comes from one place, and every account and resource stays in an account you own.
Steel is the piece that reaches past those services to the rest of the web.
Run stripe projects add steel/browser and your projects get cloud browser sessions for the live web. Start one session or run many in parallel.
The command creates a Steel project, writes Steel API key, and gives your agents browser sessions they can use for real web work: login flows, site verification, vendor workflows with no API, and runs you need to inspect when they break.
The hard part is giving agents the things they need around the code: credentials, state, a browser session, and evidence when something goes wrong.
That is what Steel adds.
"Agents are becoming the newest and soon-to-be biggest users of the web. We'll be able to delegate any task that we can do online to our agents so we can focus on the biggest needle movers. With Steel in Stripe Projects, agents can get access to browser environments as a true utility to work, research, and purchase for us without a human in the loop."
— Hussien Hussien, CEO & co-founder, Steel
Steel Browser in Stripe Projects
We built the Steel provider integration for the Agentic Provisioning Protocol, so an agent can provision cloud browser sessions the same deterministic way it provisions a database or an auth service.
The credentials point at a Steel org that's yours: your sessions and API keys live in your own Steel account, billed through the payment method you authorized in Stripe Projects.
"Agents need deterministic setup as much as deterministic execution. In Stripe Projects, adding Steel creates the org, project, scoped key, and dashboard handoff in one path, so browser sessions are provisioned like infrastructure, not handled as a manual setup step."
— Nasr Mohamed, CTO & co-founder, Steel
How Stripe Projects provisions Steel browser sessions
Two handoffs happen.
First: Stripe Projects gives your app a Steel key and writes it into .env.
Second: Steel gives the run a browser session with memory: a session that can stay logged in, a live view while it runs, and a recording when it breaks. Your agent can run one session or many in parallel when the job needs more than one browser. For login-walled sites, Steel's Credentials API can inject secrets into the session while keeping them out of the model's context and off the live viewer.
With Steel you can watch the click, the page, the pause, and the exact place where the web pushed back.
Agent workflows that need a real browser
Steel is useful when the work has to happen inside a website.
Think vendor portals, invoices behind dashboards, login flows with site verification steps, and internal tools that were never built for agents.
In those cases, the browser is the integration.
Steel is the open browser you actually own
Steel is built on ownership, transparency, and openness: an Apache-2.0 runtime you can inspect and self-host, with your sessions, profiles, and credentials living in an account you control.
Add Steel Browser to a Stripe project
Steel is in the Stripe Projects developer preview on a free pay-as-you-go plan and a paid plan for higher limits. See pricing and limits for current rates, or follow the Stripe Projects setup guide for provisioning, credentials, and SDK usage.
Now your agents can reach the rest of the web, one command inside Stripe Projects.
All Systems Operational