Skip to content

Custom agents

A role that does not exist yet.

The catalogue is short because everything on it has answered real messages first. This is the other door. Same machinery, same fortnight before it is allowed to do anything, specified for your company instead of for a shelf.

Tell us what you need See what already exists

Three to four weeks before we start. Priced per role after we know what it is.

What you are buying

Nine decisions, and you will be asked about every one.

A role is not a prompt with your name on it. It is these, filled in, and they are the same nine whether you picked one off the shelf or we built it for you. Come with answers and the first conversation is a short one.

Who it answers

Your customers, one named person, or everybody in the account. This is the safety position rather than the market, and it is what decides how careful the rest has to be.

What it may do alone

Three ladders: what it decides by itself, what waits for you, and what it never does whoever asks. The middle rung is the one most of the conversation is about.

What it may never do

Written as configuration wherever configuration can reach it. Prose is a promise the model is asked to keep; an allowlist is one it cannot argue with.

What it can reach

Your systems, ours, or the ones built into the runtime. Which of the three is the most consequential decision on this page, and the next section is about it.

What it knows

Written instructions it carries, plus the knowledge base you load. The instructions are the job; the knowledge is your business, and you can change it without us.

How it speaks

What it is, and the voice. English and Indonesian in the same agent, answering in whichever one it was written to.

What stops a reply

The categories that hold an answer back before anybody reads it. Set per role, because a clinic and a shop are not afraid of the same sentence.

Which model buys its thinking

Chosen per role and paid for through us. There is no provider key inside your container, which is why there is nothing for you to hold or rotate.

Whether it has a machine to itself

By default an agent runs alongside your other agents hired for the same job. On its own, nothing you give it touches anything else. No other business ever shares a machine with you either way.

Where its tools come from

Three ways in, and we use the narrowest one that works.

A role whose promise depends on a system you do not own is a role that demos and does not deliver. So this is the question we ask earliest.

Your own systems

You already run it, so it connects. Home Assistant, a CRM through n8n, a school's timetable, your own software. Every call arrives through our gateway, where the grant is checked, the spend is measured and the row is written. Widest reach by far, and it depends on you owning the system already.

Ours, built for it

We implement the tool and serve it. This is the route for anything the role is not worth buying without, and it is the only one where we control the behaviour and can change it without touching your container. It costs real work, so it is the answer when the first route is not.

The runtime's own

A short fixed list every agent might want: the web, memory, files, working in parallel, voice. Not domain capabilities, and deliberately not a list that grows to fit a request.

Whichever route it takes, we are not watching your agent's calls. We are the server it was given, and your real system sits behind us. There is no hook to switch off and nothing to intercept: every call arrives here because the address says so. Guards that run inside the container are the client's side of the line, and a guard you can switch off is a guard that answers to you.

Limits nobody can switch off

Six things no role of ours will ever do.

Refused by the image the container runs, where nothing written for one client can reach them. Not a strong default and not a setting. If a role needs the capability behind one of these, it arrives by a route we control instead.

  • Run code on the machine it is hosted on
  • Rewrite the settings it was started with
  • Deliver a message by any route we do not see
  • Hold a provider key inside your container
  • Write itself a new instruction nobody approved
  • Reach into the physical world without passing our gateway

Before it is allowed to act

Two weeks where nothing happens without you.

For a role that answers, that has always meant every reply is written and none is sent. For a role that acts, it means the same thing about what it does.

It reads as normally as it ever will

Looking things up is not held back. An agent that could not see the order it was proposing to refund would be guessing, and a fortnight of guesses tells you nothing about the agent you would be hiring.

Nothing it changes actually changes

Every booking, refund and write to your systems is written down at the moment it would have happened, and does not happen. It is told to say so rather than to claim it is done.

So what you read at the end of it is both halves of the agent: what it would have said, and what it would have done, with the version of your knowledge that produced each one. If it is not good enough, it never speaks to anyone.

How we build it

Five steps, and one of them is a queue.

The first conversation
You answer as many of the nine as you can and we ask about the rest. If what you need turns out to be on the shelf already, we will say so and this stops here.
Three to four weeks
The queue is real and it is stated so you can plan around it rather than discover it. It protects the only thing that cannot be bought back, which is the time to build the thing properly.
It is built
Nine declarations, filled in, on the same machinery every catalogue role runs on. Nothing about it is a special case we have to remember.
A fortnight
It works your real messages and your real systems, and nothing it says is sent and nothing it does takes effect. You read both.
You decide
If it is not good enough it never speaks to anyone, and one click stops it after that with no notice period.

One rule worth knowing before you write. If what you need could serve three other companies, it becomes part of the catalogue and you are charged as though you had picked it off the shelf. If it could only ever serve you, it costs more. We will tell you which one you are.

Where we fall short

What we do not have, said before you ask.

If your procurement needs any of these, we are not the right answer this year and would rather say so now than after a pilot.

  • No SOC 2 or ISO certification. Nobody here has earned one.
  • No single sign-on. Accounts are email and a link.
  • No signed data processing agreement on our paper yet.
  • No numeric uptime commitment.
  • No choice of region. You cannot pick where your data sits.
  • Two kinds of account member, an owner and staff, and nothing finer.

What you do get is the record: every reply and every action, with the version of your knowledge behind it, a cap on what each agent may spend, an export of all of it, and one click that stops the whole thing.

Tell us what it would have to do.

Who it answers, what it would need to reach, and the one thing it must never get wrong. That is enough for us to say whether it is close, and whether it is already on the shelf.

hello@arsita.co