# Approvals for AI agents and workflows

> A second person's yes before an AI agent, workflow or script does something it can't undo. Approvers decide on their phone, the agent hears back at once, and every decision is on record. Free for 3 approvers, from $19 a month per workspace.

Source: https://hibira.io/approvals

## Built for the person who says yes

### A workspace for your approvers

Invite managers, compliance staff and database owners by email. They sign in with an emailed code, Google or GitHub and see only the requests meant for them. Nobody needs a developer account.

### Decide from your phone

New requests arrive as a notification. The inbox shows the title, the details and the options, and works as an app on the home screen. Busy people answer in seconds, wherever they are.

### The right people, by name or by group

Send a request to named people or to a group such as `dba` or `finance`. Only they can answer it, and the answer records who it was.

### Exactly what was approved, once

For database changes, the approval is bound to a fingerprint of the exact statement. A changed statement needs a new approval, and an approved one runs a single time.

### The agent hears back at once

The decision reaches the waiting agent or workflow over a live connection the moment it is made, with the chosen option and any comment. Requests nobody answers in time expire, and the agent is told so.

### A record for every decision

Who asked, who answered, which option, the comment and when, kept for your plan's history. Team and Business admins can export it as CSV for audits.

## How it works

1. **Open a workspace** and invite your approvers. It comes with its own app and keys.
2. **Ask from your tools**: a workflow node, an agent tool, one HTTP call or a proxy in front of your database tools.
3. **Approvers decide** on their phone or in the inbox, and the request continues or stops.

![The demo console: a DELETE waits for the supervisor with a QR code, the estimated rows and the statement's fingerprint.](https://hibira.io/portal/articles/sql-approvals-console-en-light.webp)

Prefer to answer inside your own admin panel? The same requests can show in an inbox you embed with [@hibira-io/approvals](https://hibira.io/guides/approvals), with approve, reject and edit.

![An embedded approvals inbox: requests from AI agents wait with their arguments, each with Approve, Reject and Edit.](https://hibira.io/portal/articles/approvals-inbox-en-light.webp)

## Plans

| Plan | Price | Approvers | Requests a month | Approver groups | History |
| --- | --- | --- | --- | --- | --- |
| Free | $0 | 3 | 100 | 1 | 30 days |
| Starter | $19 / month | 10 | 2,000 | 5 | 1 year |
| Team | $49 / month | 30 | 10,000 | 20 | 2 years |
| Business | $149 / month | 100 | 50,000 | 100 | 3 years |

Prices are per workspace. Viewers who only read the history are free. Audit export and embedding the inbox in your own admin are on Team and Business. Need more approvers, longer history or a contract? [Contact sales](https://hibira.io/contact-sales).

## Ask from the tools you already use

- **Workflow tools**: an approval step in [n8n](https://hibira.io/guides/n8n), [Make](https://hibira.io/guides/make), [Activepieces](https://hibira.io/guides/activepieces), [Node-RED](https://hibira.io/guides/node-red) and Dify.
- **AI agents**: the `request_approval` tool of the [Hibira MCP server](https://hibira.io/mcp-server), and [@hibira-io/approvals](https://hibira.io/guides/approvals) for the AI SDK, Mastra and LangGraph.
- **Databases**: [mcp-approval-gate](https://hibira.io/use-cases/database-write-approvals) in front of a database MCP server lets reads through and holds every write for approval.
- **Admin panels**: the [Filament approvals plugin](https://hibira.io/guides/filament-approvals) for Laravel.
- **Anything else**: one signed HTTP call to create a request and one to read the answer.

## Frequently asked questions

### Who counts as an approver?

Every member who can answer requests: admins and approvers, including people you have invited who haven't joined yet. Viewers, who can read the history but not answer, are free.

### What counts as a request?

Each approval request created in the workspace in a calendar month, whatever its answer. Reading a request or waiting for its answer is not counted.

### What happens when the month's requests run out?

New requests are refused with a clear error, so your workflow can stop safely or try another path, and admins get an email at 80% and 100% of the quota. Requests already waiting can still be answered.

### Do approvers need a Hibira developer account?

No. They join your workspace by email and use the inbox on the web or as an app on their phone. Only whoever connects the workflow or agent needs the workspace's keys.

### Can an agent approve its own request?

Not when the request names its approvers: then only those people can answer, after signing in, and the agent never gets a working answer link. Each answer records who gave it.

### I already use Hibira for realtime features. What changes?

Nothing you rely on. Approval links on your existing apps keep working as before. A workspace adds the approvers, groups, inbox and records on top, with its own plan.