Skip to main content

​
Getting Started

No. Sign in at agent.creao.ai and start chatting immediately. Workspaces are an optional way to organize your agents and files as your usage grows.
Yes. Sign up for free and start using the super agent right away. The Free plan includes the core super-agent experience; plans differ in credits, support, access to premium models, and a small number of resource-intensive generation capabilities.
Anything you’d ask a technical teammate: generate a web app, analyze a dataset, draft a report, scrape a website, create charts, send emails, build PDFs, automate workflows, and more. The super agent runs code in a full Linux sandbox, so it can install packages, call APIs, and produce real files — not just text responses.

​
Agents

An agent is a reusable workflow built from a successful chat session. Instead of re-prompting the same task, you save it as an agent with structured input fields. Anyone on your team can run it with different inputs, and every run is tracked with version history.
After a successful chat session, click Create Agent in the chat toolbar. The super agent analyzes the conversation and extracts the workflow into a reusable agent with a structured input form, a skill definition, and version control.
Yes, on Pro Plus or higher. Open any agent, go to the Schedule tab, and configure a recurring schedule — daily, weekly, monthly, or a custom cron expression. Scheduled runs execute autonomously and consume credits like manual runs. On Free or Pro, existing schedules stay saved but don’t run until you upgrade.

​
Skills and Connectors

Skills are instruction packages that teach the super agent how to perform a task (like a recipe). Connectors give the super agent access to external services via MCP (Model Context Protocol) — Gmail, Slack, Google Sheets, GitHub, and more. Skills define behavior; connectors provide integrations.
Yes, three ways: install from a public GitHub repo URL, upload a ZIP file containing a SKILL.md, or ask the super agent to create one directly in chat. Custom skills use a simple markdown format with YAML frontmatter.
CREAO supports a growing connector catalog including Gmail, Google Calendar, Google Sheets, Google Docs, Google Drive, Google Tasks, Google Ads, Google Analytics, Google Search Console, Outlook, Microsoft Teams, Asana, Linear, Notion, Slack, Discord, Facebook Ads, Reddit, YouTube, GitHub, Semrush, Perplexity, Firecrawl, X, Telegram, Shopify, eBay, and gated previews such as Etsy. Check the Skills and Connectors page for the latest list.
A connector can access only the data allowed by the permissions (scopes) you approve with that provider. Access is scoped to the connected account and the connector’s authorized capabilities. See Connector Security for an overview.
Yes. You can disconnect a connector in CREAO at any time. For complete revocation, you can also remove CREAO app access from the provider’s own security settings.
When you connect your own AWS account (Bring Your Own Cloud), CREAO does not store long-lived cloud credentials. You deploy a CREAO-provided CloudFormation stack in your account that creates a cross-account IAM role; CREAO assumes it on demand using short-lived STS credentials gated by a per-connection ExternalId. The agent reads only what the tool you triggered returns — read-only CloudWatch logs, metrics, and alarm states for debugging. Those tool results flow into the agent’s context, which means they are sent to your selected LLM provider as part of the conversation (the same as other connector data); CREAO does not bulk-export or continuously ingest your cloud account. You can disconnect at any time (which also deletes the stored connection), or delete the CloudFormation stack in your own account. See Privacy and Cross-Account Cloud Access (BYOC) for details.
Your device runs a small daemon that registers its available capabilities (like running shell commands, transferring files to or from the device, or a custom MCP server you configure) and receives lightweight task notifications over AWS IoT Core, then fetches the durable task over an authenticated connection. Each task is checked against your device’s local consent policy — allow, deny, or ask (an interactive prompt in the desktop app). New pairings default to ask for the shell-command capability, so nothing runs unattended until you decide otherwise. Long-running tasks continue without keeping the chat open, show durable status and deadlines, and can be stopped from their task card. You can pause or revoke a device at any time. See Device Connect Security for details.
Built-in skills are instruction packages, not standalone third-party services. Data is shared externally only when required by model providers or connected tools used during execution. See Skill Security.
They run under the same platform security boundaries, but their trust model differs. Built-in skills are curated by CREAO, while custom skills are user-provided instructions and should be reviewed before enabling.

​
Data Privacy

