Sharing Bots

AISCouncil encodes bot configurations directly into the URL fragment (the part after #). This means you can share a bot by simply sharing a link -- no server, no account, no setup.

How It Works

When you share a bot, the configuration (name, provider, model, system prompt, temperature, max tokens) is:

1. Serialized using short keys for compactness (n, p, m, s, t, x)
2. Compressed with deflate
3. Encoded in Base80 (a custom alphabet optimized for URL density)
4. Prefixed with a VLQ version byte
5. Placed in the URL fragment: bcz.co/#B{encoded_config}

The recipient opens the link, and the app decodes the configuration instantly in the browser.

API Keys Are Never Shared

Bot URLs contain only the configuration -- never API keys. When a recipient opens a shared bot URL, they use their own API keys (stored locally in their browser). This is a core security guarantee of the platform.

Keys are stored in localStorage under ais-apikey-{provider} and are excluded from all URL encoding and data export operations.

URL Format

bcz.co/#B{base80_compressed_bot_config}

• B is the VLQ version prefix (version 1 for bot configs)
• The payload is Base80-encoded compressed data
• The fragment (#...) is never sent to a server by the browser

Sharing Workflow

1. Configure your bot (name, model, system prompt, etc.)
2. Click the share button
3. Copy the generated URL
4. Send it to anyone -- email, chat, social media, documentation

The recipient opens the URL and gets your exact bot configuration. They add their own API key and start chatting.

No Server Required

Because the configuration lives entirely in the URL fragment, there is no server-side component involved in sharing. The app can be hosted on any static file server, CDN, or even opened from a local file. The URL is the bot.