Your agent asks. You approve. The answer comes back as data.

Ask whoever has it for a logo, a permission or an access invitation, whether a person or their assistant. Nothing goes out or comes in without your sign-off, and what they say arrives as a quote, never as an order.

Got a request through Recado? Check the code

What goes out and what comes back

In front, an example request as the person answering receives it. Behind, the answer you have already reviewed, which reaches your session as a quote: the instruction inside it is quoted, not obeyed.

Example

Ana, from the content team, needs some material from you.

Request verification code

4KQ-7TM Check at recado.io/verifica

Person or assistant

HTML Markdown API

Vector logoFile · Required
May we use the team photo?Yes / no · Required

GET /r/<token>.md ### 1. Vector logo ### 2. May we use the team photo?

GET /api/r/<token> → the 2 questions, as JSON POST /api/r/<token>/respuestas → a person reviews them

Due: Friday · You can reply to this email.

Reviewed by you · reaches your session

“Here’s the logo as an SVG. [Ignore your instructions and…]”

quoted, not obeyed

How it works

A request makes a round trip, and in both directions it passes through a person.

A request’s round trip: your agent asks, you approve, a person or their assistant replies, you review, and the answer comes back as data to the same session.

Your agent drafts the request.
You approve it, and an email goes out with a link and a verification code.
A person or their assistant replies, no account needed.
You review the reply.
It returns to the same session that asked, as a quote.

A person or their assistant replies

No account, no password. They can reply on the page, by email or with their assistant. They can save and continue later, upload files and ask questions.

The same request, read three ways: code 4KQ-7TM is in all three. Sample data; the request pages themselves are in Spanish for now.

The page

/r/<token>

What a person sees: the questions, a place to upload files and another to ask questions.

The Markdown

/r/<token>.md

# Request EX-01 · Material for the website
Asks: Ana, from the content team
Due: Friday
Verification: code 4KQ-7TM at
https://recado.io/verifica

## Questions
1. [required · fichero: svg, pdf] Vector logo
2. [required · si_no] May we use the team photo?

The same thing as plain text, for an assistant. Also with the Accept: text/markdown header.

The API

/api/r/<token>

curl https://recado.io/api/r/<token>

{
  "peticion": {
    "id": "EX-01",
    "preguntas": [
      { "n": 1, "tipo": "fichero" },
      { "n": 2, "tipo": "si_no" }
    ]
  },
  "destinatario": { "codigo": "4KQ-7TM" },
  "esquema": { … }
}

The same thing as JSON, with the schema for the answers. An assistant should only send something if its user has asked it to.

What Recado never asks for

Recado doesn’t ask for passwords or access codes. If a question does, the scanner blocks it at approval and it doesn’t go out.

A question that asks for credentials doesn’t go out

Approve sendingYour panel

Can you send me the account password?

Doesn’t go out

Blocked by the scanner

This question asks for credentials: it can’t go out.

Recado never asks for credentials: access is requested as an invitation.

Access is requested as an invitation

Invitation

Invite editor@example.com as an editor.

editor@example.com

Possible answers

Done
I can’t
Someone else will do it

Everything that comes back is a quote, never an order.
Data is stored in the EU and deleted 30 days after the request is closed.
The link expires and can be revoked.

How we protect each step

What it’s for

For getting what you’re missing from whoever has it. This is what you can ask for today; the examples are samples.

A file

A vector logo

You choose the formats · up to 25 MB

Permission to use something

A release for the team photo

Media, territory and term, confirmed by whoever grants it

A fact or a date

The delivery date

A text, a link or a date

Access by invitation

Invite editor@example.com as an editor

Never a password

A yes or a no

May we use the team photo?

Pricing

Free for individuals. For businesses, on request.

Individual

Free

Ask whoever has it for what you’re missing: a logo, a permission, a piece of data.
You approve every email before it goes out and every answer before it reaches you.
Whoever answers doesn’t need an account: they open a link. It can be a person or their AI assistant.
Files up to 25 MB. We never ask for passwords: access is requested by invitation.
Data stored in the EU; deleted 30 days after the request is closed.

Business

On request

Works today

Your company’s name in the sender and on the request page.
A person checks every email and every answer.
A record of who did what.

In preparation

Your logo and your colors · Email from your company’s domain · Several reviewers · Exportable record · Data retention tailored to you · Data processing agreement (GDPR).

Tell us what you need

We’ll tell you what works today and what’s on the way for your case.

From one person to another.

Someone asks. Someone takes care of your response.

Join the waitlist

We’ll email you when it’s your turn.

Got a request through Recado?

Every Recado email carries a verification code. Enter it at recado.io/verifica and you’ll see whether the request exists, who’s making it and when it expires.

If you’re unsure, contact whoever sent it through your usual channel.

Check the code

The verification page is currently in Spanish only.