CREAO does not train its own models on your conversations, files, or data. Anthropic, OpenAI, Google, MiniMax, Z.AI, Moonshot AI, Thinking Machines, DeepSeek (open weights), Fireworks AI, Meta (Muse Spark models via the Meta Model API), and BytePlus are accessed under API agreements or provider API terms that prohibit training use. MiniMax M3 conversation requests are served by Fireworks AI under CREAO’s Fireworks account (Fireworks’ API terms prohibit training use) — if Fireworks returns a capacity error, the request is automatically retried via OpenRouter and served by DeepInfra, Novita, or Together AI under OpenRouter’s API terms, which prohibit training use — while MiniMax’s own API is used for CREAO’s internal response-quality evaluation under MiniMax’s API terms, which prohibit training use; Moonshot AI and Thinking Machines’ Inkling are reached via OpenRouter, whose API terms prohibit training use, and GLM 5.2 / Moonshot AI requests may be served by Fireworks AI under CREAO’s Fireworks account — Fireworks’ API terms also prohibit training use. GLM 5.3 and GLM 5.3 Flash are the exceptions among the Z.AI models: they are sent directly to Z.AI under CREAO’s own Z.AI API agreement, which prohibits training use, so their conversation content reaches Z.AI and no other company — not even a relay. (GLM 5.2 is still reached via OpenRouter. CREAO can move the GLM 5.3 models onto that path as a fallback, in which case OpenRouter relays the request and Z.AI still performs the inference.) Muse Spark 1.3 and 1.2 go directly to Meta by default, and reach OpenRouter only if CREAO moves them onto that path as a fallback, in which case OpenRouter relays the request and Meta still performs the inference, being the only host OpenRouter offers for those models (Muse Spark 1.1 has no such fallback). DeepSeek V4.1 Flash is served by default through OpenRouter, preferring Fireworks AI under CREAO’s Fireworks account. Conversation messages, context, and attached images reach OpenRouter and the serving inference host; OpenRouter may use another host if Fireworks is unavailable. DeepSeek’s own API is excluded from Flash routing. These paths prohibit training use under their API terms. Selecting Flash does not keep content exclusively on CREAO-managed systems; the self-hosted V4 checkpoint is a separate, explicitly selected legacy route. DeepSeek V4 Pro uses a different serving provider: it is NOT self-hosted — every conversation request for it is relayed via OpenRouter and served by DeepSeek’s own API by preference (GMICloud as a fallback), so conversation content for that model IS sent to DeepSeek, under DeepSeek’s and OpenRouter’s API terms, which prohibit training use. Fugu Ultra via Sakana AI is a qualified exception while governed by Sakana’s public Fugu terms: submitted content may be used for Sakana training or improvement unless an opt-out or separate no-training/DPA arrangement is in place, so do not use Fugu Ultra for regulated, sensitive, confidential, or personal data without that confirmation.
Data is stored in cloud infrastructure and protected with encryption in transit and at rest. Execution runs in isolated sandbox environments.
CREAO estimates your approximate location from your IP address at login. A country code is used for analytics, abuse detection, and billing routing, and CREAO may also derive a coarse city/region estimate, used for regional analytics and to segment location-relevant CREAO marketing and lifecycle emails by area. This estimate is approximate — it reflects your network, not a precise position, and can be wrong (VPNs, mobile carriers). CREAO does not collect GPS or precise-location data, and only the coarse city/region estimate — never your raw IP — is shared with our marketing-automation provider (customer.io) for this. Because CREAO does not yet operate a per-user consent mechanism for location-based marketing, users in the EU/EEA/UK are excluded from it entirely. You can opt out of marketing emails at any time via the unsubscribe link or your notification settings. See Privacy for details.
Yes. You can delete conversations, files, and memory entries, and request CREAO account deletion. A limited audit record of a deletion request itself may be retained where required for legal, compliance, and security purposes, as described in the Privacy policy. A Developer Platform account created at developer.creao.ai is a separate product account and is not removed by CREAO account deletion; request that erasure at privacy@creao.ai.One deletion request can also be initiated automatically: if you joined CREAO only by accepting a team seat invite (a team-only account, with no personal workspace) and you later leave your last team, CREAO files an account-deletion request on your behalf, since the account has no remaining purpose. Like any deletion request it is reviewable and reversible before it is finalized.
CREAO is designed around core privacy rights including access/export and deletion. Enterprise customers can request a DPA. See Privacy for details.
Yes. The CREAO iOS and iPadOS app (Apple App Store) shows two notices that web and Android do not:
  1. Before sign-in — you must accept CREAO’s Privacy and Personal Information Protection Agreement before creating an account or signing in.
  2. After sign-in — before using AI features, you must acknowledge that your messages, files, and other content may be sent to third-party AI providers (such as Anthropic and OpenAI) for processing.
You can review the full policy anytime from Account Settings → Privacy. See Privacy for details.
Secrets are encrypted at rest and injected at runtime for execution. Values are not shown in plain text after creation, except through whitelisted and logged campaign audit exports used by authorized admins to verify trading activity. Trading-campaign secrets, including WEEX API credentials and the S2 debot developer API credentials (DEBOT_API_KEY / DEBOT_API_SECRET), are not stored in campaign tables. S2 never collects a wallet private key — debot’s custodial wallet API signs Robinhood Chain transactions server-side.

