Bengar Gateway AVAILABLE
The service that decides, executes and records.
What it is
- A Fastify service with two surfaces: a machine API authenticated by API key, and a session-authenticated control plane the Console uses.
Why it exists
- Authorization is one decision from several inputs. Split across callers, each caller gets it slightly wrong.
How it works
- Verify the permit. Evaluate the policy. Consult risk. Take the meet.
- On ALLOW, execute if asked, with idempotency.
- Write the audit event, batch it, anchor it.
Who uses it
- Your backend
Security boundary
- Holds tenant data under row-level security, and never a private signing key.
- It is not chain consensus. A decision does not wait on a block.
- It asks Custody to sign and cannot read what Custody holds.
Example flow
One call
- POST /v1/authorize with an agent, a permit, an action and a resource.
- Read `decision`.
- Only ALLOW means go.
Current status
| Capability | Status | Where |
|---|---|---|
| Authorize an agent action | AVAILABLE | The API: POST /v1/authorize |
| Create, list and revoke API keys | AVAILABLE | /projects/:id/api-keys |
Related API
POST /v1/authorize