An AI team that does the work, and stops for you.
Describe a job once. Claritty runs it across the tools you already use, on a schedule, and nothing is sent until you say so.
Free, and no card. It runs for real, five times.
This week
↑ 12%52
bills chased
Waiting on you
12
to approve
Books Watch
Active 2m ago
Overdue
QuickBooksAcme
61 days
Globex
34 days
Initech
12 days
Umbrella
8 days
Chased 52, none sent without you
Since midnight
- 07:02Drafted 4 replies
- 08:26Booked 2 interviews
- 09:14Stopped for your approval
- 09:31Sent the one you approved
Approval
It stops before it acts.
Every write waits for a person. The message carries what it read, what it is about to do, and the exact words it will send.
See it stop for you
Invoice chaser paused before acting.
Found 3 items, and wants to send a Slack message.
Ran on its schedule.
What it found
• List bills · Quickbooks — 3 items, vendor: Acme, amount: 4200 (find bills past their due date)
What it will do
Send a Slack message to #finance
3 bills are overdue, totalling 5220.
Approve it here, ask for changes, reply in this thread, or open it. Approving performs only the above, and re-uses what it already read, so nothing is charged twice.
Where you are
It comes to you, not the other way round.
Slack, WhatsApp, Telegram or email. It says what it did, what it could not finish, and what is waiting on you.
Get it in your SlackTuesday, 8 September
9:41
A run needs your approvalnow“Invoice chaser” paused before acting.
- Slack9:14 AM
✅ “Chase overdue invoices” — Weekly AR sweep just ran. 3 bills are overdue, totalling 5220.
- Gmail8:02 AM
⚠️ “Weekly digest” — the Notion sync run hit a snag. I’ll retry on the next schedule.
- TelegramYesterday
✅ “Answer the overnight tickets” — Support Desk just ran. 34 resolved, 2 waiting on you.
The team
A team arrives with a roster.
Each teammate has the job it was built for, the tools that job needs, and a name you can hand work to.
Hire a team freeThe team
Inbox Chief
Triage
Sorts the overnight mail
Working…GmailDrafter
Drafts the routine replies
Active 12m agoGmailCalendar
Protects the calendar
Ready — no tasks yetGoogle Calendar
The room
Watch them work it out.
They post into one room. When two of them disagree about a bill, it asks you once, remembers the answer, and stops before it sends.
Open your own roomBillsChases what is owed
ReceiptsFiles the receipts
PaymentsWatches the charges
BillsChases what is owed
You
BillsChases what is owed
BillsChases what is owed
Proof
Every action leaves a receipt.
The other system's own reference, kept as it came back, and who approved it. Where there is no reference it says so.
See your own receiptsWhat it actually did
Every real action, with whatever the other system gave back as proof.
- Emailed Acme a payment reminder9:14 AM
Gmail · 198a4f2c9d1e77b0 · you approved
- Posted the overdue list to #finance9:14 AM
Slack · 1727.4242 · you approved
- Filed the receipt against the bill9:15 AM
Notion · a41f8c2e · unattended
- You sent one the team had written9:31 AM
your word, no receipt from anywhere · approver not recorded
- Marked the Acme bill settled9:32 AM
QuickBooks · no reference returned · you approved
No API
Some jobs have no API.
Record yourself doing it once in the browser. It watches the steps, not the data, and asks when a step could mean two things.
Record your first jobvendorportal.com
Invoices
Blurred here for the same reason they are not in the recording.
Connections
No connector? It builds one.
It checks whether it already reaches the system you named. If it does not, it finds the API, works out which keys it needs, and builds a connector for that step.
Connect your tools
35 connected out of the box. The platform runs the whole sign-in for 15 of them.
Not one of them?In build
It finds the API and builds the connector.
No API at all?
You do the job once and it watches.
Credentials are encrypted with AWS KMS and brokered server-side. They never reach app code.
The library
65 jobs it already knows.
Start from one of these, or describe your own. Either way it comes back as a team you can hand work to.
Generated from the live catalog. Anything this deployment cannot run is dropped before it reaches this list.
Questions
The ones people actually ask.
What it does that the others do not, how you teach it, and what it costs.
Start freeClaritty builds and runs automations for the work you repeat by hand. You describe the job in plain language, Claritty wires it into the tools you already use, and it runs on a schedule. You see what it did every time, and anything that acts on your behalf waits for your approval. Start from a ready-made automation or describe your own.
ChatGPT helps you do the job faster. You still do it. A Claritty automation does the job itself, on its own schedule, against your real tools, whether or not you open anything. An app builder hands you code and leaves you owning its maintenance and its security. Here the automation runs on the platform and your credentials are brokered server-side, so they never reach app code.
With Zapier or Make you assemble the steps: pick a trigger, add the actions, map the fields between them. That suits a rule you can state exactly. With Claritty you describe the outcome and it composes the automation, then puts an agent on the steps that need a decision rather than a rule. The graph is something it produces, not something you maintain.
You describe the job and it comes back as a team: named teammates, each with the job it was built for and the tools that job needs. Where a step could mean two things it asks you once rather than guessing, and it keeps your answer for the next run instead of asking again. The rest of the teaching is the approvals, because you see exactly what it is about to do before it does it.
Then you show it. Install the Chrome extension, do the job once the way you always do, and read back the steps it wrote. It watches what you do rather than the data on the page, and it asks when a step could mean two things. That is the work no connector reaches: a carrier portal, a council system, the back office you log into every Monday.
Every action leaves a receipt: what was done, in which system, and the reference that system gave back. Where the other side returned no reference it says so rather than showing you a tick it cannot support. Anything you did yourself is recorded as your word with no receipt from anywhere, because that is what it is.
Only where you have said it can. Every write waits for a person, and the message you get carries what it read, what it is about to do, and the exact words it will send. You can approve that one run, ask for changes, discard it, or approve and stop being asked for that job.
Safety is architectural, not a promise: integration credentials are AES-256 encrypted with AWS KMS and brokered server-side, so they never touch app code. Each app runs in its own isolated runtime with its own database schema. See our Security page for the full control-by-control picture.
Free is $0, no card: build up to three automations and actually run them, five times, taking real actions on a schedule. Pro is $25 a month and lifts the five-run ceiling, adds building your own apps and teams, 2,000,000 credits and a smarter model. Business is $129 a month with 10,000,000 credits, your whole team, the most capable model, and bring-your-own-key. Credits refill every cycle.
No. Ready-made automations install in one click with a guided setup, and building your own is a conversation rather than code. Developers who want full control can also build with Claude Code or Codex and publish via the Claritty CLI.