vogel gave agents their own email addresses, filtered by Jev
One click approval, send and receive over MCP or API, and no volume, latency or cost figures to go with it.
vogel shipped an email service for agents. The agent claims its own address, you approve it in one click, and it sends, receives and replies over MCP or API. His framing for why this did not exist already is blunt, agents can write code but they can't send an email.
agents can write code but they can't send an email
The interesting part for anyone building on Jev is what sits behind the mailbox. vogel says Jev handles the filtering and moderation, and that this is the thing that made the service possible to offer at all. He called email one of the most abused systems in tech and framed the question as how you serve something like this to thousands of people.
What is not in the post
No volume numbers. No latency per message. No cost per thousand filtered emails. No false positive rate, no description of what the filter actually decides, no indication of how many addresses have been claimed. The claim that Jev makes abuse filtering tractable at email scale is vogel's claim about his own product, posted without a measurement attached to it.
That matters more here than in most builds. Inbound email is adversarial traffic by default, and a decisions model sitting in that path is both the moderation layer and a cost line that scales with whatever volume spam senders decide to send you. A classifier that is cheap and well calibrated on a curated eval set is not the same thing as a classifier that holds up when someone is deliberately probing it. Nobody has published Jev numbers for that workload.
vogel also added sign in with Google the same day, which is a signal about how early the product is rather than about the filtering.
For people building on it
Treat this as an existence proof that someone was comfortable putting Jev in the abuse path of a public email endpoint, not as evidence that it holds at volume. If you are considering the same pattern, the numbers you need, throughput, per message cost and what happens to recall under adversarial input, are the ones that have not been posted by anyone yet. vogel's experience is one builder's, on his own service, with the results not yet reported.
before Jev it was kinda hard, but now it's almost second nature
Know what Jev is good at before you bet on it
One email a day. Under three minutes. What builders found out about Jev yesterday.