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

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Run and check Skyvern cloud browser tasks from Guild agents

> Connect Guild agents to Skyvern to launch cloud browser tasks against any URL and retrieve run status, output, screenshots, and failure details.

Integrations · Skyvern

Guild agents can launch Skyvern cloud browser tasks and retrieve their results without leaving the agent workflow. Guild stores the Skyvern API key server-side and injects it into every request, so agent code never handles the secret. Credential policies let you restrict which operations each agent can call, and every request passes through Guild's credential proxy before reaching Skyvern.

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Skyvern.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Skyvern to your first agent.

## What the Skyvern integration exposes

The integration provides two tools under the `skyvern_` prefix. `skyvern_run_task` sends a goal prompt and a target URL to Skyvern to start a cloud browser task. `skyvern_get_run` returns the status, structured output, screenshot URLs, and failure reason for a completed run. Together they cover the launch-and-retrieve workflow for automated web research and staging environment reproduction.

## How it works

**1. Open credentials in Guild**

Go to **Access & setup > Credentials** in your Guild account or organization. Click **Connect** and select **skyvern**.

**2. Paste your Skyvern API key**

Enter your key in the **API Key** field. Guild stores it and sends it as `x-api-key` on every request; agent code never sees it.

**3. Add the tools to your agent**

Import `SkyvernTools` from the integration package and spread it into your agent's `tools` object. Use `pick()` to include only the tools your agent needs.

## Why Skyvern access needs governing

Skyvern tasks execute goal prompts against real URLs, which means an agent with unconstrained access could trigger unintended actions on staging or production systems. Guild's credential proxy holds the API key server-side and checks credential policies before any request leaves Guild. You can write ALLOW and DENY rules scoped to specific operations, agents, or workspaces, so one agent can retrieve run results while another is blocked from starting new tasks.

Credentials can be scoped to an account, a single workspace, a specific member, or one installed agent. That scope controls which runs can use the Skyvern key at all. Revoking a grant or disconnecting a credential takes effect immediately without changing agent code.

## About the Skyvern integration

Guild agents can use Skyvern to launch cloud browser tasks by providing a goal prompt and a target URL. Agents can then retrieve the status, structured output, screenshot URLs, and failure reasons for any completed run. This enables automated web research and staging environment reproduction workflows. The integration is `guildai~skyvern`.

## Authentication

* **Type:** API key
* **Header:** Guild sends the key as `x-api-key: <key>`

### Setup

**1. Connect Skyvern**

In Guild, go to **Access & setup > Credentials**, click **Connect**, select **skyvern**, and paste the key into **API Key**.

See [Credentials](https://docs.guild.ai/platform/credentials.md) for workspace, member, and agent-scoped credentials.

## Usage

```typescript theme={null}
import { SkyvernTools } from "@guildai-services/guildai~skyvern"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  systemPrompt: "You work with Skyvern.",
  tools: { ...SkyvernTools },
})
```

### Selecting specific tools

Tools are named with the `skyvern_` prefix. Use [`pick()`](https://docs.guild.ai/sdk/tools#selecting-specific-tools) to include only what your agent needs.

## Tools

Tools in the latest published version of `guildai~skyvern`:

| Tool | What it does |
| - | - |
| `skyvern_get_run` | Return status, structured output, screenshot URLs, and failure reason for one run. |
| `skyvern_run_task` | Ask Skyvern to complete a prompt against a URL. |

## Frequently asked questions

> [accordion] How does Guild send my Skyvern API key to the service?
>
> Guild injects the key as the `x-api-key` header on each outbound request server-side. Agent code never reads or handles the key directly.

> [accordion] Can I limit which agents are allowed to start new Skyvern tasks?
>
> Yes. Write a credential policy with a DENY rule on `skyvern_run_task` scoped to the agents you want to restrict. The credential proxy enforces the rule before the request reaches Skyvern.

> [accordion] Can I give one workspace a different Skyvern key than the rest of my organization?
>
> Yes. Connect a second credential scoped to that workspace. Guild resolves credentials in order: workspace credentials take precedence over the account default.

> [accordion] Does Skyvern send webhook events back to Guild?
>
> No. The catalog entry for this integration lists no webhook events, so Guild does not receive push notifications from Skyvern. Agents must call `skyvern_get_run` to poll for results.

## Put a governed agent on Skyvern this week

> [card] [Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)
>
> See how teams govern agents that use Skyvern.

> [card] [Talk to sales](https://guild.ai/talk-to-sales)
>
> Get access to Guild, then connect Skyvern to your first agent.

## Related

**Also runs on Guild:** [Browserbase](https://docs.guild.ai/integrations/browserbase.md) · [Cloudflare](https://docs.guild.ai/integrations/cloudflare-openapi.md) · [Firecrawl](https://docs.guild.ai/integrations/firecrawl.md) · [Kernel](https://docs.guild.ai/integrations/kernel.md)

**Read:** Docs: [Credential policies](https://docs.guild.ai/platform/credential-policies.md) · [Credentials](https://docs.guild.ai/platform/credentials.md) · [Tools in agents](https://docs.guild.ai/sdk/tools.md)
