| ▲ | mrklol 7 hours ago | |
Looks like SES + api access, isn’t Amazon offering that already? | ||
| ▲ | ktanishqk 7 hours ago | parent | next [-] | |
> Because we built the same inbox infrastructure as Gmail. Inboxes have threads, threads have messages, messages have attachments. You can search, label, filter, reply, forward. None of this comes out of the box with SES. aws just gives you a low-level smtp + api service. we are the application layer they do not offer but your agents need to actually use email as first-class users. | ||
| ▲ | yard2010 4 hours ago | parent | prev | next [-] | |
This alone doesn't give you gmail UX - threads, inboxes, tagging, etc. | ||
| ▲ | mpeg 7 hours ago | parent | prev [-] | |
No offence, but this reads to me like the classic dropbox HN comment The idea is pretty solid, automation platforms often provision a mailbox per flow for this reason, so it makes sense to make a generic service that can be used through MCP for agents | ||