VOICE → RESEND · SAFETY-FIRST
Make Resend voiceable.
A spoken word never executes.
Operate Resend by voice — safely. Every destructive action is gated behind a deliberate confirmation.
5 actions · 3 writes · 2 gated as destructive
Get early accessEXAMPLE COMMANDS
What you can say to Resend.
Generated from the Resend spec — these are the real utterances the parser is built to handle.
“send an email with from you@acme.dev and to alice@example.com”needs confirm“retrieve a single email with id abc123”read-only“list all domains”read-only“create a domain with name acme-web”read-only“remove an API key with id abc123”needs confirm
PER-ACTION SAFETY
Every write, classified.
Destructive actions are gated; reads run free. No destructive action is ever left unflagged.
| Action | Endpoint | Class | Why | Blast radius |
|---|---|---|---|---|
sendEmail | POST /emails | ⚠ destructive | irreversible/costly action: “send” | Sends a real message — irreversible once it leaves. |
getEmail | GET /emails/{id} | read-only | read-only — safe to run without a gate | No side effect. Read-only. |
listDomains | GET /domains | read-only | read-only — safe to run without a gate | No side effect. Read-only. |
createDomain | POST /domains | read-only | read-only — safe to run without a gate | No side effect. Read-only. |
deleteApiKey | DELETE /api-keys/{id} | ⚠ destructive | irreversible: HTTP DELETE | Permanently removes the resource. |
AUTH & SETUP
Connecting to Resend.
Resend authenticates with Bearer token. Voxy stores only a vault reference — your secret is never written inline in the config or sent to the browser.
| Scheme | Bearer token |
| Header | Authorization: Bearer <token> |
| Where to get it | Create a token / API key in the API's dashboard, then store it in your vault. |
| How Voxy stores it | As a vault reference (keyring:voxy/resend) — never the literal secret. The gate and execution run server-side; the secret never reaches the client. |
FAQ
Questions about Resend by voice.
How do I authenticate Voxy with Resend?
Resend uses Bearer token. You generate the credential in the Resend dashboard and store it as a vault reference; Voxy never holds the literal secret and never sends it to the browser. The credential is attached server-side when a confirmed action runs.
What can I do in Resend by voice?
This page exposes 5 Resend actions generated from its OpenAPI spec: sendEmail, getEmail, listDomains, createDomain, deleteApiKey. For example, you can say things like “send an email with from you@acme.dev and to alice@example.com”.
Which Resend actions need confirmation?
2 of the 5 actions are classified destructive or costly and are gated behind a deliberate click: sendEmail, deleteApiKey. Voxy shows a read-back of exactly what it will do, and nothing runs until you click confirm.
Is operating Resend by voice safe?
Yes — safety is the whole point. A spoken word never executes a destructive action. Every irreversible or costly Resend call (like sendEmail) requires an explicit on-screen confirmation, and destructive detection runs at 100% recall, so nothing dangerous is silently executed.
Do I need a Resend API key to try the demo?
No. The demo on this page is parse-only: it understands your command, shows the parsed call and read-back, and stops at the gate. It never calls Resend and needs no keys. A key is only required when you wire Voxy to your live Resend account.
Does Voxy change my Resend setup or require code?
No code and no changes to Resend. Voxy reads the Resend OpenAPI spec to generate the voice layer; you keep using Resend exactly as before and add a safe voice/natural-language way to run these actions.
← More in Email & Messaging · All integrations
Give Resend a voice.
Keep the safety.
Early access is rolling out across the Tier-1 APIs. Point Voxy at your spec and get a gated voice agent.
Request access