Actor context
Principal and agent
Keep the represented principal distinct from the acting agent and bind both to the authenticated tenant context.
Delegated authority
Authentication identifies an actor. Authority determines whether that actor may perform this exact commerce action for this principal, tenant, resource, amount, payee, and time window.
THE OPERATING MODEL
Effective authority can depend on a delegation, mandate, approval, policy limit, resource boundary, tenant route, revocation state, and the action currently requested. Those facts must be evaluated together at one known time.
The Agent Authority Map explains the supporting and missing evidence. It does not invent legal authority, rank agents, or convert absent evidence into trust.
WHAT THE RECORD MUST SHOW
Actor context
Keep the represented principal distinct from the acting agent and bind both to the authenticated tenant context.
Delegation scope
Record permitted actions, resources, amounts, beneficiaries, validity windows, and revocation evidence.
Exact action
Compare authority with the canonical action digest rather than relying on a broad role or reusable credential.
EVIDENCE FLOW
CLEAR PRODUCT BOUNDARY
AgentGateFee reports what the configured evidence supports. It does not certify an agent, create a delegation, provide identity proofing, or make a legal determination on the merchant's behalf.
COMMON QUESTIONS
No. Authentication can identify the actor, but action-level authority also needs applicable delegation, scope, limits, validity, policy, and context evidence.
The conflict remains explicit. In OBSERVE, the result explains that authorization would be required or the action would be reviewed or blocked; it does not modify the request.
No. Mandates and identity credentials remain with customer-selected providers. AgentGateFee consumes minimized references and verification state.
START WITH EVIDENCE