Documentation

The approval layer for AI agents.

Connect a local agent, describe which calls need your approval, and decide your first request.

The three core concepts: agents, approval pipelines and escalation paths.

What agents and instances are, and how they fit together.

How requests get a decision, and what happens next for the agent.

How approval pipelines decide what happens next for a request.

Who reviews a request, when they’re contacted, and what happens if nobody decides.

How resources keep their history, and how revisions let you make changes and roll them back.

Review and decide approval requests that need a human.

Explore the record of requests, decisions, and organization activity.

Connect agents and manage their instances and credentials.

Connect downstream MCP servers and choose which tool calls need approval.

Define how requests are evaluated and when they reach human review.

Choose who reviews requests and how they escalate over time.

Manage teams, their members and the permissions they inherit.

Manage direct and inherited access, permission scopes and decisions outside routing.

Invite people, manage member access and control who belongs to your organization.

Choose personal or organization API keys for scripts and integrations.

Let an AI agent set up approval pipelines, escalation paths, teams and webhook endpoints for you.

Choose how withHuman reaches you for standard and urgent requests.

Manage your organization's connections to external services.

Manage organization-wide rules for reviews, request visibility and API keys.

Make tool requests easier to read with clear titles and formatted arguments.

Manage your password and understand how you sign in to withHuman.

Manage your hosted plan, purchased seats, usage limits and payments.

Sign in, receive notifications and review requests on iPhone or Android.

Connect your identity provider for single sign-on and manage how people join.

How the API is organized, how to authenticate, what an error looks like, and the rules every endpoint follows.

What an adapter calls on behalf of a running agent. Create an instance and get its credential, ask for approval of a tool call, and wait for the answer.

The review queue is where approval requests wait for a person to approve or deny them. These endpoints list the queue, retrieve one request, claim it while you look at it, and record your decision.

Connect an agent from a developer machine. The agent asks for a code, a person approves it in the browser, and the agent exchanges the code for a credential. A withHuman extension, not part of the protocol.

Who the session belongs to. Read the current member, their organization and permissions.

Agents are the AI systems that ask for approval. Each agent has instances, and each instance holds a credential it uses to call the API.

The ordered list of blocks every approval request runs through. A block can decide the request itself, ask a service of yours, hand it to a person, or, as a branch, run blocks of its own for the requests that match its condition. The hosted edition adds a block that asks a model.

An escalation path decides who reviews a request once the pipeline hands it to a person, and what happens when nobody answers in time.

A webhook endpoint is a URL on a service of yours that a pipeline's webhook block can ask for an outcome.

The people in the organization, their status, and their permissions.

Groups of members. A team can be an escalation target, and its members inherit the team's permissions.

Invite people to the organization by email.

Personal API keys let a script act as you outside the browser: a whk_ bearer that carries a subset of your own permissions, changes with your permissions, and dies with your membership. Mint one, list yours, revoke it, and verify what a key can do.

The organization's append-only log of what happened and who did it, and the request timeline it tells.

Every permission a role can carry, grouped by area, with who can hold it and the endpoints that require it.

Every named object the published API uses, with its fields. Type names throughout the reference link here.

Read or download the OpenAPI contract for the published withHuman API.