Browse the manual

Agent API and AI clients

Use Pepper by hand or from your own AI client, with the same records and permissions.

On this page

New to this? Explore the AI tools and example jobs before connecting a client.

Use Pepper by hand or from the AI client you already use. Both use the same records and the same permissions. You do not need an AI account to use Pepper.

A connection cannot give your client more access than the person it represents. The client does everyday work directly. For a sensitive step, it prepares an exact request. You approve it in Pepper, or a supported rule approves it within your limits.

Start with your job

Build an integration

Owners can manage delegation and credentials in the connection settings and access reference.

Use HTTP, MCP and sign-in for transport details. Read the tool page for the app you use:

The tool reference lists every tool with its HTTP route, grant and permission. Steps that stay with people lists the steps without a tool. The tool list in your installation (GET /api/v1/tools or MCP tools/list) gives each tool's input and output schema for your connection.

Visitors' own AI clients

The visitor door is a separate public door at /visitor/mcp. A visitor's own AI client uses it to read published widgets and website pages and to act as that visitor, under the form's rules. It needs no connection and shares nothing with the staff door on this page. The owner can turn it off in Settings > Widgets.

Stay in control

AI access starts off. The owner enables connections. Each person can then connect an app, choose its access and set an expiry. Read Connect your AI.

Each sensitive step needs an exact approval, from your decision or a supported rule. The approval expires. Only an approved online refund moves money. Passwords, two-factor authentication, agent connections, updates, and downloading or restoring backups stay with people. See what stays with people.

Need help with the product?

Contact support