Introducing JAW for Agents 🎉
Tell your AI what you want onchain. It prepares everything for your one-tap approval, or runs it on its own inside limits it can't break. It can even pay for the services it uses.
Works in Claude, ChatGPT, Gemini, Grok and more.
Join the waitlist 👇🧵
jaw.id
7/ For seasoned users, the same layer automates onchain workflows and runs trading strategies on its own, within permissions you sign once.
Join the waitlist and we’ll let you know when it’s your turn 🫶
jaw.id
What building wallet infra in-house costs:
👉 bundler and paymaster ops
👉 a passkey server you maintain
👉 a permission engine, from scratch
👉 the 7702 upgrade path nobody scoped
👉 the lost seed phrase queue, forever
Just use one SDK instead 👇
docs.jaw.id
👉 “alice.yourapp.eth” reads like an account.
👉 “0xa39f...” reads like an error message.
It’s the same account either way, but a support agent can only read one of them back to someone over the phone.
JAW.id‘s passkey native accounts have @ensdomains names built in.
Offer stablecoin balances and payments inside the app you already have.
One integration: sign in with Face ID, and you never hold your customers' keys. They hold them through a passkey that cannot leave their devices.
jaw.id/?utm_source=twitter&u…
One-off payments are the easy part. Recurring and usage-based charges are where onchain gets pretty awkward.
We fixed this with session keys: the user grants a scoped allowance with an expiry once, and your app charges against it without asking again.
We made zero sacrifices on self-custody, and there would be no centralized servers in your users’ way.
docs.jaw.id
With JAW, your money goes to an @ensdomains name, not a 42-character address.
That removes the step people most often get wrong on a cross-border transfer, and the recipient signs up with Face ID instead of having to install a wallet before they can be paid.
jaw.id/?utm_source=twitter&u… 🤝
