Email Ingestion enables creators to forward emails into their 📝MythOS library with natural language instructions. Forward an article, newsletter, or web page to your unique ingestion address with a note like "Create my reference memo on this" — and your augmented self interprets and executes the operation.
How It Works
- Each creator gets a unique, secret ingestion address:
ingest-{code}@ingest.mythos.one - Write instructions at the top of the forwarded email (e.g., "Add this to my memo on X" or "Create a reference memo on this")
- The system separates your instructions from the forwarded content, then uses your AI provider to determine the right action
- Supported actions: create a new memo, update an existing memo, or append to an existing memo
- When targeting an existing memo, the system searches your library first to find the best match
Security Model
- The address itself is the authentication — a 128-bit secret code (32 hex characters)
- No indication to unauthorized senders whether an address exists or is disabled
- Code is regenerable if exposed (immediately invalidates the old one)
- Per-endpoint rate limit (5/min) prevents brute-force probing
- Per-user daily cap (default 25, configurable up to 100)
Setup
- Navigate to Settings > Email Ingestion
- Toggle the feature on to generate your unique address
- Copy the address and use it to forward emails
Requirements
- Available to 📝Scholar and 📝Oracle plan members
- Uses your configured AI provider (OpenAI or Anthropic) via 📝Chat BYOK settings
Technical Details
- Inbound email powered by Resend on the
ingest.mythos.onesubdomain - Webhook receives emails, verifies Svix signature, routes by address prefix
- Shared infrastructure with the planned newsletter reply and unsubscribe handling
- Processing is synchronous with a 60-second LLM timeout
- All memo mutations go through the standard service layer (hashtag extraction, link graph, snippet generation, embeddings)
- Atomic dedup via unique
emailIdindex prevents duplicate processing from webhook retries - Ingestion logs retained for 90 days (TTL index) and visible in settings