Put policy before execution.

Sentinel is an advisory authorization gateway. Your execution system must enforce its decision and bind the exact evaluated transaction.

1. Register and create a policy

Create a local account in the workspace, register an agent, and configure an allowlist, permitted networks and exact wei ceilings. API keys are scoped to an agent and shown once.

2. Evaluate a proposed transaction

const response = await fetch('/v1/transactions/evaluate', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: 'Bearer ' + process.env.QYPHERA_AGENT_KEY
  },
  body: JSON.stringify({
    agentId, requestId: crypto.randomUUID(),
    network: 'base', to: permittedAddress,
    valueWei: '1000000000000000', data: '0x'
  })
});
if (!response.ok) throw new Error('Do not execute');
const result = await response.json();
// Deny and review are never execution approval.
// Inspect result and enforce the exact request in your executor.

3. Enforce and record

Never execute after an unavailable response, denial or review decision. Evaluation does not sign transactions. Native spending reservations are conservative and must not be interpreted as settlement records.

4. Handle durable approval

For a review decision, an account owner can approve or reject the stored request in Sentinel. HTTP 202 means processing, not permission to execute. Poll the approval endpoint until a terminal state; inspect its final result. Policy changes, expiration and spending ceilings can still prevent authorization. Closing the page does not cancel a submitted workflow.

5. Monitor evidence changes

The workspace offers automatic checks for eligible test plans. Cloudflare Agents retain scheduling state and stream progress to the dashboard. Local execution requires the development runtime to remain running. No production schedule, external notification channel or AI model is activated by this interface.