TAP — Tool Authorization Protocol

How TAP works

1 — Agent sends request

Your agent calls TAP's proxy URL with a service name instead of a real API key.

2 — TAP checks policy

By default, reads auto-approve and writes (POST, DELETE…) wait for your OK. You can customize this per credential.

3 — You approve

You see exactly what your agent wants to do in your approval channel and approve or deny with one tap.

4 — TAP injects key

After approval, TAP substitutes the real credential and forwards the request.

Dashboard sections

Everything you need is in the sidebar. Here's what each section is for.

Credentials

The API keys and tokens your agents need. Store them here, encrypted. Agents reference them by name so the actual values stay protected.

Agents

Each agent gets its own API key. Your personal assistant, your work agent, a teammate's bot, each gets scoped access to exactly the credentials it needs.

Roles

Optional shortcut: bundle credentials into a named group (e.g. "social-media-tools") and assign the role to many agents at once rather than granting credentials one by one.

Policies

Fine-tune approval rules per credential: which HTTP methods auto-approve, which ones need you to sign off, and URL patterns that always pass through. Approvers can confirm with a passkey for cryptographic proof of identity.

Approvals

Connect a Telegram or Matrix group. When an agent makes a write request, TAP messages the group so you can approve or deny directly from your phone.

Connect your agent

Create an agent below and copy the API key
Add this block to your agent's system prompt:

TAP proxy: 
TAP key: <your agent key>

Discover credentials: GET <proxy>/agent/services  (X-TAP-Key header)
Forward a request:    POST <proxy>/forward  — always POST, even for upstream GETs
  X-TAP-Key / X-TAP-Target / X-TAP-Method / X-TAP-Credential — only these 4 required headers
  Body goes in HTTP body. Non-TAP headers forwarded verbatim. Writes need human approval.
        

For Claude Code: /setup-tap configures this automatically.

When to use roles: If you have multiple agents that need the same set of credentials (e.g. five different assistants all needing access to Slack and Google), create a role with those credentials and assign the role to each agent — instead of granting credentials individually every time. Roles are optional. Small setups with one or two agents can skip them and assign credentials directly on the Agents page.

Policies control which agent requests need human approval. With no policy, everything requires approval (fail closed).
The proxy checks in order: URL patterns → HTTP method → default deny.

Credential

Load template

Request Rules

Auto-approve (skip approval)

Requests with these HTTP methods go through without human approval.

Auto-approve URL patterns

If the target URL contains any of these substrings, auto-approve regardless of method. One per line.

Require approval

Requests with these HTTP methods need human approval (unless matched by a URL pattern above).

Methods not in either list default to requiring approval.

Approval Settings

Require security key for approval

When enabled, approvers must use Face ID, fingerprint, or a security key. Telegram approve buttons are replaced with a secure passkey link.

Approval channel

Route approval requests for this credential to a specific channel, overriding the default. Set up defaults on the Approvals page.

Allowed approvers

Team members who can approve. Leave empty to allow any signed-in team member.

Minimum approvals required

Number of approvers who must approve before the request proceeds. Default is 1 (any single approver).

When an agent makes a request that requires approval, a notification is sent to your Telegram group. You approve or deny directly from the message. We recommend adding both the approval bot and your agent to the same group so you can see what your agent is doing and approve requests in one place.

Telegram Setup

Create a Telegram group for approvals (or use an existing one)
Add @vaulty_tap_bot to the group
Get the group's Chat ID: add @raw_data_bot to the group, it will post the Chat ID, then remove it
Paste the Chat ID below

Telegram Chat ID

A negative number for groups. The approval bot must be a member of this chat.

Matrix Setup (alternative to Telegram)

Loading bot info… Invite to your room. The bot can join rooms on any federated homeserver. Matrix bot is not configured on this server. Set MATRIX_HOMESERVER_URL and MATRIX_ACCESS_TOKEN to enable it.

Invite the bot above to the room you want approval messages in
Find the internal Room ID (starts with !) for that room:
How to find it: Element Web / Desktop: open the room → Room Settings → Advanced → copy Internal room ID
Element iOS / Android: tap the room name at the top → Settings → scroll to Room ID
Any client: room IDs look like !aBcDeFgH:your.server — the ! prefix distinguishes them from #alias:your.server room aliases
Paste it below

Room ID

Internal Matrix room ID, starting with !. Not the human-readable alias.

Email

Display Name

Matrix User ID

Telegram User ID

Security keys (passkeys) protect your account with hardware-backed 2FA. You must verify your identity with a security key every time you log in. You must keep at least one security key registered.

Free during early access

Overview

Credentials

Agents

Roles

Policies

Approvals

My Profile

Security

Free during early access

Overview

Credentials

Agents

Roles

Policies

Approvals

My Profile

Security

Add Credential

Create Agent

Edit Agent:

Create Role