For you Preview
Let an agent use your APIs.
Sign in to API Delegate with the BetterSign app, connect the API of a service you use, and give your agent a token for exactly the calls it may make. Watch its calls, and revoke it with one click.
Solution · For AI agents
AI agents, scripts and build jobs need to call the APIs of services you use. The usual answer is to hand over an API key and hope. With BetterSign API Delegate, a person grants an agent exactly which API calls it may make, for as long as it needs, and sees every call it makes.
Agents call through a credential broker with a short-lived bsd_ token bound to a grant on the owner’s VLAD. Each call is checked live against the grant and made with the owner’s credential, which never leaves the broker.
Agents get a token, not your keys.
BetterSign API Delegate is live at delegate.bettersign.ing, with the Rocket.Chat API as the first one you can connect. The version for organizations is being shaped with design partners.
What changes
Who it’s for
For you Preview
Sign in to API Delegate with the BetterSign app, connect the API of a service you use, and give your agent a token for exactly the calls it may make. Watch its calls, and revoke it with one click.
For organizations Design partners
Each grant belongs to a person in your directory, and each call is logged against them, so you can see which agents act for whom and cut them off. We’re shaping it with design partners.
How each product plays a part
API Delegate and Approve run on the same identity as the BetterSign app, Credential Vault, and BetterSign IdP, and follow the rule they share: a device or agent can ask, but the decision and the secret stay with you.
Your phone is how you sign in to API Delegate, so every grant belongs to your identity. Next: an agent asks for the access it needs, and you review and approve the request on your phone.
Sign-in uses the phone’s passkey for id.bettersign.ing, checked against your provenance log. Planned: agent-initiated requests, approved with your passkey or a push to the app, with the token sent to the agent directly.
API Delegate covers what an agent does through a service’s API. Approve covers what it does on your computer: before a risky command, file change or use of a secret, it asks, and you decide on your desktop or your phone.
A hook in the agent’s tool (Claude Code first) asks bs-gate, which asks your identity over a local socket or a sealed relay. Decisions and receipts are signed by your identity key.
Your paired browser can already only ask your phone; it never holds the vault. Delegation gives agents the same deal. With the extension paired, signing in to API Delegate is one tap on your phone.
bs-id offers “remember this browser” for API Delegate; later sign-ins ask the extension, the phone approves, and the broker checks the signed statement (origin, client, challenge, time) through the verifier.
Each grant belongs to a person’s identity and each call is logged against it, so a company can see which agents act for whom, and cut them off. We’re shaping this with design partners.
Grants are bound to the owner’s VLAD with a per-owner audit log. Running the broker beside your org IdP is part of the design-partner programme, not a shipped edition.
| What | Where it is | Status |
|---|---|---|
| Sign in with BetterSign (phone passkey) | App | Live |
| One-tap sign-in from a paired browser | Credential Vault extension | Live |
| Grants with permissions, room limits, expiry, revoke, and a call log | delegate.bettersign.ing | Live |
| Rocket.Chat’s API as a connected service | delegate.bettersign.ing | Live |
| Any OAuth 2.0 API, added from its API description | delegate.bettersign.ing | Next |
| Agents request access; you approve on your phone | App | Next |
| Agents ask before risky steps; you approve on your desktop or phone | BetterSign Approve | In development |
| A secret from your vault, for one approved command | BetterSign Approve | In development |
| Tokens bound to a key the agent holds | delegate.bettersign.ing | Later |
| API Delegate for an organization’s staff and agents | BetterSign IdP | Design partners |
Questions
It’s in preview at delegate.bettersign.ing. Anyone with a BetterSign identity can sign in. Rocket.Chat is the first API you can connect; tell us which you’d like next.
Only APIs. The agent makes calls to a service’s API through API Delegate, the same calls it would make with an API key. It doesn’t fill in login forms or drive a browser; for your own logins in your own browser, use BetterSign Credential Vault.
Yours. You’re lending your own access, so calls show up on the service as you. That’s why API Delegate checks every call against what you ticked, and why some calls, like creating keys or changing users and settings, can never be granted.
API Delegate is for an agent using a service’s API: it gets a token, never your credential. Approve is for an agent working on your computer: it asks before risky steps, and you decide. Many people will want both.
It only works through API Delegate, only for the permissions and service in its grant, and only until it expires. Revoke it and it stops working on the next call. The service’s real credential was never in the agent’s hands.
Try the preview, or tell us which API you’d like to delegate next.