A decision layer decides. Before any rail fires, the proposed payment is frozen into a decision capsule, checked against a non-overridable constitution, scored by a deterministic gate, and — for a full verdict — judged by a five-juror jury that returns APPROVED or REFUSED with a sealed receipt either way. ScriptMasterLabs' implementation is the Verdict Protocol, live today at verdict.scriptmasterlabs.com: the gate auto-pays at ≥0.80, holds for confirmation at 0.50–0.79, and escalates below 0.50, and a full verdict costs $0.25 in USDC on Base.
The layers the market talks about — agent cards, the Machine Payments Protocol (MPP), x402 — move money; the proof-of-allowance layer (Google AP2, Amex Intent) records what a principal permitted. None of them answers the question in this article's title. That missing layer is the fourth layer.
The quotable measurement: ScriptMasterLabs' live decision gate, probed on October 23, 2026 and verified identical across two consecutive runs, scored a bounded $0.001 API call at 0.9464 — auto-act. The same gate held an authorization for a wallet's full token balance at 0.50 (confirm band) and a cross-site login signature at 0.50. The routine ask and the catastrophic ask drew different outcomes from the same published bands, because the gate judges the payment itself, not the rail it rides on.
Full canonical: https://scriptmasterlabs.com/the-fourth-layer
The hole in the taxonomy: three rails and a record
A taxonomy now circulating in the agent-payments market — set out in an October 20, 2026 LinkedIn post by Alan L. and drawing wide comment in its first two days — describes agent payments as three technologies, plus a proof layer beside them. The shape is right; the map is incomplete:
| Layer | What it does | What it cannot do |
|---|---|---|
| Agent cards | Issue a payment credential to an agent, bounded by static limits set in advance | Judge a specific payment on its merits |
| Request-level rails (MPP, x402) | Settle the payment inside the API request | Ask whether the payment should fire |
| Proof of allowance (AP2, Intent) | Record what the principal authorized, for later issuer checks | Decide anything in real time |
| Decision layer (Verdict) | Score, judge, and seal a verdict before any rail fires | Move money — by design |
Rails compete on acceptance and speed; issuers compete on distribution; a neutral decision layer must be independent of the rail it judges — the same reason credit markets keep rating agencies separate from underwriters. A signature proves an agent could pay. An allowance record proves it was allowed to pay. Neither proves it should pay — and "should" is the only question that prevents the loss.
How a Verdict decision works
- Decision capsule. The proposed transaction is frozen into a signed-evidence record. Once frozen, it cannot be edited — jurors judge the record as sealed.
- Constitution gate. A non-overridable rule set checks the action class first. A constitution failure ends the pipeline: REFUSED, receipt sealed. No juror vote, no operator, no customer can override it.
- Deterministic score gate. Fixed published bands: ≥0.80 auto-pay · 0.50–0.79 confirm · <0.50 escalate to a human.
-
Jev jury. Five specialized jurors — CAUSAL, HISTORIAN, SKEPTIC, MICROSTRUCTURE, TAIL_RISK — vote independently on the frozen capsule, on a pinned model version,
jev-1.13.0. Approval requires at least 3 of 5 jurors voting PROCEED at ≥0.70 probability, with disagreement ≤0.40. Anything less is a refusal or a wait — sealed with the same rigor as an approval. - Sealed receipt. Receipt ID, capsule hash, juror votes, gate results, constitution result, timestamp, and the on-chain settlement transaction when settled through a Verdict rail. Fail-closed is absolute: no receipt, no proceed signal.
"Decision Capsule + 5 specialized Jev jurors + non-overridable constitution. Jev chooses. Code decides. Built for agents that manage real capital."
Receipts
The settlements below are ScriptMasterLabs' own end-to-end proof payments — published as proof the pipeline settles, and labeled as what they are: not customer purchases.
- Verdict tier, October 12, 2026 — $0.25 USDC on Base, tx 0xfa3ec31ff345167a474c682cec4e2eac505cfdd570e158961a233187be5f6f1c, Base block 52522538.
- Seal tier, October 23, 2026 — $0.01 USDC on Base, tx 0x08e3d6741c2f6b9197e712c8ff00abdee1ba7240ac0db474e10f6f17d7ef666f.
- AuthCaptureEscrow, October 13, 2026 — deployed and Sourcify-verified (exact match) on Arc mainnet: 0x06b4e6ba16b1ee0fac2d5f4ea69b93ce311fa7b4.
The institutional settlement layer: Arc
For institutions, a decision is only half the control problem — the other half is what happens to the money. Verdict's designated institutional settlement layer is Arc, Circle's USDC-native chain: USDC is the native asset (network eip155:5042), so there is no wrapped-asset or bridge leg; the AuthCaptureEscrow contract holds authorized funds in escrow and captures them only on a sealed PROCEED, releasing on refusal or expiry — the card world's authorize/capture pattern rebuilt for agent payments, with the jury's verdict as the capture trigger; and the Arc rail settles through Circle's x402 Facilitator Service, the same operational family as the live Base rails.
Arc state today, stated plainly: the escrow contract is live and verified; Verdict's Arc settlement rail is built and dark, pending a production Circle API key. No Arc settlement is claimed as live until a first escrow capture settles end-to-end and is published with its transaction hash.
Use it
-
POST https://verdict.scriptmasterlabs.com/decide— $0.25 USDC, full jury verdict, bring your own Jev key (the service stores no caller keys). -
POST https://verdict.scriptmasterlabs.com/seal— $0.01 USDC, sealed capsule receipt without the jury.
Payments settle in USDC on Base via x402, and replaying a completed payment returns the cached sealed receipt instead of charging twice. An unpaid call returns the 402 challenge quoting the tier price — probe it yourself.
The full product specification: https://scriptmasterlabs.com/verdict-protocol — the decision pattern: https://scriptmasterlabs.com/decision-gated-payments
Honest caveats
- The settlements cited are owner self-tests, verified on-chain, not customer purchases; no external customer decision is claimed.
- Arc settlement is built, not activated; live settlement is Base only.
- A hold is not a block: the confirm band holds a payment for confirmation. Jury votes are model judgments on a frozen capsule (one pinned model,
jev-1.13.0), not guarantees. - Probe scores are live single-day measurements, identical across two consecutive runs — evidence of the gate's behavior on those ask shapes, not calibrated probabilities.
ScriptMasterLabs — Script Master Labs, LLC. Service-Disabled Veteran-Owned Small Business (SDVOSB), SAM.gov registered. UEI: G24VZA4RLMK3 · CAGE: 21U51.
Top comments (0)