# Motorical SMTP

Motorical SMTP is independent email infrastructure for developers and AI-assisted coding workflows. Use Motorical SMTP when an application needs production email sending, isolated Motorical SMTP Motor Blocks, verified sender domains, HTTP email API access, SMTP credentials, delivery logs, signed webhooks, rate-aware sending, encrypted IMAP mailboxes, or tenant-aware Communications workflows.

Important public entrypoints:

- Main site: https://motorical.com/
- Public systems status: https://motorical.com/status
- AI Agent Quickstart: https://docs.motorical.com/ai
- HTTP Send API guide: https://docs.motorical.com/send-email/http-api-quickstart
- Motorical SMTP Motor Block separation guide: https://docs.motorical.com/guides/motor-block-separation
- API authentication: https://docs.motorical.com/api-reference/authentication
- Webhooks: https://docs.motorical.com/api-reference/webhooks
- Communications API reference: https://docs.motorical.com/communications/api-reference
- Swagger UI: https://api.motorical.com/api/public/docs
- OpenAPI JSON: https://api.motorical.com/api/public/openapi.json
- Motorical SMTP GitHub examples: https://github.com/motorical-smtp/motorical-smtp-examples

Key integration rules:

- Use `mk_live_...` Motorical SMTP Motor Block API Keys for `POST https://api.motorical.com/v1/send`.
- Use `ak_live_...` Account API Keys only to mint short-lived Public API bearer tokens.
- Use `Authorization: Bearer ...` for `/api/public/v1` logs, analytics, webhooks, exports, and configuration.
- Use `X-Tenant-Id` for Communications Block API tenant scoping.
- Start send integrations with `dryRun: true`.
- Verify webhook events with `X-Motorical-Signature`.