Skip to main content
The whole integration is one call before a consequential action. There is no runtime to adopt, no framework to standardise on, and no proxy in front of your traffic.
1

Install

2

Point it at your deployment

See Authentication for where the key comes from and what it is scoped to.
3

Ask before you act

By default authorize raises on a refusal, so the unsafe path is the one you have to write on purpose rather than the one you get by forgetting to check a return value.

What comes back

Six outcomes, not two. allow, deny, exhausted, gated, review_sync and review_async are different findings that send an operator to different places, which is why they are not collapsed into a boolean. See Outcomes.

Nothing is enforced yet

A grant created today starts in observe. It records what the check would have done and changes nothing. That is deliberate: run it against production for a fortnight and find out what your agents are actually doing before you decide whether to stop any of it.
The first week of observe data reliably contains at least one behaviour nobody knew about. That finding is usually worth the integration on its own.
When you are ready, move one grant up the ladder. See Move up the ladder.

Handling refusals properly

See Errors for the full hierarchy and what each one means.