TolavoFor builders
You built the AI.
Make the offer.
Turn what you built into a clear offer and a proposal.
Access starts with a conversation about what you have built.
From working AI to a clear offer.
Connect your AI
Point Tolavo at the system you already run; nothing moves.
Define your offer
Set the price, the result in one sentence, and where the system stops.
Send a proposal
Your client opens a link and accepts the exact terms they were shown.
What you declare,
and what Tolavo records.
- Outcome and limits are your words; Tolavo does not check them
- The security section is worked out from the credentials Tolavo stores
- The approval line is written when you publish, not typed
Each correction keeps the version it replaced.
How your system connects.
The difference is who places the call.
- An HTTPS endpoint Tolavo calls
- An outgoing webhook Tolavo posts to
- An n8n webhook
- An inbound webhook your system calls
How this works: the connection
An HTTPS endpoint Tolavo calls
Tolavo calls your address with GET, POST, PUT or PATCH (the run’s input with every method but GET) and records whether your system answered, how long it took and the shape of the reply, by default not the reply itself.
An outgoing webhook Tolavo posts to
Tolavo posts the work to your URL and records that it was delivered; an acknowledgement is not a result.
An n8n webhook
A URL, not an account connection; its “workflow was started” reply counts as an acknowledgement, not a result.
An inbound webhook your system calls
Tolavo gives you a URL and a key, shown once; your system calls Tolavo, and Tolavo cannot start it.
The address has to be public HTTPS
Plaintext HTTP is refused, and so are private and internal addresses. This is enforced when you save the connection, not advised.
How the connection is tested
Tolavo sends a test call and records whether it answered. Testing a connection calls it with a fixed test message instead of your real work, marked with a Tolavo-Probe header so your system can recognise it (a GET connection is called with no body), and passes on a 2xx answer. A failed attempt in the test may be retried under the connection’s retry policy. An endpoint that refuses an unknown body fails the test.
Four ways to authenticate
A bearer token, an API key in a header you name, HTTP basic, or a signature Tolavo adds to every call, so your system can tell the call came from Tolavo (HMAC-SHA256). There is no OAuth.
What has no integration, and is not planned
Make, Zapier, GitHub and container runtimes have no Tolavo integration and none is scheduled. Any can still be reached as a public HTTPS endpoint or webhook URL.
Your AI stays where you run it.
Where it runs
Tolavo does not host or run your system; it calls your address, or you call it.
Where the money goes
Your clients pay you directly. Tolavo never collects, holds or routes their money.
Bring the one you would sell first.
Tell us what you have built and who it is for. A person reads every request.