For agent builders
IDhen gives your agent sanctioned, reliable access to your users’ accounts, with no passwords or 2FA codes to handle and no scrapers breaking on login. One integration reaches every app on IDhen. Users approve in a familiar flow inside the app, and you get a scoped, time-limited token plus revocation events.
The problem
Your agent is only as useful as the accounts it can reach. Today that usually means a password, a relayed code or a browser you hope keeps working.
Storing passwords and passing along 2FA codes makes you a target, and one leak hurts every user who trusted you.
A redesigned login page, a new CAPTCHA or a bot rule stops your agent mid-task, and your users feel it.
Each app means a separate integration to build and keep alive, if the app will work with you at all.
Plenty of agent teams start by wiring up each app themselves, or plan to. One app is doable. Every app adds the same list again:
IDhen gives you one way to connect to every app that supports it, so your team can stay on the agent.
Already working on it? Talk to us about running IDhen beside them.
How it works
Tell IDhen who you are and what your agent does. Verified agents show who makes them in the app’s picker, so users know it’s you.
Inside an app they already use, your user taps “Invite your agent,” picks you and approves what you can do and for how long. You can suggest a length; the app sets the cap and the user decides.
You get a scoped token that lasts as long as the user chose, from this session to ongoing, within the app’s limits. If the user removes access, you get a revocation event and the token stops working.
idhen.on("grant", async (g) => {
// g.app, g.scopes, g.duration, g.expiresAt
// expiresAt is null when access is ongoing
await saveToken(g.user, g.token);
});
idhen.on("revoke", async (r) => {
await dropToken(r.user, r.app);
});Not a live SDK. The API is being shaped with early partners.
Why it works
Sign in with Google and Apple taught people to log in through an account they already trust. PayPal did the same for payments, so a store never sees your card number. More recently, Plaid made linking an app to a bank account routine. Each time, one familiar consent step replaced a pile of one-off setups. IDhen brings the same model to agents and the apps they work in.
One integration reaches every app that supports IDhen, the way Plaid gave fintech teams one integration instead of one per bank. No scrapers or per-app logins to keep alive.
They connect you from inside an app they already trust, through a consent step they have seen before. No passwords to hand over.
The user’s side
Your user connects you from inside an app they already use.
Users find you inside apps they already trust. The same button works in every app on IDhen, so you build one flow instead of an integration per app.
Verified agents show who makes them, so users know it’s really you.
Your user proves it’s them, right there in the app. You never hold their password or relay a 2FA code.
This screen is yours. The user confirms which account on your side gets access, so the grant lands in the right place.
Users see a consent screen from an app they know, which is an easier yes. You can suggest how long access lasts; the app sets the cap and the user decides.
You hold scoped, revocable access to real account actions, like checking a claim or scheduling a refill, for as long as the user allowed. No password to store, and no scraper to break when the login page changes.
FAQ
You register your agent with IDhen and we check who makes it. In the app’s picker, users see your agent as verified, along with the company behind it.
Any app that adds IDhen. We’re starting with health plans, banks and utilities, where people already want help from an agent. Your one integration covers each new app as it joins.
Your token stops working right away and you get a revocation event, so you can stop any work in progress and let the user know.
No. The user confirms it’s them with the app and IDhen. You only ever get a scoped token, never a password or a 2FA code.
Early access
We’re talking with a small group of teams building agents and assistants. Tell us what you’re building and which apps your users need.
Thanks for your interest in IDhen. We’ll be in touch about early access.