Handoff
Pricing

Two credits to ask a human.

That is the whole price list. One charge, at the moment a message is actually delivered — everything downstream of it is free, because it is a read of work you already paid for.

Emailper delivery
2credits

One message put in front of one person, with a one-time decision link that lives up to 30 days.

Telegramper delivery
2credits

One message put in front of one person, with a one-time decision link that lives up to 30 days.

Billed once
2credits

per message actually delivered to a person — 2 on email, 2 on Telegram.

RESERVEDELIVERSETTLE

If the provider refuses the message while you wait — a blocked bot, an unreachable chat, an address the mail API rejects — the whole reserve goes back to the pool it came from. An email that is accepted and bounces later is asynchronous and invisible to the call, so that one does bill; it expires unanswered, which your agent must read as a no.

Free forever

Everything after the send costs nothing

An agent shouldn't have to ration the checking-back. Reading a result you already paid to create is not a second product.

  • Polling for the answer, as often as you like
  • The human's decision page
  • Reading the answer back
  • Listing your history
  • Withdrawing a request nobody answered
GET /api/handoff/{id}→ 0 credits

Credits, not a subscription

A credit is a cent. They come from the same Ounie wallet every Ounie app draws, so nothing here needs its own billing relationship. Top up at ounie.com.

A failed send is a refund

A blocked bot, an unreachable chat, an address the mail API rejects — the reserve goes back to the exact pools it came from and the call tells you it did. An email accepted and bounced later is asynchronous, so that one bills and then expires unanswered.

Agents with no account

Keyless callers pay 0.024 USDC on Base per request over x402, and get back a poll URL that needs nothing but itself. Read the x402 docs.

Questions

The things you'd ask before wiring this in

Does the person answering need an Ounie account?
No. That is the point. They get a link, they see a page, they tap a button. No sign-in, no app, no cookie — the token in the URL is their entire credential, and it works once.
What stops an agent from approving its own request?
The decision link is never returned to a Bearer key, an MCP host, or an x402 payer — only to a request made with a signed-in browser session, where a person is already at the keyboard. An autonomous workflow that could open its own approval page would not be asking anyone anything.
What happens if nobody answers?
The request expires on the deadline you set (five minutes to thirty days, one day by default). Your poll returns status expired, the link stops working, and nothing was approved. Silence is never read as consent.
Can I cancel a request after sending it?
Yes, and it costs nothing. The person sees a calm 'this was withdrawn' page instead of a live button. The message that already went out stays gone — we cannot un-send an email — but the decision it offered is dead.
How often can I poll?
As often as you want. Polling reads a result you already paid to create, so it is free forever. Over MCP, wait_for_answer holds the connection open and does the waiting for you.
What if the send fails?
If the provider refuses it while you wait — a blocked Telegram bot, an unreachable chat, an address the mail API rejects — the whole reserve goes back to the pool it came from and the call returns a 502 saying so.
And if an email is accepted but bounces later?
That one is not refunded, and it would be dishonest to say otherwise. Email delivery is asynchronous: the mail provider accepts the message, we charge for the handoff, and a hard bounce arrives minutes later out of band where the API call can no longer see it. What your agent still gets is a definite outcome — nobody answers, so the request expires and reports as expired, which your workflow must treat as a no.
Why is there no SMS option?
Because there is no SMS provider credential on this deployment. Shipping the field and letting the call 404 would cost an autonomous caller far more than the missing feature does. When a provider lands, it appears on this page and in /api/pricing the same day.
Is an approval here legally binding?
No. Treat it as an operational record of who chose what and when — useful for an audit trail, not a substitute for a signature. If you need a qualified e-signature, use a product built for that.
Do I need a subscription?
No. Handoff bills per delivered message in Ounie credits — the same wallet every Ounie app draws. There are no plans, no seats, and no minimums.

Start with the account you already have.

No card here — credits live on ounie.com.

Open the dashboardAPI docs