Custom Agents · no code required

Build your own AI agent, then put it everywhere

Name it, tell it how to behave, connect the datasources it should know and the tools it’s allowed to use. Then use it in chat, call it from the API, or drop it on your website to answer customers.

Create your agentTry the builder
admin.klartai.com/dashboard/agents/newLive builder — try it

Create your agent

Four steps. Nothing to install.

Draft — autosaved
Accent colour

Tone, scope, what to refuse, when to escalate to a human.

A working model of the real builder — click the steps, rename the agent, toggle sources and tools.

Knowledge and actions are separate on purpose

Most agent builders blur the two and you lose track of what your agent can touch. Klart keeps the line sharp.

Datasources — what it knows

Read-only. The agent answers from these and cites them; when the answer isn’t there it says so instead of inventing one.

Drive, Notion, Confluence, Jira, your website, uploaded files

Existing permissions are inherited, never widened

Re-indexed as content changes — no stale answers

Tools — what it can do

Write access, granted one action at a time. Every tool can require your approval before it runs.

Create tickets, update CRM records, send email, file issues

Any internal API: endpoint, auth header, JSON parameters

Every call logged with who asked, what ran, what came back

One agent, three surfaces

Build it once. Your team uses it in chat, your product calls it over the API, your customers meet it on your site.

N

Nova

Customer Support

New chat

Recents

Refund for order 44192

Is the API rate limit per key?

Customer says the enterprise plan was billed twice in March — what’s our policy and can you fix it?

Duplicate charges inside 60 days are refunded in full, no approval needed. I’ve refunded $2,400 on order 44192 and emailed the customer a confirmation.

Billing policy §4Account: Northwind
refund_order ranemail sent

Ask Nova anything you need…

Nnova
Surface 01

Your team just picks it from the list

A published agent shows up in workspace chat next to Klarty and the rest. It answers with citations, and when it runs a tool you see exactly which one ran.

Cited answers, so anyone can check the source

Tool receipts in the thread, not hidden in a log

Also reachable from Slack and Microsoft Teams

What teams build first

Three custom agents that pay for themselves in a week.

O

Onboarding agent

Answers every new-hire question from the handbook and IT wiki, and files the access requests itself.

DriveConfluenceJira tool
T

Tier-1 support agent

Sits on your site, resolves the repeat questions, and opens a ticket with context when it can’t.

WebsiteNotion FAQZendesk tool
R

RFP response agent

Drafts answers from past bids and security docs, cites each one, and logs the deal in the CRM.

DriveUploadsSalesforce tool

Custom agents, answered

No. Naming it, writing its instructions, connecting datasources and enabling tools all happen in the dashboard. Code only enters the picture if you choose to call the agent from the API or embed the widget yourself.

A datasource is what the agent knows — it reads from it. A tool is what the agent can do — it writes, creates or triggers something. Keeping them separate is what lets you give an agent deep knowledge and almost no power, or the reverse.

Yes. Publish it to workspace chat for your team, to the API for your product, and to the website widget for customers — each surface with its own permission scope.

Yes. Add a custom tool with your endpoint, method, auth header and a JSON schema for the parameters. The agent then calls it like any native tool, and you can require approval before each run.

Scope is set per surface. A datasource attached for internal chat can be excluded from the widget, and the agent answers only from what its surface is allowed to read. User permissions are inherited on top of that.

That depends on your plan. Most teams start with two or three — one internal, one customer-facing — and add more as each proves itself.

Build your first custom agent today

Name it, connect what it should know, choose what it can do. Publish to chat, API and your website from the same screen.

Create your agentTalk to sales