
Adam Frankel
General Counsel · Technology & AI
15+ years as General Counsel to technology, cloud & AI companies
Prefer the original wording?
AGENTIC AI PROCUREMENT AGREEMENT
This Agentic AI Procurement Agreement (this “Agreement”) is made effective as of [effective date] (the “Effective Date”), by and between:
(1) [customer legal name], a [customer entity type] organized under the laws of [customer state of organization] with its principal place of business at [customer address] (the “Customer”); and
(2) [vendor legal name], a [vendor entity type] organized under the laws of [vendor state of organization] with its principal place of business at [vendor address] (the “Vendor”).
The Customer and the Vendor may be referred to individually as a “Party” and together as the “Parties”.
WHEREAS, the Vendor develops and operates the Agentic Service, an AI agent service capable of planning and executing actions on a customer's behalf, autonomously or subject to human approval;
WHEREAS, the Customer wishes to procure and deploy the Agentic Service in its operations, subject to a defined delegation of authority, outcome-based performance standards, and the other terms of this Agreement; and
WHEREAS, the Parties intend that the authority the Customer delegates to the Agentic Service, and the guardrails on that authority, are set out in Exhibit A, the performance standards in Exhibit B, and the fees in Exhibit C.
NOW, THEREFORE, in consideration of the mutual covenants set out in this Agreement, and for other good and valuable consideration, the receipt and sufficiency of which are acknowledged, the Parties agree as follows:
1. DEFINITIONS
1.1 “Agentic Service” means the AI agent service identified in Exhibit A, including all AI Features, AI Technology, software, models, credentials, and interfaces the Vendor uses to provide it, that is authorized to plan, decide, and execute actions on the Customer's behalf within the Delegation of Authority.
1.2 “AI Customer Input” means information, data, materials, text, prompts, instructions, or other content that is provided or made available by or on behalf of the Customer or its authorized users to the Agentic Service, or collected or received by the Agentic Service for or on behalf of the Customer, including for purposes of configuring, grounding, or customizing the Agentic Service for the Customer.
1.3 “AI Customer Output” means information, data, materials, text, code, communications, decisions, actions, or other content generated or otherwise output by the Agentic Service in response to AI Customer Input or from the operation of the Agentic Service for the Customer, including the content of Autonomous Actions.
1.4 “AI Feature” means any feature, functionality, or component of the Agentic Service that incorporates, uses, depends on, or employs any AI Technology.
1.5 “AI Technology” means any and all machine learning, deep learning, and other artificial intelligence technologies, including statistical learning algorithms, models (including large language models), neural networks, and other artificial intelligence tools or methodologies, and all software implementations of any of the foregoing.
This is a preview. The full template is free on GitLaw.
This agreement provides a legal framework for a company to procure an AI agent capable of planning and executing actions autonomously. It establishes a formal Delegation of Authority, including Autonomous Actions, Escalation Triggers, and a mandatory kill switch to immediately suspend operations.
This is a specialized software procurement agreement for AI agents that act autonomously rather than just processing data. It contains unique controls for a Delegation of Authority and a Shadow-Mode pilot that are not found in standard SaaS agreements. It is NOT a general SaaS agreement or a simple consulting contract.
Use this when the AI service will interact with third parties or execute transactions without a human in the loop. The nearest alternative is a standard AI SaaS agreement, but that would lack the kill-switch and decision-log audit provisions contained here.
| Clause | Name | What it does |
|---|---|---|
| 2.2 | Delegation of Authority | Defines the scope of Vendor operations through categories of Autonomous Actions, Approval-Required Actions, and Prohibited Actions set out in Exhibit A. |
| 4 | Shadow-Mode Pilot and Acceptance | Requires the Agentic Service to run for a [pilot period] without executing live actions before the Customer provides written acceptance. |
| 5.1 | Outcome-Based Service Levels | Obliges the Vendor to meet accuracy, timeliness, and escalation compliance rates defined in Exhibit B rather than simple uptime metrics. |
| 6.1 | Kill-Switch Mechanism | Requires a console control, API, and emergency contact to suspend the service within [kill switch effectiveness] minutes of activation. |
| 7 | Model Changes | Provides a [model change notice period] and a re-acceptance right before the Vendor may deploy new Base Models. |
| 8.2 | No Training on Customer Data | Prohibits the Vendor from using Customer Data or Confidential Information to train, tune, or improve any AI Technology. |
| 9.1 | Decision Logs | Mandates human-readable logs for every action including the material inputs and the logic used to propose or execute the action. |
| 14.3 | Autonomous-Action Indemnity | Requires the Vendor to indemnify the Customer against third-party claims arising from AI acts outside the Delegation of Authority. |
A template isn't binding on its own - like any contract, it becomes binding once it's properly completed and signed. Templates in our curated library are professionally drafted for US or UK law; review any template before you sign it.
Yes. Chat with GitLaw to edit any section, or make changes directly in the editor.
Yes, read about team plans here.
Describe what you need in the chat and GitLaw will draft it for you.
Templates in our curated library are professionally drafted for US or UK law. The wider library comes from the GitLaw community and public sources - a solid starting point, but check any template fits your situation before you rely on it.
Mostly US and UK law. Some templates use general commercial terms that work across jurisdictions, and many note which law they're written for.
It depends on the situation. Templates work well for routine business agreements. For anything involving significant money, complex IP, employment, or areas you're unsure about, it's worth getting professional advice before you sign. GitLaw provides templates and tools, not legal advice.
Open any template in GitLaw and describe the change you want in the chat — 'make clause 4 mutual' or 'add a 30-day notice period', for example. GitLaw drafts the revised language and shows it as a suggested edit. You accept, reject, or keep editing from there.
Yes. Upload a Word, PDF, or Markdown file and GitLaw will open it in the editor. You can review, edit, or chat with GitLaw about it the same way you would with any template from the library.


Every template opens in an editor with an AI agent alongside it.
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
Share it for negotiation, then collect signatures without leaving GitLaw.
eSign included
Trained on 5,500+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.
No sales calls, no credit card. Just chat with GitLaw.
GitLaw provides templates and tools, not legal advice. Templates are a starting point, not a substitute for advice on your situation - for anything significant, speak to a qualified lawyer.