# TAP

> Public, agent-readable snapshot of TAP — credential isolation for AI agents, built by human.tech. TAP is a credential proxy: agents reference credentials by name and never see the secret values; the proxy injects real credentials after policy enforcement, with optional human approval on the actions that matter.

Last updated: 2026-08-01T00:00:00Z

TAP exists because giving an AI agent raw API keys means the agent can leak,
misuse, or exfiltrate them. With TAP, the agent holds only a TAP agent key.
Every outbound API call goes through the proxy, which substitutes the real
credential, enforces per-credential policy (allowed hosts, auto-approve vs
require-approval URL patterns), and pauses risky writes until a human approves
them from a dashboard. Responses are sanitized so credential values never
flow back to the agent.

Definitions:
- "Credential": a secret (API key, token, multi-field key pair) stored in TAP
  and referenced by name.
- "Approval": a human decision, made in the TAP dashboard, that releases a
  specific pending request.
- "Connector": a protocol-translating sidecar for services that are not plain
  HTTP APIs (e.g. a personal messaging account).

## Product surfaces

- [Marketing site](https://tap.human.tech/): what TAP is, hosted sign-up. Hosted credentials are stored via hardware enclaves; keys never touch the user's machine.
- [Pricing](https://tap.human.tech/pricing): Free ($0, 1 team member seat / 2 agent seats / 5 credentials / 1,000 requests per month), Pro ($49/mo, 5 team member seats / 10 agent seats / 20 credentials / 50,000 requests per month), Team ($149/mo, 15 team member seats / 25 agent seats / unlimited credentials / unlimited requests per month), Enterprise (custom). Every plan runs in the same hardware enclave with the same protections. Self-hosting is free and unlimited.
- [Developer docs](https://docs.tap.human.tech/): quickstart, proxy API reference, policies, MCP integration, self-hosting.
- [Open-source repository](https://github.com/holonym-foundation/tap-oss): Apache-2.0 source for the proxy, policy engine, CLI, and MCP server. Mirror of the internal monorepo's public paths.

## Key facts

- Agents authenticate to the proxy with `X-TAP-Key`; the target API and method
  are declared per request; the credential is selected by name.
- Single-secret APIs use automatic header injection; multi-secret APIs use
  explicit `<CREDENTIAL:name.field>` placeholders.
- Writes (POST/PUT/PATCH/DELETE) can be gated on human approval per policy;
  approvals are passkey-gated in the dashboard.
- Self-hosting is supported (Apache-2.0); the hosted service runs credential
  storage inside hardware enclaves.
- TAP is a product of [human.tech](https://human.tech/), the identity and
  control layer for people, institutions, and AI (also builds Human Passport,
  WaaP wallet infrastructure, and Shield).

## Where to start

- [Quickstart](https://docs.tap.human.tech/quickstart): first proxied request in minutes.
- [How it works](https://docs.tap.human.tech/how-it-works): request flow, placeholder substitution, response sanitization.
- [Proxy API](https://docs.tap.human.tech/proxy-api): full request/response reference.