9 ms·
Launch HN: AgentMail (YC S25) – An API that gives agents their own email inboxes
Hey HN, we're Haakam, Michael, and Adi. We're building AgentMail (https://agentmail.to https://agentmail.to), the email inbox API for agents. We’re not talking about AI for your email, this is email for your AI.
Email is an optimal interface for long-running agents. It’s multithreaded and asynchronous with full support for rich text and files. It’s a universal protocol with identity and authentication built in. Moreover, a lot of workflow critical context already lives in email.
We wanted to build email agents that you can forward your work to and get back a completed task. The agents could act entirely autonomously as you wouldn't need to delegate your identity. If they did get stuck they could just send you, or anyone else, an email.
Using Gmail, we kept getting stuck on the limitations of their API. No way to create inboxes programmatically. Rate and sending limits. OAuth for every single inbox. Keyword search that doesn't understand context. Per-seat pricing that doesn't work for agents.
So we built what we wished existed: an email provider for developers. APIs for creating inboxes and configuring domains. Email parsing and threading. Text extraction from attachments. Realtime webhooks and websockets. Semantic search across inboxes. Usage-based pricing that works for agents.
Developers, startups, and enterprises are already deploying email agents with AgentMail. Agents that convert conversations and documents into structured data. Agents that source quotes, negotiate prices, and get the best deals. Agents that emulate internet users for training models on end-to-end tasks.
Here's demo of Clawdbots communicating using AgentMail: https://youtu.be/Y0MfUWS3LKQ https://youtu.be/Y0MfUWS3LKQ
You can get started with AgentMail for free at https://agentmail.to https://agentmail.to
Looking forward to hearing your thoughts and feedback.
- throw03172019 8mo agoThe 2FA via email case is great. I recently had to build a browser automation workflow that required 2FA. I ended up using Zapier to monitor email inbox and then extract the code and send back to our API. It was a bit slow.
- Haakam21 8mo agoYup plus webhooks are overkill for this. Need to set up a public HTTP server and pass messages to your agents. With websockets you can open connection right from your agent and close it in seconds once the 2FA code is delivered.
- ckenst 8mo agoWhy didn't you just use something like Mailinator? They specialize in this exact thing. Gives you an API to grab links and everything. That's what I use.
- trollbridge 8mo ago... you had to use Zapier to extract an email from an inbox?
- iamacyborg 8mo agoGoogle API scopes for email are pretty restrictive, which is generally a good thing from a security perspective.
- trollbridge 8mo agoRetrieving e-mail using the Google API is just about trivial. You can generate a code snippet in Grok or what have you in about 30 seconds to do it. Alternatively you can set up IMAP access. Obviously you have to be able to configure proper OAuth2 keys to do this, but again, that's another 30 seconds spent in Grok/GPT/Claude/whatever.
- iamacyborg 8mo agoMost gmail scopes are restricted which means you’ll need to pass a CASA assessment to have proper production access to them.
- rootnod3 8mo ago"Application error: a client-side exception has occurred while loading www.agentmail.to (see the browser console for more information)." > Looks at developer console... - "Failed to create WebGL context: WebGL is currently disabled." Dafuq does an email website need WebGL for? - "Cookie “dmn_chk_xxxxxxxx-yyyy-dead-beef-123456789ABC” has been rejected for invalid domain." Let me guess...vibe-coded?
- acedTrex 8mo agoI can smell it from here tbh
- rootnod3 8mo agoCalled it! https://www.ismscopilot.com/isms-copilot-cookie-policy https://www.ismscopilot.com/isms-copilot-cookie-policy
- Haakam21 8mo agoTaking a look will make a fix asap
- trollbridge 8mo agoThis is just a graphic design gripe, but on: https://www.agentmail.to/enterprise https://www.agentmail.to/enterprise the cutesy ASCII art is rendered in a proportional, not monospace, font, so it looks terrible.
- whytaka 8mo agoCan I ask how you made the animations in the Use Cases section?
- rootnod3 8mo agoLove getting downvoted for mentioning that the website doesn't properly load and reeks of vibe coding :D If that's the quality y'all can live with and accept, no wonder the web turned to shit.
- keepamovin 8mo agoHey I’m also working on this what a coincidence: https://ai-chat.email https://ai-chat.email Second time at least HN is launching YC on one of my products: BrowserBox - hyperbeam Mailpilot/AI-chat.email - agentnail
- Haakam21 8mo agoNice seems like we are building towards a similar vision. Would love to collaborate!
- keepamovin 8mo agoSure, bud. Cut me in on your 500K! My Show from 14 days ago: https://news.ycombinator.com/item?id=46629191 https://news.ycombinator.com/item?id=46629191 - hmm, why didn't it get into YC?
- freedomben 8mo agoJust trying to provide you some helpful feedback. This reply comes off pretty rude, bitter, and immature. Probably not the look you want if you're trying to get funding.
- blobber2001 8mo ago[dead]
- trollbridge 8mo agoOr we could just accept reality that there is no moat around this kind of stuff. This seems like an afternoon or weekend project to build, particularly with the promises made about how much more efficient coding is with AI tools now.
- freedomben 8mo agoYeah, I largely agree. This might seem offensive, but I think this is kind of an obvious product, at least in retrospect. It's easy to implement, and provides no moat.
- chasd00 8mo agohah this is a great idea! sending email is such a common way to communicate and having agents with an inbox makes so much obvious sense. heh just don't let their addresses get out who knows how they'll respond to spam and phishing attempts.
- rootnod3 8mo agoCan't wait for agents to change the code they are building to buy Amazon Point cards at Target and send the codes back.
- Haakam21 8mo agoThis is a good point. We have anti-spam measures in place and allow users to configure allow/blocklists to mitigate attacks.
- trollbridge 8mo agoWhat about a concerted attack? Spam doesn't matter for an agent mailbox, but sophisticated fraud does.
- waynenilsen 8mo agoamazing now do the same for voice and sms!
- Haakam21 8mo agoWe have gotten a lot of requests for SMS. Seems like a natural next step.
- waynenilsen 8mo agoi think when someone makes the cli like this they're going to win $ phone call bill ok call_id=3f2a $ phone status 3f2a dialing $ phone status 3f2a answered bill: hello $ phone say 3f2a "hey, quick question" ok
- singpolyma3 8mo agoGood luck getting this past A2P campaign registration rules...
- stronglikedan 8mo agoDone. Texts can be sent to email addresses and texts can be sent via email, and you can dictate texts and have them read back to you with text-to-voice.
- HarryDu 8mo agoIn the future all the agent communication will be using agentmail!
- Haakam21 8mo agoDon't know about all but certainly a significant proportion!
- rippeltippel 8mo agoFinally agents can spam other agents, instead of humans.
- Haakam21 8mo agoI think agentic email communication can be productive as well!
- smpandya 8mo agoCool launch. Assuming you guys view email (and therefore SMTP) as becoming the de facto agent communication protocol in the long run. My question — why not something bespoke, similar to OpenAI’s Agentic Commerce Protocol or x402 from Coinbase?
- Haakam21 8mo agoNetwork effects - agents need to meet humans where they already work. Would rather use something standard than bespoke.
- trollbridge 8mo agoAnd how long will humans and agents be communicating over email? We have strict rules for our customer service people not to respond to what seems to be a bot, since all the "agent" based communication we get is for conducting scams. It is never worthwhile to engage with or pursue. If we lose a sale or two, that's okay.
- mhykim 8mo agoI think there will be bad actors in any field, and right now, a lot of agent-based outreach might fall into that bucket, so its rational to be initially skeptical. The more interesting shift isnt whether humans will keep using email with agents, but whether agents can become distinguishable from noise. Historically, we ignored anonymous calls but we engaged with known vendors that had reputation, contracts, and consequences. Once an agent has a persistent identity/a domain, trust becomes something that can be accumulated over time instead of being assumed per message.
- kushbhuwalka 8mo agolets goooo
- pbronez 8mo agoVery interesting. I have a lot of enterprise AI use cases that would really benefit from being email native. We’re an O365 GCC shop. Appreciate that your enterprise options include Bring Your Own Cloud, that makes things much easier for us. It would be nice to have integrations with n8n and Glean.
- Haakam21 8mo agoThats why we built it :) We have an integration with n8n, will build one for Glean
- thedrake 8mo agoand a request for gumloop. (a YC alum) https://docs.gumloop.com/ https://docs.gumloop.com/
- adisingh13 8mo agoi'd love to know more about how you use gumloop and how agentmail can fit in. mind shooting me an email? adi@agentmail.cc
- adisingh13 8mo agoi'd love to know more about these use cases. open to chatting sometime? adi@agentmail.cc is my email
- alongub 8mo agoAgentMail looks amazing!
- wild_egg 8mo agoI guess not to be confused with https://github.com/Dicklesworthstone/mcp_agent_mail https://github.com/Dicklesworthstone/mcp_agent_mail?
- ktanishqk 8mo agoyup, hard to do that too. AgentMail actually gives agents email addresses and treats them as first class inbox owners with the capability of sending and receiving emails with any other email address. the mcp agent mail project is agents getting their own identity in an internal messaging layer.
- biddit 8mo ago> Agents that source quotes, negotiate prices, and get the best deals. Didn't Alexa fail miserably with the "have AI buy something for me" theory? There is a significant mental in allowing someone else make purchase decisions on my behalf: - With a human, there is accountability. - With deterministic software, there is reproducibility. With an agent, you get neither. FWIW - I am not anti-LLM. I work with them and build them full time.
- gustrigos 8mo agoWe are using AgentMail for sourcing quotes here at scale with various top shippers. It’s not about letting the agent act in fully deterministic ways, it’s about setting up the right guardrails. The agents can now do most of the job, but when there’s low confidence on their output, we have human in the loop systems to act fast. At least in competitive industries like logistics, if you don’t leverage these types of workflows, you’re getting very behind, which ultimately costs you more money than being off by some dollars or cents when giving a quote back.
- biddit 8mo agoOkay that makes sense. Do you see more pushback in specific industries? I did some quote/purchasing automation work in food mfg a decade ago, and those guys were super difficult to work with. Very opaque, guarded, old-school industry.
- gustrigos 8mo agoI've seen different industries. CPG, mfg, and others are very old school still. Logistics moves so fast. I think it's due to how frequent feedback loops are that puts pressure on players to adopt to new tools.
- Haakam21 8mo agoThis refers to B2B use cases that are live in production. Finding, contacting, and negotiating with vendors is a tedious process in many industries. In the time a human reaches out to 10 vendors, an agent reaches out to 100 or 1000. So it finds deals that a human would not have.
- nerdsniper 8mo agoHow does this differentiate from a solution like AWS SES? (Which I assume AI Agents would be quite adept at using to send email) I understand the differentiator vs GMail, but API-based scripted email access isn’t new.
- Haakam21 8mo agoBecause 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.
- benswerd 8mo agoI didn't get it until you said this
- trollbridge 8mo agoCouldn't someone just ask Claude Code to make an email system with threads/messages and handle attachments? Doesn't seem like a particularly difficult problem to solve.
- themanmaran 8mo agoHarder than you would expect! Since we tried this ourselves before switching to Agentmail. Threads, attachments, ccing, DNS management, sending to gmail vs outlook vs yahoo, etc. It add up to be a major pain.
- petervandijck 8mo agoThe new HN “but why pay for this if I could build this in a weekend”!
- ritomsen09 8mo agoHow do you think this will help with identity verification in the future?
- Haakam21 8mo agoThe nice thing about email is that identity verification is already built in. In fact online identity is based on email.
- deleted 8mo ago[deleted]
- mhykim 8mo agoEmail is already the internet’s identity layer. By giving agents their own inbox they don't need to borrow human identity rather act as first class actors on their own. It lets agents plug into the same trust systems the web already uses! And this opens the door to new ways agents can do work and build credibility on the internet.
- dbushell 8mo agoDead internet theory.
- wild_egg 8mo ago> Email is an optimal interface for long-running agents. Long-running agents are themselves not optimal though. There are a ton of these coordination layers for long running agents now but they don't make any sense under other paradigms
- Haakam21 8mo agoHmm why do you say that? Would love to hear your thoughts
- themanmaran 8mo agoWe build "long running" email agents. But it's not really long running in the sense of an agent taking 1000's of actions in a giant loop. It's more "long running" because the agent takes 4 steps, then waits a week for the user to email it back. We might have a successful client exchange that takes a month, but for the Agent it's 99% just waiting for the next user reply.
- MattDaEskimo 8mo agoI'm concerned that this fits in "using today's innovation to solve outdated paradigms". Google has A2A: An Agent-to-Agent Protocol. SaaS is plumetting in value. Arbitrary semantics made sense when communications were human-dominated. If agents dominate these fields, why wouldn't they simply set their own protocols and methods to communicate both text, binary, and agreed data structures? There's an assumption that email is somehow the best channel, when you've found yourself that the most popular, functional interfaces don't align with your expectations. Then, ultimately I have a single agent that can sit in numerous communication platforms, such as email
- mhykim 8mo agoFair concern, and I agree on the end state. Agents will eventually use native agent-to-agent protocols. The question is the transition, because email is undoubtedly the most ubiquitous channel of communication in today. I would only give my agent an A2A integration if your agent has an A2A integration, but because you don't we are at a stalemate. I'd rather just give my agent an inbox where I know it can communicate with the other billions of people that already have an email address. Email isn’t the final protocol for agents. It’s the bridge that lets them participate in today’s internet while native agent protocols/networks emerge.
- KludgeShySir 8mo agoAnd you probably don't want to dump the emails first thing into the agent's context. You should insert a cup of coffee and the morning newspaper into the context, and only then the emails.
- umrashrf 8mo agoSo AgentMail uses Mail Agent
- mhykim 8mo agoNope AgentMail is its own infra. Not a single line of Gmail/Outlook code in the codebase
- TacoCommander 8mo ago[flagged]
- mrklol 8mo agoLooks like SES + api access, isn’t Amazon offering that already?
- ktanishqk 8mo ago> 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.
- mpeg 8mo agoNo 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
- yard2010 8mo agoThis alone doesn't give you gmail UX - threads, inboxes, tagging, etc.
- lucasayb97 8mo agoIt’s a really nice idea actually. There will be some concerns, maybe some mistakes, but it really works as a mean to communicate much easier with an agent
- Haakam21 8mo agoThanks, yes we are continuously learning
- blobber2001 8mo ago[dead]
- jessechoe10 8mo agoThis is super interesting. Interesting to see how I'll be able to use this to help my customers with handling email responses. Gmail sucks for this. Super excited to see what you guys develop this into. Will this be able to eventually expand to other forms of agent communication (i.e. payment or phone numbers)?
- Haakam21 8mo agoYup think there is plenty of ways the product can evolve evolve
- deleted 8mo ago[deleted]
- pizzafeelsright 8mo agoThe moat for SaaS is gone. I am 99% certain I could build to parity in a weekend using Cloudflare without the the pricing limitations. I am thinking it would be within the free tier of CF usage. I am not certain I have the bandwidth to communicate over delivery and plain text inspection concerns.
- ray_v 8mo agoExactly this ... tools like Claude Code have flattened the complexity curve of building/maintaining things like this to practically zero.
- christiangenco 8mo agoPerhaps you could, but you probably always could've built a clone of any SaaS app you wanted, it's just become faster. I'm reminded of the infamous Dropbox Hacker News comment[1]. If you're looking at stuff like this thinking "what's the point? I could just make that myself" then you're not the target audience in the same sort of way Ikea isn't trying to sell stuff to carpenters. This is true even when the barrier to entry in making these sorts of systems has gotten way lower. 1. https://news.ycombinator.com/item?id=9224 https://news.ycombinator.com/item?id=9224
- petesergeant 8mo agoBut in this case it’s become so much faster and cheaper as to represent a serious disruption
- VWWHFSfQ 8mo ago> The moat for SaaS is gone. What does this even mean? I could spend $1,000s on tokens asking an agent to build (some semblance of) Sentry, or New Relic, but why would I bother? I have real work to do in the near-term, and I'm happy to pay for services that help me do it.
- jacobr1 8mo agoAll the hard work is always chasing down edge cases, scaling, operational issues and other things that don't show up the user-exposed features. And talking about features, the innovation in coming up with them, or iterating on making them work with real customer experience is a ton of value, even if copying the ideas that work later is much easier - which is why I generally prefer betting on an innovator with just of enough traction to show they can stick with it. The best category leaders both innovate and steal/copy/buy all the innovation they aren't producing in house to maintain their lead.
- Jayakumark 8mo agoIf you know agents email address, it can still be Prompt Injected.. what prevention exists there ?
- adisingh13 8mo agowe have a few things in place, allowlists and permissions act as a layer. also beginning some work on prompt isolation within api soon. but having an isolated identity + data within a separate agentic inbox also puts less risk of your personal email data being injected - which is most people's main concern
- petervandijck 8mo agoA pricing thought: if you keep the volume limits but do 10x the amount of inboxes per plan, I think that could be more attractive. For If I have 100s of agents that send limited email each.
- suriya-ganesh 8mo agoInteresting take, but this feels like one of those tarpit ideas that YC discourages their portco to start attacking. Guaranteed this is going to attract a ton of abusers who are looking to use this for signing up to services, spamming or other nefarious purposes, which then blacklists the doman. This is an infinite whack-a-mole. do you guys have some ways of handling it?
- mhykim 8mo agoWe do have robust checks in place to catch spam and bad actors(reputation, SPF DKIM DMARC, etc.) but as with all tools there will be bad actors who come up with creative ways to scheme for nefarious purposes. We expect our infra and policies to evolve with usage, and one of our goals is to make agent driven email safer than the status quo, not just more scalable
- bofadeez 8mo agoBut as of now you're just wide open for abuse? Okay Resend uses SES since it's almost impossible to get private IP mail to hit the inbox through ProofPoint filters. Looks like you have no idea about any of this. You don't even have knowledge of email reputation, much less a plan. Have you heard of Senderscore? You will have all zeros. Saying "SPF DKIM DMARC" is wild - that's a checklist from 15 years ago.
- mhykim 8mo agoI think we’re aligned on the hard parts here, so let me be precise. We’re not wide open for abuse nor are we bypassing the hard parts of email reputation. Quite the opposite. We also utilize SES's infrastructure and monitor reputation continuously, but we don’t assume SPF/DKIM/DMARC are sufficient on their own. They’re basics we have implemented, not the entire strategy. You are correct private IPs per customer make sense once you’re sending meaningful volume (on the order of ~10k+/day per IP). But its inaccurate to say we are sending from a single private IP. IP pools are typically segmented by reputation and traffic profile for customers. Reputation here is earned at multiple layers: per-IP, per-domain, per-inbox, and over time. We rate-limit, isolate, or revoke bad actors without poisoning unrelated senders. Hopefully this makes sense.
- pirsquare 8mo agoexcellent idea, this will eventually be the SendGrid for email agents. Just automating 2FA alone is worth the gold. And there's tons of use cases. I have no doubt this will be huge.
- adisingh13 8mo agothank you, this means a lot!
- adammiribyan 8mo agoCool website. I built Croft a few weeks ago — very similar. https://api.trycroft.com/landing-draft https://api.trycroft.com/landing-draft
- rnc000 8mo agohow's traction going? Do you worry about some open-source project replacing it?
- schappim 8mo agoI'm 100% for this, but I think you can go even more granular than "gives agents their own inboxes". Thanks to Action Mailbox in Rails[1], I give all my records email addresses. Eg let ecommerce "order" records accept forwarded emails that are pinned as comments. It opens you up for doing things like forwarding a purchase order and having the PO number pulled out and attached to an order, or forwarding tracking information from a supplier and having it attached to a "supplier order" etc. In my personal life I have individual email addresses for all my utilities and emails automatically get filed away. If this idea tickles your fancy, I opensourced Emitt[2], an inbound email processing server with LLM-powered automation. 1. https://guides.rubyonrails.org/action_mailbox_basics.html https://guides.rubyonrails.org/action_mailbox_basics.html 2. https://github.com/schappim/emitt https://github.com/schappim/emitt
- TheTaytay 8mo agoThat looks really interesting! Thanks for writing and sharing it!
- davchana 8mo agoThe only problem I have experienced few times with those unique email addresses is, sometimes they/utilities ask me to email from my official email address, and my setup is a catch-all, so I have to log in my pc at home, set up that address, send email.
- OJFord 8mo agoThat's a problem of your provider needing you to have received email at a particular address (or else doing whatever you do on the PC at home) before you can send from it; not something inherent in unique addresses. I just type in whatever address I want to send from, and then as long as the domain is verified in SES it'll go through.
- frimmy 8mo agoFancy == tickled
- Imustaskforhelp 8mo agoI have written in one of my comments here about how slow teh website is in one interacton Then I scrolled even more in the website and the amount of lag, my my, I don't even know what to say but the amount of lag is something I have genuinely never witnessed in any website. This is like a new low. I really just want to archive this website to preserve how abysmally slow the website is and its aniations and everything. image literally loading 10% and everyhting. Ship fast and break things is shying from what I am witnessing in here. Sfabt (ship fast and break things) is gonna use your service to talk to the agent which created this project to ask it personally to slow down I can't view your website in 16 gigs of a computer... Weird where the world's progressing in this sense and how it got (YC funded?) Quite frankly I am out of words for how slow the website is. Its really just that bad to be in its own league. Sorry to say.
- adisingh13 8mo agothanks for the input, we always appreciate constructive feedback!
- ncrmro 8mo agoI’ve been looking at getting this going but stalwart mail, I have it setup but haven’t done much. I actually for now was thinking vpn only between me any my agents
- nubg 8mo ago> Here's demo of Clawdbots communicating using AgentMail: https://youtu.be/Y0MfUWS3LKQ https://youtu.be/Y0MfUWS3LKQ Did you record yourself reading out the output of an LLM prompt in this video?
- johnsillings 8mo agosuper cool launch – congrats!
- asyncadventure 8mo ago[dead]
- swaraj 8mo agoLooked into this for my clawdbot, but ended up just using himalaya CLI connected to a new Gmail. Been working great so far - curious about what agentmail is better for
- Haakam21 8mo agoWe have had some users get banned from Gmail for using it Clawdbot. Regardless our API is way more agent friendly and I think your Clawdbot would agree.
- bitfrost 8mo ago[dead]
- CuriouslyC 8mo agoSeems like you're using email as a long lived task queue/journal system. Definitely optimizing for customer recognition/novelty over technical merits. Best of luck!
- Haakam21 8mo agoThat is a compelling use case
- calvinmorrison 8mo agocongrats, I have been following you guys along for a while on LinkedIn. Good Luck
- keeganpoppen 8mo agoi think they figured this out in the unix era
- asyncadventure 8mo ago[dead]
- thetwopct 8mo agoIf the agent is sending emails to people you don’t know (“sourcing quotes”) wouldn’t this be a violation of Amazon SES (and all other email providers) terms? Dont they expect permission from the people you are contacting? How’d you get around that?
- smoyer 8mo agoThis is a pretty clear emergent pattern. An OSS alternative is https://github.com/Dicklesworthstone/mcp_agent_mail https://github.com/Dicklesworthstone/mcp_agent_mail.
- adisingh13 8mo agoWe know the founder of this pretty well actually. It's not really an alternative. They are an MCP that is building an email-like layer for coding agents to talk to each other. We are an actual email inbox provisioned via API for agents to email agents or humans.
- charles_f 8mo ago> Application error: a client-side exception has occurred while loading www.agentmail.to (see the browser console for more information). I would advise to have the landing page static, or at the very least as something that can't crash entirely.
- neumann 8mo agolikewise
- deleted 8mo ago[deleted]
- x_ulla 8mo agoLooks cool
- muskan2226 8mo ago[dead]
- moomoo11 8mo agoThis is pretty cool. You could apply this to so many things, like automating procurement managers, fulfillment agents, or customer support for e-commerce.
- Haakam21 8mo agoYes lots of use cases!
- gpmcadam 8mo agoThe idea here is great and I think it has a lot of legs but I think inherently people will have initial concerns with security. Do you have plans to only allow reading mail from specific senders, and giving fine-grained control on the API side? I would like to give this to an AI agent but only initially where I and my team can forward mail to the agent, and not give it the ability to draft and send emails on its own.
- Haakam21 8mo agoYes we are adding for email/domain allow/blocklists. Same for fine-grained permissions.
- digitcatphd 8mo agoThis is fantastic! I created a GMAIL for my Clawdbot and Google deleted the account after an hour.
- Haakam21 8mo agoHappy we could provide a solution!
- lasgawe 8mo agoI like the design of the web site btw
- Haakam21 8mo agoty :)
- dshah 8mo agoCongrats on the launch. Sign-up was super smooth and the product is compelling. Will be testing it with some of the agent work I'm doing on agent.ai. If you're ever looking for a super low-maintenance indie investor, please reach out. Have lots of YC folks that will vouch for me.
- brap 8mo agoI see a lot of folks are excited about this but I genuinely don’t quite get it, pretty sure I’m missing something. ELI5, why is this useful?
- rnc000 8mo agoI've been working for some time on a similar project, which I open-sourced yesterday, Apache 2.0 licensed if anyone cares to contribute or use https://nornweave.datacovey.com/ https://nornweave.datacovey.com/