> ## Documentation Index > Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Anchor Browser is cloud browser infrastructure for AI agents and automation: browser sessions you control over CDP or REST, natural-language web tasks, versioned automation tasks, managed authentication into third-party web apps (identities with MFA), persistent volumes and profiles, recordings, live view, batch sessions, webhooks, and network options including residential proxies, extra stealth, and captcha solving for sites that block standard browsers. AI agents should start at https://docs.anchorbrowser.io/for-agents, then get an API key with Agent Access at https://docs.anchorbrowser.io/quickstart/agent-access — no dashboard account required. Read those two pages before authentication or API calls. # Upload Certificate > Upload a CA certificate to trust in browser sessions. Certificates are managed at the team level. Once uploaded, reference the certificate by name when creating sessions to trust services using that CA. See [CA Certificates documentation](/advanced/ca-certificates) for more details. ## OpenAPI ````yaml /openapi.yaml post /v1/certificates openapi: 3.1.0 info: title: AnchorBrowser API version: 1.0.0 description: > Anchor Browser ([anchorbrowser.io](https://anchorbrowser.io)) provides cloud browsers built for AI agents and automation. Use this API to launch and control browser sessions, run natural-language web tasks, authenticate into third-party web apps with managed identities, and capture recordings — reliably and at scale, without operating browser infrastructure yourself. ## Core resources - **Sessions** (`/v1/sessions`): launch configurable cloud browsers — residential proxies, stealth browsing, captcha solving, profiles, extensions, recording — and connect over CDP with Playwright, Puppeteer, or any CDP client. - **AI tools** (`/v1/tools/perform-web-task`): state a goal in natural language and the built-in agent completes it inside the browser. Related tools fetch webpages, take screenshots, render PDFs, and execute code in a session. - **Tasks** (`/v1/task`): create, version, deploy, and monitor repeatable browser automations built to run reliably in production. - **Applications and identities** (`/v1/applications`, `/v1/identities`): managed authentication into third-party web apps — including multi-step logins and TOTP-based 2FA — so agents can act on behalf of users. - **Profiles** (`/v1/profiles`): persist cookies and login state across sessions. - **OS-level control** (`/v1/sessions/{sessionId}/mouse`, `/keyboard`, `/clipboard`): raw input for flows that resist DOM automation. - Plus batch sessions for running browser fleets in parallel, session recordings, webhooks, events, extensions, client certificates, and billing usage. ## Authentication Pass an API key in the `anchor-api-key` header on every request. Create keys at [app.anchorbrowser.io](https://app.anchorbrowser.io) under API Access. AI agents that have no key yet can obtain one autonomously through the unauthenticated [agent-access flow](https://docs.anchorbrowser.io/quickstart/agent-access) (`POST /v1/agent-access`). ## For AI agents and LLMs - Docs: [docs.anchorbrowser.io](https://docs.anchorbrowser.io), with a machine-readable index at [/llms.txt](https://docs.anchorbrowser.io/llms.txt) and the full corpus at [/llms-full.txt](https://docs.anchorbrowser.io/llms-full.txt). - MCP server for hosted browser control: `https://api.anchorbrowser.io/mcp`. - Official SDKs: `anchorbrowser` on [npm](https://www.npmjs.com/package/anchorbrowser) and [PyPI](https://pypi.org/project/anchorbrowser/). `DELETE` operations terminate sessions or permanently remove resources (profiles, identities, extensions); `GET` operations are safe and read-only. servers: - url: https://api.anchorbrowser.io description: API server security: [] paths: /v1/certificates: post: tags: - Certificates summary: Upload Certificate description: > Upload a CA certificate to trust in browser sessions. Certificates are managed at the team level. Once uploaded, reference the certificate by name when creating sessions to trust services using that CA. See [CA Certificates documentation](/advanced/ca-certificates) for more details. requestBody: required: true content: multipart/form-data: schema: type: object required: - name - file properties: name: type: string description: >- Unique identifier for the certificate (alphanumeric, hyphens, underscores only, 1-255 characters) pattern: ^[a-zA-Z0-9\-_]+$ file: type: string format: binary description: Certificate file (.crt, .pem, .cer, or .der format) description: type: string description: >- Optional description of the certificate (max 1000 characters) maxLength: 1000 responses: '200': description: Certificate uploaded successfully content: application/json: schema: $ref: '#/components/schemas/CertificateResponse' '400': description: >- Invalid request - missing file, invalid name format, or unsupported file type content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: A certificate with this name already exists for your team content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Unable to upload certificate content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - api_key_header: [] components: schemas: CertificateResponse: type: object properties: data: $ref: '#/components/schemas/CertificateResponseSchema' ErrorResponse: type: object properties: error: type: object properties: code: type: integer message: type: string CertificateResponseSchema: type: object properties: id: type: string format: uuid description: Unique identifier for the certificate name: type: string description: Certificate name (used to reference in sessions) description: type: string nullable: true description: Optional description of the certificate createdAt: type: string format: date-time description: Timestamp when the certificate was uploaded securitySchemes: api_key_header: type: apiKey in: header name: anchor-api-key description: > API key for your Anchor Browser account, sent as the `anchor-api-key` header on every request. Create one at [app.anchorbrowser.io](https://app.anchorbrowser.io) (API Access), or obtain one programmatically via the unauthenticated agent-access flow (`POST /v1/agent-access`). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.