the layer the console A destination page states what our code does there, and nothing about who we work with.
runs as-is

Base
as a destination.

EVM · the delegate is bytecode, and this is bytecode's home

All ten reasons are available here the moment the delegate lands, because none of them are chain-specific. What follows is the whole of what that takes, stated as work rather than as a conversation.

What it takesFour facts, and none of them need anyone's agreement.
the codeUnchanged. SessionKeyDelegate is EVM bytecode with a pinned runtime hash, and the same artifact deploys at every EVM destination.
the deployOne transaction. After it lands you check the deployed runtime against the pinned hash and the check either matches or it does not.
the preconditionThe chain has activated EIP-7702. The authorization tuple signs only chain id, delegate address and nonce, which is what lets the scope live in your own account instead of a contract wallet you had to move to.
what the venue doesNothing. The bound sits at the wallet, so a market here does not integrate with UNTOLL, get asked for an API key, or change a line. Your agent trades at it the way it already would.
The ten reasons, hereEvery one of them is a check inside the delegate, so every one travels with it.
✓TARGET
✓SELECTOR
✓PER_TX
✓PER_EPOCH
✓RECIPIENT
✓EXPIRED
✓UNIT_PER_TX
✓UNIT_PER_EPOCH
✓GRANT_LIMIT
✓CALLDATA_SHORT

Ten of ten. The count is a property of the delegate rather than of the destination, which is why it is the same number at every EVM row and why a non-EVM row cannot borrow it.

A scope written for hereThe console writes this. It is the same object at every destination.
agent scout may call swap(...), buy(...) on 2 named contracts value 1.0 ETH per tx / 5.0 ETH per day units 250 per tx / 1000 per day output to you and nobody else until 30 days from install may leave 3 standing approvals at Base

Change the last line and everything above it holds unchanged. That is the whole reason a destination is a choice rather than a rebuild.

What a refusal looks like hereThe same event, on this chain's explorer.
01
An allowed call carrying more than the per-transaction cap.
PER_TX

Nothing forwards, and the attempt is mined as a ScopeViolation event carrying the target, the selector and the reason. It is readable by anyone, on this chain, without asking us for a log.

Held
mined ScopeViolation
moved 0 wei

A refusal on this chain is native activity on this chain. That is the part worth saying plainly to anyone who runs one: enforcement here does not route volume away, it produces its own.

Scope an agent for here →All destinations
UNTOLL, the enforcement layer for agent trading. the layer  ·  run the demo  ·  all destinations