Good question. The server sees the key at generation. It's not stored. The wallet is a normal Ethereum wallet, and this design is what lets agents provision one from a Python sandbox, an MCP tool, or any pure-HTTP environment where running Node or installing crypto libs isn't an option. Compared to embedded-wallet services like Privy or Magic — which see the key, store it persistently, and bind it to your OAuth identity — Aethergent never ties the wallet to who you are. It generates it, sends it to you, then immediately discards it. TEE generation with attestation is on the roadmap.
But that isn’t verifiable right? It is only what you claim. It requires that people believe you have no intention to ever take the money that you could take.
Today it isn't verifiable. That's exactly what TEE attestation fixes. Until that's deployed, yes, you're trusting me.
For testing, dev work, and ephemeral agent flows that's a reasonable tradeoff for the convenience. For valuable wallets it's not, and you should generate locally, until TEE attestation ships, at which point these keys become safe to use for valuable wallets too.
Hi, I'm Eoin. I kept hitting the same problem when building and testing tooling for AI agents: they need a wallet to pay for things (x402, MPP, etc.), but every existing option assumes you can run Node or install crypto libraries. That doesn't work from a Python sandbox, a curl-only environment, or inside an MCP tool. It's a 10-minute detour that breaks the agent's flow.
So I built Aethergent. POST to the API, get back an Ethereum-compatible wallet — address, private key, funding instructions. No account, no API keys, no signup. One HTTP call.
It's deliberately simple. No private keys stored, no auth, just math over HTTPS.
Works from anywhere that can make an HTTP call — including environments where shelling to a Node CLI isn't an option. There's also an MCP endpoint at /mcp for agents that prefer to discover tools that way.
Namecheap still requires you to setup everything first. Ideally agents have a wallet with a certain amount of money and can search on their own, then ask the human to approve the purchase. Or you just limit the amount of money the agent has and tell the agent specifically what domain you want and it buys it. Essentially pre-approving the purchase.
The real use case is you don't want the agent to stop. This is a blocker for an agent that needs you to setup credentials to search, register or buy a domain.
I can relate, I picked up Unity to build a game. Not to learn programming. This has had consequences. Years later one of my oldest projects is a maze of spaghetti code that I'm afraid to enter, I don't want to face the minotaur inside or worse realize it's a dead end.
Pure genius! I had my agent hit the endpoint and I realized it returned a jumble of text: "if 七 wor~kers co.mplet/e{ | a job in 十七} days but 四 ] quit a^ft|e?r ^ day_ 三 ~ how many to{tal da[y;s> to fin>i?sh" but it was in japanese! Unfortunately my agent proceeded to solve the reverse CAPTCHA and got back the API key. So, I asked it to keep hitting the endpoint again until it returned another CAPTCHA that was in japanese kanji and it did (without solving it this time) and I got "a s:tore h?as ^ 二十 pe@rcent off< items- over 五十 : dollar;s and 八 ~ percent } of\f> ; i]te[ms u~nd~er: # 五十 do/ll@ars wh-ats } the c.omb>ined pri|c;e of a 一 百 二十 一 dollar item a]nd> a* 九 dollar} i!tem" And this time I was able to translate that into "a store has 20 percent off items over 50 dollars and 8 percent off items under 50 dollars what's the combined price of a 121 dollar item and a 9 dollar item?" I solved it and got 1210.8 + 90.92 = 105.08. I will admit I messed up a little bit on translating the kanji and I got a little assistance from my agent pointing out that I was wrong, but overall this was good fun, well done!
Absent any distinctive Japanese scripts or other Japanese writing in context, it probably makes more sense to call those Chinese characters, since those characters for numbers were taken directly from Chinese and still retain the same/original meanings in both languages
Originally I thought they were just em dashes and part of the jumble so I ignored them. That's why I got it wrong in the first place. You're assessment is probably right though.
reply