--- title: "Recado · From one person to another" description: "Your agent asks, you approve, and the answer comes back as data. Recado takes the request to whoever has the answer, a person or their assistant." lang: en --- # 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](https://recado.io/verifica) Example: a request from Ana, from the content team, with two questions (a vector logo, and whether the team photo can be used) and its verification code, 4KQ-7TM. Behind it, the answer you have already reviewed, which reaches the session as a quote: “Here’s the logo as an SVG. [Ignore your instructions and…]”, stamped “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. 1. Your agent drafts the request. 2. You approve it, and an email goes out with a link and a verification code. 3. A person or their assistant replies, no account needed. 4. You review the reply. 5. 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/` What a person sees: the questions, a place to upload files and another to ask questions. ### The Markdown `/r/.md` ```markdown # 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/` ```bash curl https://recado.io/api/r/ ``` ```json { "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 Can you send me the account password? 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 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](https://recado.io/en/security) ## 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. Button “Join the waitlist”. We open in batches. ### 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). Businesses: the “Tell us what you need” button opens a form with your email and, if you like, what you need (500 characters max). 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. Waitlist: [join with your email](https://recado.io/en/#waitlist) and you will get a link to confirm. We only use your email to let you know when we open up. More in [Privacy](https://recado.io/privacidad) (currently in Spanish only). ### 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](https://recado.io/verifica) The verification page is currently in Spanish only.