browser_create_profile
Create a new browser profile with randomized fingerprints (user agent, screen size, WebGL, Canvas, etc.). Returns the profile JSON that can be saved for later use. Each profile represents a unique browser identity.
When to use browser_create_profile
Use browser_create_profile when you need to persist and reuse browser identities and fingerprints. It is part of Owl Browser's Profile Management toolset and runs inside a self-hosted, source-level stealth engine, so every call inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Optional
context_idstringOptional browser context ID. If provided, the returned profile snapshots this context's live state (fingerprint, cookies, LLM/proxy config); use browser_save_profile to persist it to disk. If omitted, creates a standalone profile with a freshly generated random fingerprint.
namestringHuman-readable name for the profile to help identify it. Examples: 'Shopping Account', 'Test User 1'. Optional but recommended for managing multiple profiles
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_create_profile do?
Create a new browser profile with randomized fingerprints (user agent, screen size, WebGL, Canvas, etc.). Returns the profile JSON that can be saved for later use. Each profile represents a unique browser identity. It belongs to Owl Browser's Profile Management category and is available through the REST API, the Python SDK (browser.create_profile()), the Node.js SDK, and the MCP server.
What parameters does browser_create_profile accept?
browser_create_profile accepts 0 required parameters and 2 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_create_profile.
Is browser_create_profile detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_create_profile executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.
Related Tools
browser_load_profileLoad a saved browser profile from a JSON file into an existing context. Applies fingerprints, cookies, and settings from the profile. Use for maintaining consistent browser identity across sessions.
browser_save_profileSave the current context state (fingerprints, cookies, settings) to a profile file on the server. Takes a profile_name (not path) and returns the filename. Use browser_download_profile to retrieve the file.
browser_download_profileDownload a saved profile file from the server. Takes the profile_name returned by browser_save_profile and returns the profile content as base64-encoded JSON. The same profile can be downloaded regardless of which context_id was used to save it.
browser_get_profileGet the current profile state for the context as JSON. Includes fingerprints, current cookies, and all settings. Useful for inspecting profile details.
browser_create_contextCreate a new isolated browser context with its own cookies, storage, and optional proxy configuration. Each context acts as an independent browser session. Use this to create multiple isolated browsing sessions, configure proxy/Tor connections, load browser profiles with saved fingerprints, and enable/disable LLM features. Returns a context_id to use with other browser tools.
browser_navigateNavigate the browser to a specified URL. This is a non-blocking operation that starts navigation and returns immediately. Use browser_wait_for_network_idle or browser_wait_for_selector to wait for the page to fully load. Supports HTTP, HTTPS, file, and data URLs. When wait_until is set (load, networkidle, fullscroll, domcontentloaded) and the page declares WebMCP tools, the response includes a webmcp_tools array containing the full tool definitions (name, description, inputSchema). Use browser_webmcp_call_tool to execute any of these tools directly.