AI Action Verification · Interactive Console & Agent Action Gate

Every AI action, verified before it executes.

Adversarial AI review for teams and autonomous agents — verifying every high-stakes decision and agent action before execution.

AGENT ACTION PROPOSAL GATE
ACTION 1 OF 4 · HIGH-VALUE WIRE
PROPOSAL: "Transfer $12,400 to external vendor acct-8841"
FLAGGED · POLICY CHECK
Launch Review Console See Threat Model
Approve or block in real time Signed audit trail Works with any agent framework
00 · The standard

Every high-stakes decision deserves cross-examination.

"Who authorized this amount?"
"Is this recipient verified?"
"Does this match policy?"
Agent actionWire $12,400 · acct-8841
"What does the record show?"
"Has this run before?"
"Who is accountable?"

Most actions pass. Some don't.

Refund customer #2201 · $42.00PASS
Update CRM record · contact-7734PASS
Send invoice · acct-5510PASS
Wire $12,400 · acct-8841BLOCKED
Rotate API key · svc-gatewayPASS
Export table · pii_customersBLOCKED
The guarantee

The verdict is signed — before execution.

Every verdict checks the action against known attack patterns and the active policy layer — the policy in force is hashed into the signed receipt.

APPROVED
Agent action · intercepted

Wire $12,400 to acct-8841

Initiated by agent:finance-ops · persona financial_compliance · 4 nodes
REVIEW GATE — execution halted
Node 01 · amount within policy limitCLEAR
Node 02 · recipient verified against recordCLEAR
Node 03 · matches approved workflow step 4/4CLEAR
Node 04 · no prior evidence for this payeeCHALLENGED
SIGNED · ef_attest_v5 · Ed25519-EdDSA · 9f3a…c21e

Two audiences. One standard of proof.

For teams

Independent models cross-examine your hardest questions, strategies, and documents.

Review Console →

For agents

Every action reviewed, approved or blocked, before it runs.

API →
01 · The threat model

The ways AI agents are attacked are documented, categorized, and measured.

Security bodies like OWASP and MITRE maintain public catalogs of the techniques. The consistent finding across independent benchmarks: without a check at execution time, AI systems fail 24–84% of realistic attacks.

The floor — an agent with no check

Published, peer-reviewable results for unprotected models:

InjecAgent (Deng et al., WWW 2024):
Prompted GPT-4 failed 24% of direct attacks — 47% against enhanced, multi-step attacks. Llama-2-70B: over 80%.
24%–47% FAIL
Agent Security Bench:
Highest average attack-success rate across 13 model backbones is 84.3%. A 2026 independent evaluation put GPT-5.1 at roughly 70% on average.
84.3% PEAK FAIL
Meta CyberSecEval 3:
Published per-model injection success rates of 20–40%.
20%–40% FAIL

These are published, independent numbers — not marketing.

The ceiling — the same attack surface, with the gate
97.5% defense (2.5% fail-open, 95% CI 2.07–3.04) scored across 4,203 hazard cells

Our external battery — 4,221 pre-registered test cases drawn from the same published suites, run in a single campaign. Every verdict a signed receipt:

InjecAgent: 2,108 attack scenarios 100% DEFENDED
AgentDojo: 123 attack scenarios, four environments 100% DEFENDED
PyRIT converters: 400 attack scenarios 99.75%
garak: 721 attack scenarios 98.9%
HarmBench: 200 attack scenarios 96–98%
PurpleLlama CyberSecEval: 251 attack scenarios 91.2%
Agent Security Bench: 400 attack scenarios 82.8%
✓ Independent re-verification on a later build re-ran the full battery: 2.49% fail-open, reproducing the original 2.52% within the confidence interval. The result holds across builds.
One caveat, in plain sight: the published baselines are unprotected models and our numbers are with the gate, so the comparison is directional until a methodology-reconciliation pass we have scheduled. Every one of our test cases is published, signed, and independently re-runnable. No other vendor in our category has published results on these suites.

