[ product overview ]

The AI agent that does its own integration work

Algomo maps the APIs your site runs on, connects to them on its own, and takes instructions in plain language. Sierra and Decagon staff engineers on each deployment; Chatbase and Botpress hand you a connector list.

Start free

Where an agent is described, in plain language: what it covers, how it speaks, what it may touch and where it hands off. What it will do is laid out on the screen, so nothing about its behaviour is a mystery.

From your URL to a working agent

Three steps, in this order, and you can do every one yourself. Our team is there if you want a hand.

  1. 01

    Connect the assistant you already use

    Add Algomo to Claude or ChatGPT and sign in through the browser. One command adds Algomo as an MCP server to Claude Code, Codex or Cursor instead. There is no API key to copy and nothing to paste into a settings page, and everything below can also be done from the dashboard.

  2. 02

    Install the extension and let it read the site

    The extension does three jobs. It previews the agent on your site before the snippet is installed, so you test it on your real pages. It maps the site: it takes the sitemap, follows the pages and records the data connections each one makes, and it also records any page you open while it is on. And in a session you start, it lets our team work on an integration with you, in front of you. When the mapping finishes, Algomo holds a map of the endpoints your pages already call.

  3. 03

    Describe the job, and the assistant builds it

    You say what the agent should answer, what it should hand to a person, and what it must never touch. Your assistant turns that into the agent's configuration and stages each change as a diff you read, and preview on your site, before it goes live. What you build shows up on a board, and clicking any piece of it replays the command that made it.

The building blocks behind your agents

Everything you ask for is composed from these, which is why there is no feature list to wait on. If your systems can do it, a request is enough.

Questions, answered

What it does

What counts as a real action?

Anything your site can already do. Its reach is your site's reach: if a visitor could do it on the page, the agent can do it for them, inside the limits you set.

Where does the agent run?

In the visitor's own browser, not on a server pretending to be a visitor. What it sees is exactly what that visitor sees, which is why its answers match the page.

When does it act instead of explaining?

When doing the step is quicker than talking the visitor through it. Where that boundary sits is your call.

Can visitors still do things themselves?

Yes. It acts alongside the visitor, not instead of them.

Control and limits

Can we limit what it is allowed to do?

Yes. The agent can only use the tools you give it, so anything it has no tool for is out of its reach. Within those tools, you set the rules in plain language, and most businesses send refunds and anything that charges a card to a person. When a question needs judgement, it hands over instead of improvising.

Can I change what it does after launch?

Yes, by telling it. A new policy, a new rule, a new limit: say it in plain language and the next conversation follows it. Ask what changed this week and it will tell you, with the call behind any answer you want to check.

What if the agent makes a wrong change?

You throw it away. A change is staged, not live, until you keep it, and the dashboard holds the history of what changed and why.

Do we need training?

No. If you can describe the change, you already know how to make it. Anything you can request in conversation can also be done and seen on screen.

Your stack

Does it work on our stack?

It acts in the visitor's browser session, so it works on any website and needs no platform app. There is no list of supported platforms to check yourself against, because the normal case is a stack that appears on no list.

Do I need to build or expose an API?

No. It uses the same requests your site makes for itself.

What if my site has few discoverable endpoints?

Server-rendered sites expose less for the agent to discover on its own than client-rendered ones do. In that case Algomo is pointed at the systems behind them in a setup session.

What happens when we redesign our site?

Discovery is not a one-off import. If a redesign moves an endpoint, the broken tool is flagged so the mapping can be rebuilt, and the rest keeps working.

Developers and data

Can our own AI tools work with it?

Yes. Everything the agent can see and change is available over MCP, so Claude, ChatGPT, Claude Code or any MCP-speaking tool can run the platform the same way a person does from the dashboard, with nobody in the loop.

Do you copy or index our site?

No. There is no ingestion pipeline for your site: the agent browses the live site to find the answer, the way a person would. That is why answers never lag behind the page, and why a very large site does not hit the limits RAG does. The only stored knowledge is what you add yourself because the site does not have it.

Do you train models on our conversations?

No. Conversations belong to you. We act on your instructions, for your purposes.

Getting started

What do you need from us to start?

A URL. Public endpoints are discovered automatically; anything behind a login is set up together. Someone pastes one snippet into your site and the agent takes it from there.

How long does setup take?

Minutes, not a project plan. The slow part of an agent rollout is normally the integration, and that is the part Algomo does itself.

Can we see it working before we commit?

Yes. Start free puts a working agent on your own site, against your own live data, before a visitor ever sees it and before any sales conversation.

What does it cost?

You pick a rung on the ladder, from free to $4,300 a month, and it buys credits. A conversation that helped someone is five credits, and five more for every further ten replies; spam, abuse and gibberish are not charged. Workflows run free, apart from a hundredth of a credit for a step that calls an outside service or reads your knowledge base; a step that calls a model adds its tokens, and a data-provider call has its own price. The amount you picked is the most any charge can be: no overage, no credit packs. Run out early and you can renew now, or the agent pauses until the month turns. Every number is on this site's pricing page.

Explore more from Algomo

Why Algomo

Why we built an agent that does its own integration work.

Why Algomo

Comparisons

See how Algomo compares to Sierra, Intercom Fin, Decagon and Gorgias.

Comparisons

[ next step ]

Put a real assistant on your website