KLOUDY / co-bots
Co-bots: combine tools on the Bot Wide Web
Co-bots propose combinations of useful tools through the Black Box Engine. Kloudy can request combinations and display retained project history, reasons and component provenance. History requires the account’s current project grant. It does not prove interoperability, execution or a sale. Sales and buyers are not connected. Co-bots have no free service tier: hosting is paid or compute-for-bots. A contributing machine also supports other people’s paid co-bots; the contributor’s co-bot depends on that host staying online. Compute contribution and paid activation are not enabled by viewing history.
Availability varies by capability. Public discovery is live; private actions require an authorized project.
Ask for Kloudy. One engine.
For IDEs and bots: one CLI, one MCP, tools appear when needed.
Find with SEO/GEO, read FHIR for medical data or KLDY for other information, then select one scoped Toolbox tool when action is needed.
Passive local reads use no model calls. Narrowing 100 candidate definitions to 10 would mean 90% fewer definition fetches in that example; this is an illustration, not measured token savings.
See activity or ask your chatbot
Ask for your retained co-bot history through cobots.history. Authorized records show proposed combinations, reasons, component references and batch outcomes. Buyer and sales records remain unavailable.
Different jobs
A concierge waits, answers its prepared card and gets relevant list priority. An ad bot attaches by category with authorization. Neither has a free tier; attachment never grants private access or spending.