Why the check has to run at execution time

Architectural failure modes that bypass pre-deployment model audits.

01 · STATIC WEIGHTS

Training and fine-tuning

Harden a model against yesterday's wording. Freshly reworded attacks are where model-only defenses leak.

02 · DECOUPLED AUDITS

Audits and evals

Certify the model, not the action. An agent can pass every eval and still export a customer table because a poisoned web page told it to.

03 · DYNAMIC CONTEXT

Static policy tools

Check rules, not context. The most damaging attacks don't break rules — they chain legal moves: three $9,900 transfers around a $10,000 limit. Catching that requires cross-examining the action against its own history, at runtime, every time.

EthersFlow does not grade the model. It judges the action — in context, before it fires, with a signed verdict you can hold afterward.

CRYPTOGRAPHIC INTEGRITY

Policy, enforced and attested

Every action is also judged against EthersFlow's built-in policy layer: spend limits, sensitive-data handling, credential handling. A policy violation is grounds for rejection on its own, and the policy in force is hashed into every signed verdict.

TRANSPARENT BOUNDARIES

What we disclose

A fail-closed gate has friction: borderline-benign actions are escalated to human review rather than rubber-stamped. Pre-registered benign cases approve at 97.2%; our dedicated benign-control set is deliberately small and we say so — a larger innocent-case control battery is an open roadmap item, published as such. Full methodology and known gaps ship with the numbers: 4,203 scored attack scenarios at 97.5% defense, re-verified on a later build.

The full methodology, per-suite results, and disclosure of open gaps are in the EthersFlow External Verification Report.

02 · Category architecture

Identity verifies who. Authorization defines scope. EthersFlow verifies the action.

AI now finds critical vulnerabilities on its own. The next ones won't be exploited by people — they'll be exploited by agents with legitimate access. Your firewall can't see that coming. A verdict on every action can.

LAYER 01

Identity (KYA)

Sumsub · Entrust · Persona

Who is the agent and whose authority does it represent?

LAYER 02

Authorization (AP2)

Google · Visa · OAuth · A2A

What permissions, OAuth scopes, or spend rails is it granted?

LAYER 03

Action Verification (KYAA)

The missing layer in the stack

Is THIS specific action legitimate? Signed verdict before execution.

LAYER 04

Execution

Verified execution state

Consequential tool call runs only with cryptographic clearance.

03 · Verification protocol

Decisions made inspectable — before a single tool runs.

Every request passes through heterogeneous reviewer personas, conflict mapping, and cryptographic attestation.

01.

Configure Reviewer Council

financial_compliance · cybersecurity_auditor · clinical_safety · legal_citation · general_adversarial (2–7 nodes)

Assign independent domain personas across heterogeneous models with strict quorum thresholds.

02.

Adversarial Cross-Examination

consensus_score · risk_index · reviewer_agreement · reason_codes

Models challenge assumptions in parallel, exposing unanchored claims, contradictions, and policy violations.

03.

Signed Clearance Verdict

Verify offline via efverify.py · Ed25519-EdDSA

Returns APPROVED, FLAGGED_HUMAN_REVIEW, or REJECTED with an offline-verifiable signature receipt.

04 · Developer extension

Verifiable trust verdicts in your agent's execution path.

SDK, REST API (/api/v1/verify), or native MCP server — one call returns the verdict.

Explore Developer Hub
4,203 attack scenarios defended at 97.5% · re-verified on a later build · results published, signed, independently re-runnable
VerdictAPPROVED
Council4 nodes · independent personas
Policyfinops_default_v1
Signatureef_attest_v5 · Ed25519 · 9f3a…c21e
Time2026-11-07T10:15:00Z

Every AI action, verified before it executes.

EthersFlow Research White Paper

Download the External Verification Report

Get instant access to the complete 4,203-scenario benchmark report, confidence intervals, and attestation methodology. An account will be initialized for your review console access.

The information you provide will be treated in accordance with the EthersFlow Privacy Notice.