Multi-model AI platform
How to use
Poe.
Trying multiple AI models in one interface, comparing responses, and creating focused prompt bots, API bots, or Canvas apps.
Poe is a multi-model AI chat and app platform. Trying multiple AI models in one interface, comparing responses, and creating focused prompt bots, API bots, or Canvas apps. This guide covers the whole path in one place: official access, a first session that produces something reviewable, the checks that make output trustworthy, and the permissions worth limiting before you connect real work.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Access & setup
Find, install, and sign in to Poe
Get into the official Poe experience with the right account and a setup you understand.
- 01
Start at https://poe.com/ and confirm the domain before entering account or payment information.
- 02
Availability: Web, desktop, and mobile experiences with access to official and third-party bots and apps.
- 03
A Poe account and internet connection. Bot access, message limits, pricing, and privacy behavior vary by provider, developer, and plan.
- 04
Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.
- 05
Run one low-risk test task before connecting sensitive files, repositories, or workspace data.
- Use official download pages.
- Review permissions during setup.
- Keep installers and applications updated.
First session
Your first useful Poe session
Learn the interaction loop using a small task with a clear outcome.
- 01
Choose a bounded task and inspect the bot's provider, description, pricing, and privacy shield.
- 02
Avoid sensitive data and provide the same context you would use when evaluating any external model.
- 03
Check important claims against sources and compare another model when the task benefits from contrast.
- 04
Save or share only after reviewing the conversation and its applicable provider policies.
- State the outcome before the background.
- Provide the real source material.
- Review the result before expanding the task.
Quality control
Check the quality of Poe output
Establish that a model's output is reliable enough for the job you are handing it.
- 01
Restate the task, the acceptance criteria, and the failure cost before evaluating any response.
- 02
Test with a fixed evaluation set rather than ad-hoc prompts, so changes are measurable across model versions.
- 03
Check determinism and drift: record model version, parameters, and date, because providers update models underneath you.
- 04
Probe the failure modes deliberately — ambiguous inputs, adversarial phrasing, and out-of-scope requests.
- 05
Validate structure as well as content: confirm schemas, types, and required fields survive real inputs.
- Pin and record the model version with every result.
- Evaluate against a fixed set, not one-off prompts.
- Validate output structure before it reaches downstream code.
Privacy & permissions
Use Poe safely
Understand what leaves your system on every call, and what the provider keeps.
- 01
Classify the data in each request before it is sent to a hosted model.
- 02
Check the provider's retention and training terms for your specific plan, not the marketing page.
- 03
Store API keys in a secret manager, scope them per project, and rotate them on a schedule.
- 04
Strip or tokenise personal and regulated data before it reaches the request body.
- 05
Set rate limits, spend caps, and monitoring so a runaway loop is bounded and visible.
- Poe hosts bots and apps from different providers and developers. Privacy shields, data handling, training use, capabilities, and policies can differ, so inspect each bot before uploading files.
- Follow your organisation's approved-use policy.
- Never treat fluent output as authorization to act.
Core workflows
Step-by-step ways to use Poe for the work it does best.
Each workflow is a separate guide with its own steps and review checkpoints.
Official references
Check the current product documentation.
Features, plan limits, availability, and data controls change. These official pages are the starting points used for this guide.