Add abilities and persistent storage
Discover supported abilities, inspect what is installed, and ask for records that survive normal bot use.
Read the capability evidence
Capabilities has Installed and Discover views. Installed maps abilities and interactions detected in the bot’s source. The feature map can include commands, buttons, AI, media, scheduling, storage, external APIs, or a web interface. Requested outcomes track what your prompt asked for separately from what testing has proved.
Source detected means code evidence was found. Build checks, service access, and platform delivery are separate observations. Read dates and details: an older or cached response does not verify today’s full journey.
Discover and add an ability
- Open Capabilities, choose Discover, and search for an outcome such as storage, voice notes, weather, or image generation.
- Read the ability’s setup, supported platforms, limitations, availability, and usage information.
- If integration is available, select Add with BOTS SI or Extend with BOTS SI. Describe what customers should be able to do.
- Review the normal edit information and submit. BOTS SI creates a checkpoint and validates the change. Publish and test the update separately.
The catalogue also covers web search, text to speech, audio transcription, crypto research and news, crypto artwork, prices, token-risk indicators, world time, and Bitcoin sentiment. Read each card’s support and pricing. Customer payments are coming soon; video generation is unavailable until supported access is verified. Configured access can still be unverified.
Adding an ability through BOTS SI can incur an edit charge. Using a paid service through that ability creates separate usage charges from your wallet. An installed ability does not include unlimited use. Check the card’s pricing and Billing for the services your customers use.
Ask for the records you need
Request persistent storage for bookings, tasks, tickets, or journals. Describe the records and who may create, edit, or read them. Specify per-person isolation and owner administration. Keep public knowledge and private records under different access rules.
Test saving a record, retrieving it in a later conversation, updating it, and attempting access from another account. If restart persistence matters, verify that journey too. Seeing database helpers in source is not proof that records survive a restart. A database setup warning should be resolved through the indicated configuration before publishing.