AG-841
Agent Contract-Formation Authority
EU AI Act
NIST AI RMF
ISO 42001
AGS Cross-Border Governance | Legal, Regulatory & Records | Version 3.1
Agent Contract-Formation Authority governs whether, when, and within what limits an autonomous agent may form a binding contract or legal commitment on behalf of its principal — establishing the agent's authority boundaries for offer, acceptance, and assent, and ensuring that contracts an agent enters are validly authorised, attributable, and enforceable.
As agents increasingly "click accept," place orders, and negotiate, the legal question of who is bound — and whether they intended to be — becomes central. This dimension provides the authority controls that keep agent-formed commitments within what the principal actually authorised.
In scope: the agent's authority to bind a principal contractually; limits on contract value/type/counterparty; verifiable authorisation and intent for agent-formed contracts; attribution and enforceability; cross-jurisdiction contract-formation differences.
Out of scope: payment-mandate authorisation (AG-809, the funds-movement complement), and general delegated-authority governance (AG-009). This dimension governs *the agent's legal authority to form contracts*.
If an agent can bind its principal to contracts beyond its authority — committing to terms, quantities, prices, or counterparties the principal never approved — the principal faces unintended legal obligations, disputes over whether assent was genuine, and enforceability uncertainty (since the agent is not a legal person). Clear contract-formation authority, with verifiable authorisation and limits, keeps agent-formed commitments enforceable and within intent, and resolves the "who really clicked accept" problem.
Test 6.1: Authority-Bounded Formation
Test 6.2: Enforceable Record
Test 6.3: Threshold Escalation
| Score | Criteria |
|---|---|
| 0 | The agent can bind the principal to contracts with no defined authority limits |
| 1 | Authority/value limits defined but no verifiable authorisation or intent record |
| 2 | Authority-bounded formation, verifiable authorisation, enforceable intent records, threshold escalation |
| 3 | Delegation-proof limits, jurisdiction-aware formation, dispute-ready evidence, repudiation/redress path |
Scenario A — Unauthorised Commitment: A procurement agent accepts supplier terms and a quantity beyond its mandate; the principal is now arguably bound to an unintended obligation. Authority limits with escalation would have prevented the commitment.
Scenario B — Disputed Assent: A counterparty claims a binding contract formed by an agent click; the principal cannot show what authority or intent backed it. Verifiable authorisation and an intent/assent record would have resolved enforceability.
Scenario C — Threshold Bypass: The agent splits a high-value commitment into sub-threshold pieces via sub-agents to avoid the approval gate. Delegation-proof limits and cumulative-threshold checks would have caught it.
| Requirement | EU AI Act | NIST AI RMF | ISO 42001 |
|---|---|---|---|
| R1: Defined contracting authority | Art. 26 — Deployer responsibilities | GOVERN 2.1 — Roles and accountability | A.9 — Use of AI systems |
| R2: No out-of-authority formation | Art. 14 — Human oversight | MANAGE 1.3 — High-priority response | Clause 8.1 — Operational control |
| R3: Verifiable authorisation | Art. 12 — Record-keeping | GOVERN 2.1 — Accountability | Clause 8.1 — Operational control |
| R4: Intent/assent enforceability record | Art. 12 — Traceability | GOVERN 2.1 — Accountability | Clause 8.1 — Operational control |
| R5: Jurisdiction-aware formation | Art. 26 — Operation per law | GOVERN 1.1 — Legal/regulatory | A.9 — Use of AI systems |
| R6: Threshold extra authorisation | Art. 14 — Human oversight | MANAGE 1.3 — High-priority response | Clause 8.1 — Operational control |
| R7: Delegation-proof limits | Art. 14 — Effective oversight | MAP 4.1 — Component risk | Clause 8.1 — Operational control |
| R8: Repudiation/redress path | Art. 26 — Deployer duties | MANAGE 4.3 — Incident communication | Clause 10.1 — Continual improvement |
Article 26 (deployer responsibility for the system's use) and Article 12 (record-keeping/traceability) require that agent-formed commitments are authorised and recorded sufficiently to attribute and enforce them — the legal backbone of agent contracting.
GOVERN 1.1 (legal/regulatory understanding) and GOVERN 2.1 (roles and accountability) require defined authority and accountability for legally-binding agent actions.
Annex A.9 (responsible use) and Clause 8.1 (operational control) require that an agent's legally-consequential actions stay within authorised, controlled bounds.