A Poe user-created bot is an application configuration layered on another AI system, not necessarily an independently trained model. A bot’s instructions and knowledge sources explain far more than its name or public popularity.
Product identity and supported workflows
Poe Creator documentation describes creating a prompt bot by choosing a base bot, setting instructions and optionally adding a knowledge base. Server bots and API bots are different architectures owned by developer and agent specialist teams; the consumer-facing directory should not merge them.
Who it is for and the decision it addresses
An educator might build a bot that answers questions using a publicly licensed course guide. A research librarian might publish a reading-list helper that explicitly refuses unsupported titles. Neither makes the underlying model infallible.
Step-by-step first evaluation
Choose one public sample PDF and write a narrow prompt: answer only from the attached material, say when a question is unsupported, and provide identifiable page references. Test three straightforward questions and two tempting out-of-scope questions. Inspect the bot profile, prompt visibility settings and source behavior from another user account.
Failure modes and limitations
A prompt bot can change when its creator edits the base model or instructions. Unknown creators can upload inaccurate documents or ask users to reveal private information. The appearance of a knowledgeable persona should not be mistaken for professional credential verification.
Privacy, permissions, licensing and governance
Avoid uploading sensitive content to public creator bots without a verified data handling policy for both Poe and the individual bot configuration. The creator’s prompt may be visible, but that alone does not guarantee how the underlying provider handles retained chats.
Exports, retention and avoiding lock-in
Archive the underlying public documents and your original prompt outside Poe. Export of complete bot behavior or historical chat context depends on documented platform options, and server bots may include inaccessible custom code.
Alternatives and team boundaries
A custom GPT is an adjacent user-facing pattern. The model and API reference covers model identity; The agent-security and orchestration reference covers server-side bot operations. This profile is about choosing and evaluating creator-configured experiences.
What remains unverified for each country, version and plan
This October 25, 2026 profile reflects dated first-party product documentation, not independent hands-on testing or an endorsement. Exact country availability, model versions, accessibility provisions, seat entitlements, enterprise residency, retention settings and the whole supported language matrix vary by configuration. Where a plan/region/date combination was not verified with its exact original source, it is left unknown, not assumed worldwide. The product may have changed since the documented feature appeared.
Pricing and evidence boundary
No subscription price, usage allowance, API token rate, special promotional plan, success benchmark or commercial license is asserted here. A dated pricing reference covers independently time-stamped pricing snapshots. Product brochures are supplier claims; human reviewers must check linked evidence against the actual source and retain their own decision trail. No screenshots, borrowed brand assets or pretend product tests are included. Specialist model, media, coding and autonomous-agent deep dives belong to their designated teams.
Sources & Further Reading
Primary vendor documentation accessed 2026-10-25; market-specific terms and feature rollout require additional verification. These sources support stated vendor-product claims, not an independent quality score.