Internet Court for agents is now in session

A MetaMask delegation can stop an agent from spending outside its budget, its merchant list, or its expiry window. It can't tell you whether the payment the agent just made inside all of those limits was actually the right call. GenLayer built Internet Court to close that gap, running an AI validator jury on top of MetaMask's Smart Accounts Kit delegations and x402 payments that decides whether an agent's in-limit action still matched what the user meant, and can revoke its authority onchain when it didn't.

The limit of a limit

A user gives an agent a MetaMask Smart Account delegation scoped by token, recipient, budget, merchant, and expiry. MetaMask enforces that scope in code: an x402 payment that falls outside it gets blocked before the MetaMask x402 Facilitator ever settles it. But a payment can satisfy every one of those limits and still violate the user's actual, plain-language mandate. Internet Court's premise is that closing that second gap takes judgment, not another deterministic rule, which is what its GenLayer-powered AI jury is for.

"Agents are only useful if you can let them act without giving them the keys to everything. MetaMask gave us the right account infrastructure for that, and Internet Court adds the missing piece: what happens when an agent stays within its spending limits but still does the wrong thing." — Albert Castellana, GenLayer

Two systems, one control loop

GenLayer is an adjudication layer built for a certain kind of situation. Builders write Intelligent Contracts in Python, executed in the GenVM, that can read live web data, interpret natural language and unstructured evidence, and turn that judgment into an onchain outcome. Because that reasoning is non-deterministic, GenLayer's validators don't have to produce identical output to agree—they use the Equivalence Principle to reach consensus on meaning instead.

Internet Court is the layer that connects that adjudication capability to the rest of an agent transaction: identity, negotiation, obligations, payment and escrow, execution, and dispute resolution, the piece GenLayer supplies through its AI jury. A verdict from that jury can release funds, revoke permissions, or update an agent's reputation elsewhere in the system.

The jury itself runs on GenLayer's Optimistic Democracy Consensus: five validators are selected at random, each running its own LLM. One proposes a response; the other four evaluate it independently and vote to agree or disagree. Without a majority, the leader rotates and the round repeats. With a majority, the decision enters a 30-minute finality window during which anyone can appeal by staking more gas, which doubles the validator set (2n+1) up to the 1,534 validators available on mainnet. The approach leans on the Condorcet Jury Theorem: with a group of independent participants who are each individually more likely right than wrong, the group's collective answer is very likely correct.

GenLayer chose MetaMask's Smart Accounts Kit because it keeps the user as the account owner while giving the agent narrow, reusable authority: an ERC-7710/7715 delegation is signed once, constrained by onchain caveats, and redeemed without ever handing over the owner's key or requiring a signature on every payment. The MetaMask x402 Facilitator makes that practical for machine-to-machine payments—the same delegated permission serves as the payment context the Facilitator verifies and settles, repeatedly, within the limits the user already approved.

That split defines the control loop. MetaMask's Smart Accounts Kit onchain caveats block anything clearly outside the delegation before the Facilitator settles a payment. For what's technically inside the delegation but still questionable, a GenLayer Intelligent Contract reviews the user's mandate against the transaction data, receipts, and other signed evidence through the AI validator jury. A finalized decision can continue, constrain, or revoke the agent's future authority through an EVM-side controller—it does not reverse a payment that has already settled, unless that specific transaction also runs through a separate escrow or refund mechanism.

Building revoke-on-drift meant GenLayer couldn't rely on a single LLM check. It needed a supervisor Intelligent Contract that reviews the user's mandate alongside structured evidence from the agent's activity—transaction receipts, requests, responses—and returns a tightly scoped decision (continue, constrain, revoke, or escalate) tied to the exact mandate, permission, review window, and evidence bundle, so the result can be enforced without re-interpreting free-form model output. From there, a bridge waits for the decision to finalize and relays it onchain to revoke the delegation.

A working example, not yet a verifiable one

One flow already runs end to end: a user delegates a MetaMask Smart Account to an agent limited by merchant, budget, and expiry, with a broader mandate restricting it to purchasing sports-news services. GenLayer reviews the signed evidence behind each purchase, and if the agent buys something outside that mandate, the finalized decision revokes its delegated authority onchain—the agent's next payment attempt is rejected before funds move, while the user keeps the account and its remaining balance.

A second flow is in progress for service-level agreements: an agent pays for AI inference under terms like 99.5% successful responses and p95 latency under 800 milliseconds, with funds held in escrow until GenLayer evaluates the signed service logs and the contract releases full payment or applies a proportional deduction. Neither flow has a published transaction hash or case ID yet, so both are working implementations of the model rather than publicly verifiable production cases today.

Numbers worth a caveat

Forbes reported GenLayer processing roughly 350,000 transactions and 20,000 to 25,000 decisions a day on July 10, 2026; GenLayer's own public dashboard has more recently shown approximately 326,000 daily transactions, 25,800 daily decisions, and over 1,000,000 cumulative trustless decisions. Those figures describe activity across the GenLayer network as a whole, not usage of the MetaMask guardrails flow specifically—GenLayer hasn't yet published a breakdown of how many Smart Account delegations, x402 payments, or revocations have run through Internet Court's MetaMask integration.

What's next

GenLayer's roadmap places its Clarke testnet phase in the second half of 2026, with mainnet targeted for the fourth quarter. In parallel, GenLayer is working with the Internet Consortium on a Composable Adjudication ERC, which would let builders implement one interface and then choose which adjudicator resolves a dispute— GenLayer, Kleros, UMA, or a group of off-chain agents—bringing adjudication onto Ethereum as a first-class primitive rather than a one-off integration.

GenLayer also sees Internet Court reaching deeper into MetaMask's account infrastructure as the agent-commerce stack matures: giving each mandate a stable ID, generating signed evidence for every paid action, and mapping each finalized verdict directly to an account action, such as continuing, tightening, pausing, requiring approval, or revoking. The same jury model extends past payments, too—GenLayer points to prediction-market resolution, performance-based contracts, and insurance claims as workflows that need a neutral, disputed judgment call rather than a single backend's answer.