Skip to main content
Every pre.dev interface uses the same workspace key: specifications and browser tasks over REST, the AI Gateway, the SDKs, the MCP server, and plain-words actions in Browser Agents Local.

​
Get your key

Copy your pre.dev API key from Integrations → Built-in in the dashboard: pre.dev/projects/integrations for your personal workspace, or the Integrations page of a team workspace. Workspace keys start with pdk_. Each workspace, your personal account or a team, has one key. The Built-in tab shows it in full with its last-used time. Keep it in your application’s secret configuration and call pre.dev from a server, a script, or local development. Never ship the key in browser or mobile code. Apps you build on pre.dev already have the key in their environment as PREDEV_API_KEY; see built into every app. Keys issued before workspace keys existed keep working. Use the pdk_ key for new integrations.

​
Send the key

The OpenAI SDKs send Authorization: Bearer and the Anthropic SDK sends x-api-key. The AI Gateway accepts both, so those SDKs need only a base URL and the key.

​
Rotate the key

Choose Rotate on the key’s card. The old key keeps working for 15 minutes, so running apps can switch without a gap. Update your secret store, then confirm a request with the new key succeeds before the window closes.

​
Which accounts each interface accepts

Authentication and feature access are separate checks. A Free account can call Browser Agents and the AI Gateway, while an Architect REST or MCP call returns 401. Which plans can generate specifications is covered in plans, credits, and pricing. Read the response message for the required action.

​
Account and team context

A personal key acts in your personal account. A team key selects the team’s context for specifications and credit usage. Browser history is scoped to the authenticated caller. Submit and retrieve work with the same key.

​
SDK setup

​
MCP sign-in

The pre.dev MCP server is https://api.pre.dev/mcp, over Streamable HTTP. It runs pre.dev’s specification and browser tools. Searching this documentation is a separate MCP server, https://docs.pre.dev/mcp, which needs no key. Add it to your client’s remote HTTP servers, then use the client’s authentication flow. The browser asks you to sign in and choose the personal account or team to connect. MCP setup covers client configuration and troubleshooting.