Action Permission
Can this exact action proceed under current conditions?
Every action gets a clear answer before it reaches your systems: allowed, refused or waiting, with its reason.
Allowed, refused or waiting. Each answer with its reason, each one on the record.
Sapey gives each action sent to it a clear answer, using your policies. You get the answer, the reason, and a record you can check.
A list of answered actions. New actions arrive at the top, each with its answer and its reason.
Answered actionsEach with its reason
- Publish night staffing planRefusedBelow the skilled coverage the state requires.
- Approve a shift swapAllowedIt meets every policy.
- Publish weekend staffing planWaitingWaiting for one fact: the skilled nurse on call.
- Add an overtime shiftAllowedWithin the overtime limits.
- Reassign a nurse to another unitRefusedNot approved by someone who can approve schedules.
- Publish holiday staffing planWaitingWaiting for one fact: patients expected that day.
Example answers. Every one is kept.
One product
One product. Three ways to start.
Sapey is one product. Start with the part you need now, and add the rest when you are ready.
Evidence & Verification
What happened, and what does the evidence support?
Check what actually changed and what the record can support, without taking our word for it. It can be used on its own where your systems keep the evidence it needs.
Controlled Operations
FlagshipControl what proceeds. Establish what happened.
Permission, the action itself and the check of its result, connected. Sapey answers, carries out the allowed action in your system, and confirms what changed.
Three answers
Same request. Three answers. One value changed.
An AI agent asks to publish a care facility's staffing plan for a Monday morning shift. We sent the same request three times and changed one value each time.
Pick a value to see how the answer changes.
Request
Publish Monday morning staffing plan
From Scheduling agent
Care facilitySame each time
ShiftMonday morning
Staff proposedEnough for the shiftBelow the state ruleA needed fact is missing
Staff proposed: Enough for the shift
AllowedAllowed for this exact plan.
The plan reached the schedule.
Your scheduling system
Monday morning shiftPlan published
Monday evening shiftPublished
Staff proposed: Below the state rule
RefusedRefused under the state's staffing rules.
Nothing reached the schedule. The refusal and its reason are on the record.
Your scheduling system
Monday morning shiftNo change
Monday evening shiftPublished
Staff proposed: A needed fact is missing
WaitingNot enough facts to decide.
Sapey waits instead of guessing, and says what is missing.
Your scheduling system
Monday morning shiftNo change yet
Monday evening shiftPublished
From a real run, October 2026. Details removed.
The record
Every answer is recorded, including the no's.
Each record shows what was asked, what Sapey answered, and why. Where your systems support it, Sapey also checks what actually changed, so the record shows both what was allowed and what happened. When someone needs proof, Sapey produces an Epi-Cert: independently verifiable evidence for that answer, which anyone you choose can check without taking our word for it.
A record of answers, including refusals and waits. One refused answer has its Epi-Cert open.
Every answer, recordedExample
AllowedApprove a shift swap
RefusedPublish night staffing plan
WaitingPublish weekend staffing plan
Epi-CertFor one answer
- What was asked
- Publish night staffing plan
- What Sapey answered
- Refused
- Why
- Below the skilled coverage the state requires.
- What happened
- Nothing reached the schedule. Checked in your scheduling system.
Anyone you choose can check it, without taking our word for it.
An Epi-Cert is not a certification in the regulatory sense, and it grants no authority.
Where Sapey sits
Between whoever acts and the systems that change.
Sapey connects by role, not by vendor: your agents, your policies, your systems, and whoever needs to check the answer.
Whoever acts asks Sapey. Sapey answers using your policies. Only allowed actions reach your systems. Whoever you choose can check the answer.
Allowed goes throughRefused stopsWaiting holds
What we don't claim
What Sapey doesn't do.
Sapey doesn't make your business decisions.
It doesn't decide what your policies say.
An Epi-Cert is not a compliance certificate.
It shows what was asked, what was answered, and why.
How to start
Start with one operation.
- Request a conversation.
- Define your operation: the action, the policies that apply, the systems involved and the evidence you need.
- Get a scoped proposal.
Pricing is based on the operations, systems, environments, usage and support Sapey is asked to cover. Implementation is quoted separately.
See what Sapey would answer for your actions.
Or write to contact@sapey.aiCopiedEmail address copied
Request a conversation (opens a new tab)