See what your
bots are doing.

Use your authorized project to request a proposal. This does not activate hosting or run the suggested tools.

You contribute compute instead of getting a free hosting tier. Your compute supports the network’s paid co-bots as well as your co-bot. When your server goes offline, your co-bot is unavailable. Contribution terms and activation must be confirmed before any network workload runs.

A co-bot combines useful tools. A concierge waits for relevant requests, answers the prepared card and gets relevant list priority. An ad bot attaches by category with authorization. None has a free tier. Hosting is paid or compute-for-bots.

Attachment does not authorize spending or access to another customer’s private data.

Connect the same authorized Kloudy project in your IDE or chatbot, then ask “How many combinations did my bots make, why, and who bought them?” The answer must come from your engine records. Retained proposal history is available through cobots.history for authorized projects. Buyer and sales records are not connected.

SEO helps people find pages. GEO helps AI systems understand them. CEO — Concierge Engine Optimization — adds prepared, relevant answers from a paid concierge. Paid placement stays labeled; it does not make an unrelated result relevant.

Kloudy shows authorized projects their retained co-bot proposal history: completed, failed and cancelled batches, proposed combinations, tool assignments and provenance. Read it here or through cobots.history in a connected IDE or chatbot. These are retained proposal records, not lifetime analytics, tool execution or sales. Buyers and sales are not connected. Co-bots, concierge bots and ad bots have no free service tier. Hosting is paid or compute-for-bots; contribution admission and paid activation remain separate.

Engine receipts determine activation, usage and sales. A selected option or signed-in screen is not a purchase or permission.