refund-policy.pdfp. 4
Customers may return any item within 30 days of the delivery date.
AI agent platform
Every agent's access to knowledge bases, tools and the internet is set by you.
Build customer support agent, sales agent, research agent, internal knowledge and other business workflows.
Grounded answers
Upload your documents and the agent answers from them, quoting the exact passage behind each sentence. One answer can draw on several files at once. Hover a sentence to follow it back to its sources.
Answer
Sources
refund-policy.pdfp. 4
Customers may return any item within 30 days of the delivery date.
shipping-terms.md§ Delivery
An order counts as delivered on the day the carrier marks the parcel as delivered.
returns-checklist.md§ Condition
Accept the return only when the item is unworn and still carries its original tags.
How it works
Go from your first upload to a live agent API in three steps, all from the dashboard. If your agent does not need documents, skip step one and start with the model.
Add policies, manuals, contracts or tickets. Commt indexes them into a knowledge base your agents can search. PDF, Word, Markdown and plain text are read.
Name it, pick a model, write the instructions in plain language, and attach the knowledge bases it should read. No prompt engineering background, and no code unless you want it.
Test in the playground, promote from dev to production, then call it from your product with an API key. Set how many requests it gets before a customer ever sees it.
Connections
Give your agents access to the business tools and services they need, and each agent reaches only the ones you allow. Connect through Commt's built-in integrations or extend an agent with MCP.
Messaging and email: Slack, Microsoft Teams, Telegram, WhatsApp, Instagram, Facebook, Reddit, Gmail and Outlook connect an agent to where people already write, from team chat to a customer's inbox.
Work and knowledge tools: Jira, Confluence, Google Docs, Google Drive, Notion, Airtable and GitHub connect an agent to where work gets planned, written, stored and tracked.
Customer and sales tools: Salesforce, HubSpot and Zendesk connect an agent to where customer records, deals and support tickets live.
Zapier connects an agent to tools beyond this list, and an API key connects it directly to your own product.
Need a custom tool? Connect MCP servers to extend what your agents can do. Commt verifies custom MCP servers before they are enabled and alerts you when its checks identify security issues. Learn how MCP works.
Use cases
One platform, one plan. Attach documents when the job needs them, and leave them out when it does not.
Answers from your help centre, policies and past tickets, and says so when the answer is not there.
Returns
Readshelp centrepoliciespast tickets
Point it at the help centre, the billing and shipping policies, and a year of resolved tickets. It replies in the customer's own words rather than quoting policy at them, and the tone and refusals are yours to set. Nothing is invented to fill a gap.
AskCan I switch to annual billing halfway through the month?
AnswerYes. The unused days are credited against the new term.
billing-policy.pdf · p. 2
Reads inbound enquiries, scores them against your criteria and drafts the first reply.
Returns
Readsinbound enquiriesyour criteria
Write the criteria in plain language: company size, budget, timeline, the industries you do not serve. Every inbound form, email and demo request is read against them as it arrives, so the queue is already ordered when your team opens it. Nothing leaves the building on its own.
AskScore this demo request: 12-person agency, no budget stated.
Answer42 of 100. Under the seat floor, and budget is unstated.
qualification-criteria.md · § Fit
Reads long documents and reports back with the passage behind every claim.
Returns
Readsreportsfilings
Attach a folder of reports, filings, papers or transcripts and ask a question that spans all of them at once. PDF, Word, Markdown and plain text are read. A reviewer can check the work instead of taking it on trust.
AskWhich suppliers raised prices more than once last year?
AnswerTwo of nine. Both increases fall in the second half.
supplier-review-q4.pdf · p. 11
Answers the questions your team asks the same three people every week.
Returns
Readshandbooksinternal wikisprocess docs
Expenses, onboarding, VPN access, holiday policy: the questions repeat every week and the answers already exist in writing. Attach those documents and the agent takes the traffic. An agent can only retrieve from the knowledge bases it is bound to, so team-only material stays team-only.
AskHow long do I have to file an expense from a trip?
AnswerThirty days from the last day of travel.
expenses-handbook.md · § Filing
Watches a feed, decides what matters and raises it with the context attached.
Returns
Readsqueueslogsshared inboxes
Point it at a queue, a log stream or a shared inbox. Each new item is read as it lands, against rules you write and can change without redeploying anything. The person on call opens a short summary instead of a raw feed at three in the morning.
AskAnything in the overnight queue worth waking someone for?
AnswerOne. Payment webhook failing since 02:14, 340 retries.
alerting-rules.md · § Severity
Checks contracts and submissions against a checklist you define, and flags what fails.
Returns
Readscontractssubmissionsyour checklist
Define the checklist once: liability caps, payment terms, data clauses, the certificates a submission must carry. Every contract, tender response and supplier form is then walked item by item, in the same order, at the same depth, however long the document is.
Asksupplier-agreement-v3.pdf against the vendor checklist
AnswerThree of twelve clauses fail. No liability cap in § 9.
vendor-checklist.md · § Liability
The dashboard
Every edit starts as a new draft. Change one thing, publish a version, promote it when it behaves.
Models
Frontier models from Anthropic, OpenAI and Google, plus open-source models for everyday volume. Your plan decides which ones an agent can reach, and switching between them is a dropdown, not a migration.
| Model | Provider | Context | Available on | Good for |
|---|---|---|---|---|
| claude-fable-5 | Anthropic | 1M | Enterprise only | Long autonomous runs, end to end |
| gpt-5.6-sol | OpenAI | 1M | Enterprise only | Multi-step coding, agentic work |
| claude-sonnet-5 | Anthropic | 200K | Pro and above | Long documents, careful reasoning |
| gpt-5 | OpenAI | 128K | Pro and above | General purpose, tool use |
| gemini-2.5-flash | 1M | Entry and above | Long context at everyday volume | |
| llama-3.3-70b | Meta · open source | 128K | Entry and above | High volume, everyday tasks |
| qwen3.8-max | Alibaba | 1M | Entry and above | Multimodal reasoning, agentic work |
Entry runs the efficient and open-source models, Pro adds most of the frontier ones, Enterprise has no restriction. Your plan sets how many requests you get each month, and every answer counts as one request. Switching model takes one click and leaves your instructions and your data untouched.
Limits
Your plan includes a monthly request allowance. Commt checks the limit before each request, so an unexpected loop cannot consume the rest of your allowance overnight.
Running · within limit
Security and data
The boundaries every agent runs inside, and exactly what each one covers.
By default, no message text is written to storage. What is kept is the metadata behind your usage report: request counts, latency, which agent answered. Message text starts being written only when you switch on a time-boxed debug window, or when a conversation is flagged as a failure.
Conversation history is kept for a period you choose, from nothing up to a year, never longer. Set it once for the organisation; a project can tighten that period but never extend it. Invoices are the exception: they have to be kept for years, so that setting doesn't apply to them.
Set the topics an agent must refuse, the data it must never repeat back, and what it does when it is not confident. Checked on the way out, before the answer reaches your customer. Available on every plan.
Web search and page browsing are on by default, and you can switch them off when you create the agent. Beyond that, it can only call what you attach: retrieval against its knowledge bases, and any connector you add, such as Slack or Jira. With web access off, those connectors still reach only the service you configured, never the open web at large.
A custom MCP server runs in an isolated environment and is checked for security issues before it can be used. If a vulnerability is found, you are warned and the server stays unavailable until it is addressed. If nothing is found, you are told it is ready to use.
Application, database and document storage run in the EU on private networking. Your files sit in our storage, your vectors in an isolated database, neither on the public internet.
Pricing
Every plan includes a monthly number of requests. When the allowance is used, your agents stop. No credits, no bundles, no expiring tokens.
Startups and Small Teams. Your First Agent in Production.
$349$244/month
Up to 5,000 requests a month.
Request early accessGrowing Teams and Serious Workloads. Agents Your Business Depends On.
$799$559/month
Up to 16,000 requests a month.
Request early accessEnterprise and Custom AI Solutions.
Custom
Request volume set by your contract, invoiced.
Request early accessA knowledge base is one set of documents your agents search. Give each agent its own, or point several agents at the same one.
Prices in USD, billed monthly, cancel any time. Included requests apply to the billing month and do not roll over. A payment method is required before uploading documents, because indexing costs us money the moment it runs.
Early access
Commt is not open to everyone yet. This round has 25 seats available. Leave your email and we will send you an invitation when it is, along with 30% off the plan you pick, locked for 12 months from the day you join.
Doors open 28 September 2026, 09:00 UTC, with 22 of 25 seats left.
No newsletter, and we do not pass your address to anyone.
Questions
A private AI agent is one that reaches only the knowledge bases, tools and connectors you explicitly bind to it, and nothing else. On Commt, you set that scope when you create the agent, choosing which knowledge bases it reads from and which tools and connectors it can call, and every request it answers stays inside that scope.
Yes, by default: a Commt agent can search the web and open pages on every plan, alongside any knowledge bases, tools and connectors you have bound to it. Switch that off when you create the agent to keep it a private AI agent that reaches only what you have explicitly scoped to it, such as Slack or Jira, each limited to the service it connects to, and nothing on the open web.
An agent reaches only the tools and connectors you scope to it, chosen from twenty available. Examples include messaging and email tools such as Slack and Gmail, work tools such as Jira and Notion, and customer tools such as Salesforce and Zendesk, plus Zapier for reaching further tools and a direct API key for calling the agent from your own product.
No, RAG is optional on Commt: an agent can run on its instructions alone, or you can bind it to one or more knowledge bases so it retrieves from your own documents. When you do attach a knowledge base, the agent reads only the knowledge bases bound to it, never anything else in your account.
By default, Commt does not store your message content, only the metadata that produces your usage report: request counts, latency and which agent answered. Message text is written only when you switch on a time-boxed debug window or a conversation is flagged as a failure. You set your own retention period for what is kept, and deleting a record means either removing it outright or anonymising it.
Commt is hosted in the EU. Application, database and document storage run in the EU on private networking, with your files in isolated object storage and your vectors in an isolated database, neither reachable from the public internet.
Commt agents can use frontier models from Anthropic, OpenAI and Google, plus open-source models such as Llama and Qwen, through one integration. Your plan sets which models an agent can reach, and switching a model is a dropdown change, not a migration, so its instructions and knowledge bases carry over unchanged.
Commt uses fixed monthly plans with a defined number of agent requests. Entry includes 5,000 requests and Pro includes 16,000. When the included requests are used, agents stop instead of generating additional usage charges.
When an agent hits its plan's request limit, further requests stop immediately and return HTTP 402 with a machine-readable error code, so your application can show a fallback instead of hanging. Alerts go out at 50, 80 and 95 percent of the limit, the check runs before each request rather than after, and upgrading takes effect immediately from the dashboard.
No, unused requests do not roll over: the requests included with your plan apply to that billing month only. We would rather say so plainly than let you discover it on an invoice, and if you consistently use far fewer than your plan includes, you are probably on the wrong plan.
On Enterprise, yes: you supply your own provider keys, Commt stores them encrypted and never exposes them again, and you keep your existing provider agreement. Commt still handles retrieval, versioning, limits and logs on top of your own keys.
Get started
Build an agent on your own data, watch how it answers, and set its limit before it ever reaches a customer.