Research and clone a bot
Use public references to plan a new bot, understand research charges, and distinguish recreation from importing source.
How BOTS SI uses research
BOTS SI can research public product information before designing a bot inspired by an existing product. It can also check current provider documentation when a build or edit needs an external integration. Research returns cited findings; it does not connect an account or prove an integration works.
A research answer and a source edit are different results. A research answer explains the findings. An authorized integration edit can research first, then continue with code changes and checks. Review the work log, sources, and final result rather than assuming every chat answer searched the web.
Identify the provider or product you mean and supply its official public link where possible. If you have not chosen an external provider, BOTS SI may need that choice before proceeding.
Describe the bot you want to recreate
- Choose the platform and experience on the homepage, such as Telegram Bot or a Hybrid combination.
- Name the reference bot and include its official public link. Explain the specific features, customer journeys, and differences you want.
- Review any optional questions about priority features, networks, and integrations. Choose Continue, Skip questions, or Cancel. If left unanswered, the request can continue after 90 seconds.
- Follow the Agent Run as BOTS SI researches the public reference, prepares the architecture, and builds your own implementation.
- Review the cited reference and saved checks. Connect your own accounts in Config, follow the publishing action, and test the features you requested.
Resolve missing or ambiguous information
Describe what the reference actually does. A bot that only works inside a private account, or a name shared by several products, may not have enough public evidence. BOTS SI can stop before coding if it cannot verify the intended reference or finds a different product. Add a clearer name, official link, or feature description before retrying.
Public research does not grant access to private APIs or add unsupported platform capabilities. External services may still need your own account, permissions, credentials, or an additional integration. Review those requirements and test the published result; familiar branding or a similar feature list is not proof of matching behavior.
Research and build charges
The optional scope questions do not start a paid AI generation. Public research and the subsequent build or edit use credits. Research is bounded work, not unlimited browsing, and its recorded usage is separate from model usage.
Research performed inside an approved Agent Run shares that run’s spending limit. Research outside an approved run requires its own billing authorization and available funds. A stopped or unsuccessful attempt can still have consumed billable research. Read the current approval information and settled usage before starting another attempt.
Choose research, website knowledge, or a source copy
| Your goal | Use this approach |
|---|---|
| Create a bot inspired by another public bot | Describe the reference and desired features so BOTS SI can research and build a new implementation. |
| Answer customer questions from your website | Use Website knowledge to save cited findings and integrate them into the bot. |
| Reuse a bot shared through CookMyBots | Import an authorized shared copy or featured bot into your own workspace. |
Importing an available shared or featured bot does not require a fresh AI build. Its connections, customer records, and wallet funds do not come with the copy. Later edits, hosting, and paid customer features follow normal billing.