One call out. One tap back.
Handoff is deliberately small. It does not orchestrate your workflow, hold your state, or decide anything on your behalf. It does one thing an agent cannot do for itself: get a real answer from a real person, and hand it back in a shape you can branch on.
- 01
Your agent hits a line it shouldn't cross alone
Refunding a customer, deploying on a Friday, emailing a list, deleting a bucket, signing anything. You decide where the line is; Handoff is what happens at it.
- 02
It calls Handoff once
Channel, recipient, the question in plain language, and the buttons you want offered. The call reserves credits, sends the message, and returns immediately with a request id — it does not sit there holding your connection open.
- 03
A person gets a message they can act on
Email or Telegram, with a single link. The link opens a page built for one thumb on a phone: who is asking, what they want, and the buttons. No account, no app, no sign-in.
- 04
They tap once, and that's the decision
The link works exactly once. A second tap, a refresh, a back button, or a mail scanner following the URL all land on the same recorded answer — nothing gets decided twice.
- 05
Your agent picks it up
Poll the request until status flips to answered, or let the MCP wait_for_answer tool hold the line for you. Either way it is free — you already paid for the delivery.
- 06
Or nobody answers, and that means no
Every request carries a deadline (1440 minutes by default). Past it the link dies, the status reads expired, and your agent knows it never got permission. Silence is never treated as consent.
Where the money goes, and where it doesn't
- 01Your agent callsPOST /api/handoff with the question and who to ask.
- 02A human gets itEmail or Telegram, with a one-time link. No account needed.
- 03They decideOne tap on a hosted page built for a phone.
- 04You poll, freeGET the request until status flips to answered.
- 05Your agent resumesWith a real answer, and a record of who gave it.
2 credits per delivered message, either channel. Reserved when you call, settled when the provider accepts it, refunded in full when the provider refuses it while you wait.
Polling, the decision page, reading the answer, listing your history, cancelling an unanswered request. Reads of paid work are free.
Not a signature product, not a workflow engine, not a chat channel. An approval here is an operational record of who chose what and when.
Ready to wire it in?
The API is four endpoints, and two of them are free.