For each operation you protect, keep the execution credential in the service performing the action. That service must verify valid human authorization before it acts, with no alternate credential or route available to the requester.
Example Β· one action, end to end
Follow one action from your code to a signature and back
A service asks to delete a production database. A person sees exactly that, and signs it. Your code verifies the signature before anything is deleted.
1Step 1: Your code asks
The exact action and its parameters, sent before anything runs.
import { IntygaClient }
from "@intyga/sdk"
const intyga = new IntygaClient({
gatewayUrl, clientId, clientSecret,
})
const action = {
target: "example-prod-db-eu",
actionType: "drop_database",
params: {
database: "example_orders",
region: "eu-west-1",
},
}
// Waits until a person signs, denies,
// or the request expires.
const approval =
await intyga.requireApproval(
"Delete database example_orders",
action,
)
2Step 2: The approver sees
The same fields, in the order they execute, and a passkey or security key to sign them.
Confirm on your device β Touch ID, Windows Hello or your security key
Illustration with example values: the approval screen for this action β action, target, requester, deadline and parameters, then the approve and deny buttons and the passkey prompt.
3Step 3: Your code gets back
A receipt over those exact bytes. Your code checks it, then acts.
if (approval.status !== "APPROVED")
throw new Error("not approved")
const wa = anchor.webauthn!
// Offline, against YOUR approvers β
// never the key inside the receipt.
const check = verifyApprovalReceipt(
approval.receipt!,
{ ...action,
tenantId: WORKSPACE_ID,
nonce: approval.nonce!,
approvers: TRUSTED_APPROVERS },
{ expectedOrigin: wa.origin,
expectedRpId: wa.rpId },
)
if (!check.ok)
throw new Error(check.reason)
// Single use, for this instruction.
const used = await intyga.consume(
approval.nonce!, action)
if (!used.ok)
throw new Error(used.reason)
// Only now does the operation run.
await dropDatabase(action.params)
All names and values are examples. The receipt is shortened; the full shape is in the verification reference.
Try it yourselfReal signature check Β· Sample data Β· No operation executes
One approval. One exact action.
Imagine an AI agent requesting a database cleanup. This synthetic action is already signed. Change the table and see why the original signature cannot authorize the new request.
Example signed action
Delete table
payments_2024Database: acme-prod-db
Agent's proposed operation
Delete table
payments_2024Database: acme-prod-db
The interactive signature check loads in your browser.
Changing a signed parameter changes the bytes being verified. This example uses your browser's WebCrypto.
Edit the fields or inspect the signature check
The payload below is formatted for readability. Verification uses the compact canonical JSON bytes, with a real P-256 / SHA-256 signature check running locally in your browser.
This demonstrates signature binding only. It does not perform a passkey ceremony or validate a complete approval receipt, expiry, quorum, hardware-key requirements or single use. The fixture has a historical expiry and authorizes no real operation.
Now think about your approval process
Would it catch that change?
Find out with an action of your own and your own passkey.
The approving credential, checked against the approver keys your service trusts.
What was approved?
The action, its target and parameters, and the signed approval requirements.
Can someone else check?
Yes. The receipt can be checked with an open-source verifier and the required trust material.
An approval receipt proves approval. It does not prove the downstream operation ran.
A separate record of committed history.
The witness trail makes changes to committed approval history detectable, with checkpoints anchored to independent witnesses. It cannot prove an event was never withheld before commitment. Explore the trust boundaries β
Bring it back to your systems
Pick one operation you would want to explain after an incident.
Choose where you need human control. See what changes in your workflow and what evidence remains.
Showing the ai agents example.
AI agents
Let the agent propose the cleanup. Keep the final say.
An AI agent requests a production database cleanup. A person approves one table, but the agent later proposes a different target.
Could the agent still delete the other table?
Where approval is checked
Your execution service holds the database credential and verifies approval against the exact operation it will run. The agent can request work, but must have no credential or alternate route that bypasses this check.
What you keep
Keep the human signature and the action details it covers. A changed table needs a new approval.
Place the approval gate immediately before the operations you choose to protect. Your existing systems keep control of execution.
01β
Request
Your system
An operator, service, pipeline or agent submits the exact operation for approval.
02β
Sign
The approver
A person reviews the details and signs with a passkey. Your configured approval rules determine who must sign.
03β
Verify
Your service
Your code checks the receipt against its own operation parameters and trusted approver keys, offline.
04β
Execute
Your service
Only after the checks pass, your code consumes the approval once and performs the operation.
For your engineering team: inspect the verification code
Rebuild the expected operation from your own parameters and use your own trusted approver keys. Your execution path must enforce verification and prevent receipt reuse.
The approving signature is made by the person's authenticator. INTYGA does not hold its private key. Your service verifies against approver keys it independently trusts. Synced passkeys are supported; your rules can require a hardware-bound credential.
Could the requester lower the approval requirements?
Quorum and separation-of-duties requirements come from gateway-owned approval rules. A requester cannot lower the required number of signers through its request parameters.
What happens if INTYGA is unavailable?
Existing receipts can still be checked offline, subject to their validity and your verification requirements. New approvals wait, or use a separately configured Offline Approval procedure. A correctly integrated execution gate refuses an operation without valid approval.
Does this protect everything automatically?
You choose and integrate the operations to protect. Your execution service must check the approval, enforce the result and prevent reuse. Operations outside that path are outside INTYGA's coverage.
Investigate unusual authorization activity with evidence behind each finding. Intelligence runs on your infrastructure and uses INTYGA to protect sensitive configuration changes with signed approval.