BetterSign™
Solution: For AI agentsGet the app
Talk to usGet the app

Solution · For AI agents

Give agents API access, not your keys.

Scoped, revocable API access for agents, bound to an identity.

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.

  • For you: the agent never holds your API key or password
  • For your organization: every agent’s access belongs to a person
  • Revoke a grant, and the agent is cut off on its next call
  • Deny by default; scopes, expiry up to 7 days, and limits
  • Grants bound to the owner’s VLAD; per-owner audit log
  • Tokens stored as hashes; credentials encrypted at rest

Agents get a token, not your keys.

Preview

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

Handing over a key vs. granting access.

Sharing a key or password

  • ✕The agent can do anything you can
  • ✕The secret ends up in its config, logs and memory
  • ✕Stopping it means rotating the key everywhere
  • ✕Nobody can see what it did on your behalf

With BetterSign

  • ✓It can do only what you ticked, until the time you set
  • ✓It holds a short-lived token, never your credential
  • ✓Revoke one grant, and it’s cut off on its next call
  • ✓Every call is checked and logged against your identity

Who it’s for

For you, and for your organization.

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.

For organizations Design partners

Agents with an audit trail.

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

One identity behind every grant.

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.

◉

The BetterSign app

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.

✓

BetterSign Approve In development

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.

⇋

BetterSign Credential Vault

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.

⛓

BetterSign IdP

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.

WhatWhere it isStatus
Sign in with BetterSign (phone passkey)AppLive
One-tap sign-in from a paired browserCredential Vault extensionLive
Grants with permissions, room limits, expiry, revoke, and a call logdelegate.bettersign.ingLive
Rocket.Chat’s API as a connected servicedelegate.bettersign.ingLive
Any OAuth 2.0 API, added from its API descriptiondelegate.bettersign.ingNext
Agents request access; you approve on your phoneAppNext
Agents ask before risky steps; you approve on your desktop or phoneBetterSign ApproveIn development
A secret from your vault, for one approved commandBetterSign ApproveIn development
Tokens bound to a key the agent holdsdelegate.bettersign.ingLater
API Delegate for an organization’s staff and agentsBetterSign IdPDesign partners

Questions

Frequently asked.

Can I use it today?

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.

Does it work with websites, or only APIs?

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.

Whose account does the agent act as?

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 or Approve: which do I need?

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.

What if the agent’s token leaks?

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.

Give your agent a token, not your API keys.

Try the preview, or tell us which API you’d like to delegate next.