​
Sandbox and Environment

Your sandbox stays active for the duration of the conversation. Installed packages, created files, and running processes persist between messages. After 30 minutes of inactivity, the sandbox pauses automatically — everything is saved and resumes in about one second.
Yes. Every chat thread gets its own sandbox. Work done in one thread never affects another. Agent runs also get isolated sandboxes, created from the agent’s saved environment snapshot.
Yes. Add your API keys as Secrets from the Secrets page. They’re encrypted at rest and injected into the sandbox as environment variables (process.env.YOUR_KEY). The super agent can use them in code execution.

​
Memory and Context

Yes. Memory is cross-thread — when the super agent learns a preference, fact, or decision, it saves it and recalls it in future conversations. You can view, search, and delete memories from the Memory page.
Memory persists across all conversations indefinitely — use it for durable facts like preferences and decisions. Thread notes are scoped to a single conversation and help the super agent maintain context during long sessions.
Dream is an automatic profiling feature that consolidates your conversation history into a concise portrait of who you are — your role, preferences, working style, and recent decisions. Like the brain during sleep, Dream replays your past conversations offline and distills patterns into a structured profile. This profile is injected into every new conversation so the super agent already knows you from the first message. You can view your Dream profile, trigger a manual regeneration, and browse previous versions from the Memory → Dream tab.

​
Pricing and Limits

CREAO offers five plans. Every plan includes the core super agent; plans differ in credits, support, premium or gated models, and a small number of resource-intensive generation capabilities.The Free plan requires no credit card. Every plan includes the core AI super agent — memory, code execution, web search, custom agents, and built-in, custom, and open-source skills. Free includes 1 personal connector per agent app. You can connect more than one account, but combining personal connectors in one agent requires a paid plan. Paid plans add more credits, higher support levels, and premium models. Pro Plus and above also add scheduled runs and durable long-running video and audio renders, with each higher tier raising how many scheduled runs and renders can run at the same time.
The core product works on every plan, including the free tier — chat, memory, skills, one personal connector per agent app, custom agents, and the API Trigger (programmatic agent runs via API keys) all run on credits from your balance. A few distinctions are paid-only: premium models — the top-tier Claude models (Fable and Opus) and Fugu Ultra — require a paid plan, and free-plan users pick from simplified model tiers rather than hand-picking a specific model. Some preview or entitlement-gated models are available only to eligible accounts. Scheduled runs and durable, long-running video and audio renders require Pro Plus or higher — Free and Pro schedules stay saved but don’t execute until you upgrade, and each tier from Pro Plus up raises how many can run at the same time. Generated PDFs longer than 10 pages also require a paid plan; quick renders and PDFs up to 10 pages remain free on every plan. Video generation on the Free plan is limited to one video per rolling 30-day period; on paid plans, additional video generations simply consume credits from your balance. See Models.
Yes. You can purchase credit packs at $0.15 per credit from the pricing page, on top of your plan’s monthly allocation.
CREAO supports multiple models including Claude (Fable, Opus, Sonnet, Haiku), Gemini, GPT variants, GLM 5.2, Kimi K3, MiniMax, Muse Spark, and Fugu Ultra. Generation-focused models include Veo (video) and BytePlus Seedance / Seedream (video and image). You can select your preferred model from the model selector in the chat interface.

​
Data Privacy

