Docs
belleq sits between your tools and your AI. Connect your tools once, group them into contexts, and give any AI exactly the right access — with memory that follows you across assistants.
Modern AI assistants are most useful when they can reach your real tools — your docs, your issues, your designs. But wiring each assistant to each tool is repetitive, hard to scope, and locks your setup to whichever AI you used last.
belleq is a single layer that holds your connections, your skills, and your memory. You connect a tool once, add skills from a curated library, organize them into contexts, and hand any AI a single link. The AI sees exactly the tools and skills that context allows — and belleq quietly remembers what matters so it's there next time, on any assistant.
One secure login per tool, reused everywhere.
Each context exposes only its allowed tools.
Memory and contexts live with you, not the AI.
Four steps from zero to an AI working inside the right context.
In the dashboard, open Connectors and add a tool — Notion, Linear, GitHub, and more. You log in once; belleq keeps the connection so you never set it up again.
Create a context for a project, role, or task — for example design or support. Choose which connected tools that context is allowed to use.
Each context has its own link. Add it to Claude (or any AI that supports connections) as a custom connector. Your AI now sees exactly that context's tools — nothing else.
Moving from design work to a code review? Switch to a different context's link. The tools, knowledge, and memory change with it — no reconfiguring.
A handful of ideas cover everything belleq does.
A tool you've connected once — Notion, GitHub, Linear, Slack, Figma. Connections are unlimited on every plan and shared across all your contexts.
A named profile that bundles the connections, skills, and knowledge an AI can use. Each context has its own link and its own memory. Create one per project, role, or person.
Ready-made abilities from a curated library. Add a skill to a context just like a connection; every AI, agent, and app in that context can then use it.
belleq learns from how you use AI — what you share, what it fetches, what you decide — and surfaces it when useful. No manual tagging or upkeep.
An autonomous worker that lives in a context. Give it a role and a task and it uses that context's tools and knowledge base to carry it out — on demand or on a schedule.
Your contexts and memory belong to you, not to one AI. Point Claude, ChatGPT, or Grok at the same context and everything is still there.
Open Connectors in the dashboard and choose a tool. You'll sign in to that tool once through its own secure login — belleq never sees your password, and stores the connection encrypted. From then on the connection is available to every context you create; there's nothing to re-enter.
Connectors give an AI your tools. Skills give it new abilities — ready-made know-how for getting a specific kind of job done. belleq keeps a curated skill library: we review the best skills from across the ecosystem, and you add the ones you want to a context, just like a connection.
We review the best skills from across the ecosystem — GitHub, Claude, and beyond — and keep the ones worth using in one library. No sifting through repos or judging quality yourself.
Browse the library and add a skill to a context in a click, exactly the way you add a connected tool. Nothing to install or configure.
Once a skill is in a context, everything working there — any AI you point at it, an agent, or an app — can use it, alongside that context's tools and knowledge.
Because a skill lives in the context — not in one assistant — it travels with everything else. The same skill is there whether you work in Claude today, ChatGPT tomorrow, or leave an agent to run on its own.
A context is a named set of tools for one job. Create one for design, another for support, another for code-review. For each, pick which of your connections and skills it's allowed to use. The AI pointed at that context will see those tools and skills — and nothing else in your workspace.
Every context gets its own stable link in the form:
mcp.belleq.app/c/your-contextbelleq speaks the Model Context Protocol (MCP), so it works with any assistant that supports remote connectors. Add a context's link as a custom connector and authorize once.
Settings → Connectors → Add custom connector. Paste your context link and authorize. belleq's tools appear in any new chat.
In a workspace that supports custom connectors, add the context link as an MCP server. Your context's tools become available to the assistant.
Any client that supports remote MCP servers works. Add the context link as a server URL — no keys to copy, the connection is already authorized.
ChatGPT, Gemini, and your own code can reach the same context over plain HTTP with your context API key — read the REST API docs.
As you work, belleq watches the exchange between you and your AI — the documents you share, the answers it looks up, the decisions you reach — and captures what looks durable into the context's knowledge base. There's nothing to tag and nothing to maintain.
When a later conversation touches the same ground, belleq surfaces the relevant knowledge automatically. Important things stay close; stale things fade. Because the knowledge lives in the context, it's there whether you return on Claude, ChatGPT, or anything else.
A context doesn't just wait to be used — it can work on its own. An agent is an autonomous worker that lives inside a context and already knows its tools and its knowledge base. You give it a role and a task in plain language, and it carries the task out — reading and writing knowledge and calling connectors exactly like you would.
Create an agent from the Agents page in the dashboard, pick the context it belongs to, and describe its job. Run a task straight away to watch it work step by step, or schedule it to run on its own.
Give the agent a role in plain language — "research competitors and summarise findings." It inherits the context's connected tools and its knowledge base automatically; there are no prompts to engineer or keys to wire.
Run a task on demand to test it, or schedule it to repeat — every day, week, month, or year. You pick a date, time, and repeat; belleq handles the timing behind the scenes.
Have the agent message you in Slack, Discord, or Telegram when a run finishes — or chat back and forth with it directly on Telegram, where it answers using its knowledge base.
Set a daily spend budget, pause or archive an agent anytime, and review anything it wants to write to shared knowledge before it's accepted.
Agents run on belleq's managed model out of the box, or you can bring your own key (BYOK or OpenRouter). Either way, a daily budget caps spend, and writes an agent marks as shared wait in a review queue for your approval before they enter the knowledge base.
A context is a scope. Share one with a teammate and they get exactly those tools — never the rest of your workspace. Each context keeps its own memory and a clear record of what the AI saw and used, so access stays accountable.
Scoped sharing means you can hand a contractor a single context for one project and trust that it can't reach anything outside it — no broad workspace access, no copied credentials.
No. You connect a tool once. After that it's available to any context you choose — no re-connecting, no re-configuring.
Everything stays. Your contexts and memory live with belleq, not with whichever AI you used last. Point a new assistant at the same context and it's all still there.
Yes. belleq learns from how you actually use AI and surfaces what's useful. There's nothing to tag or maintain.
Yes. Each context is its own scope. Share one with a teammate and they see only those tools — never the rest of your workspace.
An agent runs on its own. Instead of you prompting an assistant, the agent carries out a task you describe — on demand or on a schedule — using its context's tools, skills, and knowledge base, then messages you the result. You set its budget and approve anything it saves to shared knowledge.
A curated catalog of ready-made abilities for your AI. We review the best skills from across the ecosystem — GitHub, Claude, and beyond — and keep them in one place. You add the ones you want to a context, just like a connector, and every AI, agent, and app in that context can use them.
belleq is in private beta. Join the waitlist and we'll invite you to connect your first tool and add a context to your AI.
Join the waitlist