Service Credentials

When you connect a service like Browserbase, Stripe, or Notion, you usually need to provide credentials such as API keys or OAuth tokens. These credentials allow the AI agent and the sandbox environment to interact with your tools securely.

How it Works

1. Configure the Service

Click the Cable/Plug icon in the task form to add a service. You can attach credentials directly in the configuration modal. For example:

• Browserbase API Key: bbk_live_xxxxxxxxxxxx
• Stripe API Key: sk_live_xxxxxxxxxxxx

2. Sandbox Injection

Once the sandbox starts, your credentials are automatically available to the agent, the terminal, and any CLI tools you run.

• AI Agent: The agent can read these variables and use them in commands.
• Terminal: You can use echo $BROWSERBASE_API_KEY to verify your key is set.
• CLI Tools: Tools like the Stripe CLI will work immediately because STRIPE_API_KEY is already in the environment.

Setting Up Credentials

1. Open the Services Modal: Click the Cable/Plug icon next to the prompt input.
2. Add or Edit a Service: Select a preset or click + Add Custom.
3. Enter Keys: For presets, the required variable names are pre-filled. For custom services, you can add your own key-value pairs.
4. Save: Click Save to store the credentials.

Verifying Credentials in a Task

If you need to check if your keys are active during a task, open the Terminal tab and run:

# Check for a specific key
echo $BROWSERBASE_API_KEY

# List all service-related variables
env | grep -E '(BROWSERBASE|STRIPE|NOTION|LINEAR)'

If you don't see your variables, try opening a new terminal tab. The environment is loaded when the shell starts, so existing sessions might need a refresh.

Security

• Ephemeral Storage: Credentials are only available for the duration of your sandbox session.
• Redaction: API keys and tokens are automatically redacted in logs.
• Encryption: All service credentials are encrypted at rest in our database.
• Isolation: Variables are scoped to your specific sandbox and are never shared across users.

Troubleshooting

Keys Not Detected

Verify that the variable name matches exactly what the service expects. You can also check the Logs tab to see if the connection attempt failed due to an invalid key.

Terminal Sync

If the terminal doesn't see your variables, run source ~/.env.mcp to load them manually into your current session.

Example Workflow

1. Configure: Add Browserbase with your API key.
2. Start Task: Prompt "Use Browserbase to screenshot example.com."
3. Agent Execution: The agent uses the Browserbase tool to perform the action.
4. Manual Check: You open the terminal and run npx @browserbasehq/mcp list-projects to see your projects using the same credentials.