CREAO does not train its own models on your conversations, files, or data. Anthropic, OpenAI, Google, MiniMax, Z.AI, Moonshot AI, Thinking Machines, DeepSeek (open weights), Fireworks AI, Meta (Muse Spark models via the Meta Model API), and BytePlus are accessed via API agreements or provider API terms that prohibit use of your data for model training. MiniMax M3 conversation requests are served by Fireworks AI under CREAO’s Fireworks account (Fireworks’ API terms prohibit training use) — if Fireworks returns a capacity error, the request is automatically retried via OpenRouter and served by DeepInfra, Novita, or Together AI under OpenRouter’s API terms, which prohibit training use — while MiniMax’s own API is used for CREAO’s internal response-quality evaluation under MiniMax’s API terms, which prohibit training use; Moonshot AI and Thinking Machines’ Inkling are reached via OpenRouter, whose API terms prohibit training use, and GLM 5.2 / Moonshot AI requests may be served by Fireworks AI under CREAO’s Fireworks account — Fireworks’ API terms also prohibit training use. GLM 5.3 and GLM 5.3 Flash are the exceptions among the Z.AI models: they are sent directly to Z.AI under CREAO’s own Z.AI API agreement, which prohibits training use, so their conversation content reaches Z.AI and no other company — not even a relay. (GLM 5.2 is still reached via OpenRouter. CREAO can move the GLM 5.3 models onto that path as a fallback, in which case OpenRouter relays the request and Z.AI still performs the inference.) Muse Spark 1.3 and 1.2 go directly to Meta by default, and reach OpenRouter only if CREAO moves them onto that path as a fallback, in which case OpenRouter relays the request and Meta still performs the inference, being the only host OpenRouter offers for those models (Muse Spark 1.1 has no such fallback). DeepSeek V4.1 Flash is served by default through OpenRouter, preferring Fireworks AI under CREAO’s Fireworks account. Conversation messages, context, and attached images reach OpenRouter and the serving inference host; OpenRouter may use another host if Fireworks is unavailable. DeepSeek’s own API is excluded from Flash routing. These paths prohibit training use under their API terms. Selecting Flash does not keep content exclusively on CREAO-managed systems; the self-hosted V4 checkpoint is a separate, explicitly selected legacy route. DeepSeek V4 Pro uses a different serving provider: it is NOT self-hosted — every conversation request for it is relayed via OpenRouter and served by DeepSeek’s own API by preference (GMICloud as a fallback), so conversation content for that model IS sent to DeepSeek, under DeepSeek’s and OpenRouter’s API terms, which prohibit training use. Providers may retain data briefly for abuse monitoring and safety per their terms, but not for training on those paths. Fugu Ultra via Sakana AI is a qualified exception while governed by Sakana’s public Fugu terms: submitted content may be used for Sakana training or improvement unless an opt-out or separate no-training/DPA arrangement is in place.
All data is stored on cloud infrastructure in the United States. Data is encrypted at rest using AES-256 encryption and in transit using TLS 1.2+. Each chat thread runs in an isolated sandbox that is destroyed after the session ends.
CREAO estimates your approximate location from your IP address at login. A country code is used for analytics, abuse detection, and billing routing, and CREAO may also derive a coarse city/region estimate, used for regional analytics and to segment location-relevant CREAO marketing and lifecycle emails by area. This estimate is approximate — it reflects your network, not a precise position, and can be wrong (VPNs, mobile carriers). CREAO does not collect GPS or precise-location data, and only the coarse city/region estimate — never your raw IP — is shared with our marketing-automation provider (customer.io) for this. Because CREAO does not yet operate a per-user consent mechanism for location-based marketing, users in the EU/EEA/UK are excluded from it entirely. You can opt out of marketing emails at any time via the unsubscribe link or your notification settings. See Privacy for details.
Yes. You can delete individual conversations, files, and memory entries at any time from the respective pages. To delete your CREAO account and its associated data (agent.creao.ai and CLI), go to your account settings, where you can optionally tell us why you’re leaving. Account deletion is processed within 30 days. A Developer Platform account created at developer.creao.ai is not removed by that request; email privacy@creao.ai to erase it. A limited audit record of the deletion request itself (such as request metadata, an email snapshot, any reason you shared, and any administrator handling notes) may be retained afterward where required for legal, compliance, and security purposes, as described in the Privacy policy.
CREAO is designed with GDPR and CCPA principles in mind. You have the right to access, export, and delete your data. We collect only the minimum data necessary to provide the service and do not sell your personal information. Enterprise customers can request a Data Processing Agreement (DPA). See the Privacy page for full details.
Secrets are encrypted at rest and managed via a dedicated secrets store. They are injected into your sandbox as environment variables at runtime and are never logged, displayed in the UI after creation, or stored in plain text. For S2 debot trading, the participant’s own debot developer API credentials (DEBOT_API_KEY and DEBOT_API_SECRET) are treated as user secrets and are injected only for the participant’s Agent runtime when it executes a live Robinhood Chain (EVM) action through debot’s custodial wallet API. No wallet private key is collected or stored — debot signs transactions server-side.
Only you can see your conversations by default. If you use the Share feature, a read-only public link is generated — anyone with the link can view that specific thread and download any files or artifacts within it. Shared links can be revoked at any time. Team members in a shared workspace can see workspace-scoped agents and files, but not your private conversations.

​
Files and Data

HTML pages, PDFs, SVGs, spreadsheets (XLSX, CSV), images, code files, documents, and more. Generated files appear in the artifact preview panel during chat and are saved to your Files page automatically.
Yes. Drag and drop files into the chat input or click the attachment icon. Supported types include images (PNG, JPG, GIF, WebP), documents (PDF, TXT, CSV), and code files (HTML, CSS, JS, Python, etc.).