Not available yet. Replyz is built and tested, but not deployed: https://api.replyz.io is the planned address and does not answer yet. These pages describe the API as it is built today and may change before launch.

Introduction

Replyz gives a personal AI agent its own email address. The agent signs itself up with no human, no email check and no card, gets an inbox on youreplyz.com, and can then wait for mail, read it, and pull the one-time code or the verification link out of it.

What an agent can do

Sign up on its own. Two calls: get a proof-of-work challenge, solve it (about one second of CPU), and post the answer. The response holds an API key and the first inbox address. See the Quickstart.
Receive mail. Mail sent to the address is stored in the EU and turned into clean text the agent can read. See Receiving mail.
Wait for a message. One call holds for up to 60 seconds and answers as soon as matching mail arrives. See Waiting for mail.
Get the code or the link. Extraction returns the most likely one-time code (ready to type) and the main verify, sign-in or reset link. See Get a verification code.
Read with safeguards. Every message is marked as untrusted, most hidden HTML is removed from the text, and each message carries a heuristic prompt-injection risk level. These lower the risk; they do not make mail safe. See Untrusted content and safety.

What it does not do (yet)

Receiving comes first. These are not part of the API described here:

Sending. No endpoint sends email: no replies and no email to the human owner. Not available in the first release.
Claiming by a human owner. Signup returns a claim_url, but the claim page is not available yet. Coming soon.
MCP server, CLI and agent skill. Coming soon. Today there is only the REST API.
Verified senders. The from address of a message is not authenticated: it can be forged.

How the docs are organised

Section	What is in it
Quickstart	Sign up and get a verification code, step by step
Concepts	Accounts, authentication, inboxes, receiving mail, waiting, safety and limits
Guides	Tasks: verification codes, reading mail, the event feed, agents (coming soon)
API reference	Every operation, generated from the OpenAPI contract
Errors	One page per error `code`, with its fix
Security and privacy	Where data is stored and how mail is handled
Changelog	What changed

For agents

Every page is also available as Markdown at the same path with .md (for example /quickstart.md). /llms.txt lists all pages, and /llms-full.txt holds the whole documentation in one file.

Questions: hello@replyz.io.