AI PERFORMANCE SERVICE LEVEL AGREEMENT
AGREEMENT DATE: [DATE]
SLA NUMBER: [SLA-NUMBER]
EFFECTIVE DATE: [DATE]
PARTIES
SERVICE PROVIDER ("Provider"):
- Legal Name: [PROVIDER LEGAL NAME]
- Address: [FULL ADDRESS]
- Contact: [NAME, EMAIL, PHONE]
CUSTOMER ("Customer"):
- Legal Name: [CUSTOMER LEGAL NAME]
- Address: [FULL ADDRESS]
- Contact: [NAME, EMAIL, PHONE]
1. OVERVIEW
1.1 Purpose
This AI Performance Service Level Agreement ("SLA") defines the performance standards, metrics, and remedies applicable to the AI services provided by Provider to Customer under the Master Agreement dated [DATE] ("Master Agreement").
1.2 AI Services Covered
| Service | Description | Tier |
|---|---|---|
| [SERVICE 1] | [DESCRIPTION] | ☐ Standard ☐ Premium ☐ Enterprise |
| [SERVICE 2] | [DESCRIPTION] | ☐ Standard ☐ Premium ☐ Enterprise |
| [SERVICE 3] | [DESCRIPTION] | ☐ Standard ☐ Premium ☐ Enterprise |
1.3 Service Tiers
| Tier | Description | Monthly Fee |
|---|---|---|
| Standard | [DESCRIPTION] | $[AMOUNT] |
| Premium | [DESCRIPTION] | $[AMOUNT] |
| Enterprise | [DESCRIPTION] | $[AMOUNT] |
2. AVAILABILITY SLA
2.1 Availability Commitment
Provider commits to the following availability levels:
| Tier | Monthly Availability | Annual Availability | Max Downtime/Month |
|---|---|---|---|
| Standard | 99.5% | 99.5% | 3.6 hours |
| Premium | 99.9% | 99.9% | 43.8 minutes |
| Enterprise | 99.95% | 99.95% | 21.9 minutes |
2.2 Availability Calculation
Availability % = ((Total Minutes - Downtime Minutes) / Total Minutes) x 100
- Total Minutes: Total minutes in the measurement period
- Downtime Minutes: Minutes when service was unavailable
2.3 Exclusions from Downtime
The following are NOT counted as Downtime:
☐ Scheduled maintenance (with [X] hours advance notice)
☐ Emergency maintenance (with notification as soon as practicable)
☐ Customer-caused issues
☐ Third-party service outages beyond Provider's control
☐ Force majeure events
☐ Periods during which Customer exceeded usage limits
2.4 Scheduled Maintenance
- Maintenance Window: [DAY/TIME] to [DAY/TIME] [TIMEZONE]
- Advance Notice: [X] hours/days
- Maximum Monthly Maintenance: [X] hours
- Notification Method: [EMAIL/DASHBOARD/API]
3. PERFORMANCE SLA
3.1 Response Time
| Operation | Target | Maximum | Measurement |
|---|---|---|---|
| API Response Time (P50) | [X] ms | [X] ms | 50th percentile |
| API Response Time (P95) | [X] ms | [X] ms | 95th percentile |
| API Response Time (P99) | [X] ms | [X] ms | 99th percentile |
| Batch Processing | [X] sec/record | [X] sec/record | Average |
3.2 Throughput
| Tier | Rate Limit | Burst Limit |
|---|---|---|
| Standard | [X] requests/second | [X] requests/second |
| Premium | [X] requests/second | [X] requests/second |
| Enterprise | [X] requests/second | [X] requests/second |
3.3 Concurrency
| Tier | Max Concurrent Requests |
|---|---|
| Standard | [X] |
| Premium | [X] |
| Enterprise | [X] |
4. AI-SPECIFIC PERFORMANCE SLA
4.1 Model Accuracy
Provider commits to maintaining the following accuracy levels:
| Model/Service | Metric | Minimum | Target | Measurement Dataset |
|---|---|---|---|---|
| [MODEL 1] | Accuracy | [X]% | [X]% | [DATASET] |
| [MODEL 1] | Precision | [X]% | [X]% | [DATASET] |
| [MODEL 1] | Recall | [X]% | [X]% | [DATASET] |
| [MODEL 2] | F1 Score | [X] | [X] | [DATASET] |
4.2 Accuracy Measurement
- Measurement Frequency: [MONTHLY/QUARTERLY]
- Measurement Method: [DESCRIBE]
- Benchmark Dataset: [DESCRIBE OR REFERENCE]
- Reporting: Provider will report accuracy metrics [FREQUENCY]
4.3 Model Drift Monitoring
Provider commits to:
☐ Monitor for model drift
☐ Alert Customer if accuracy drops below threshold
☐ Retrain or update models to maintain accuracy
☐ Provide drift reports: [FREQUENCY]
4.4 Consistency
| Metric | Commitment |
|---|---|
| Output Consistency | Same input produces consistent output [X]% of time |
| Version Consistency | [X] days notice before model version changes |
4.5 AI-Specific Exclusions
Accuracy SLAs do not apply to:
☐ Inputs outside documented specifications
☐ Edge cases outside training distribution
☐ Adversarial inputs
☐ New data types or formats not previously agreed
5. SUPPORT SLA
5.1 Support Hours
| Tier | Support Hours | Channels |
|---|---|---|
| Standard | Business hours [TIMEZONE] | Email, Ticket |
| Premium | Extended hours | Email, Ticket, Chat |
| Enterprise | 24/7 | Email, Ticket, Chat, Phone |
5.2 Response Times
| Priority | Description | Response Time by Tier |
|---|---|---|
| Standard | ||
| P1 - Critical | Service completely unavailable | 4 hours |
| P2 - High | Major functionality impaired | 8 hours |
| P3 - Medium | Partial functionality issue | 24 hours |
| P4 - Low | Minor issue or question | 48 hours |
5.3 Resolution Targets
| Priority | Target Resolution Time |
|---|---|
| P1 - Critical | [X] hours |
| P2 - High | [X] hours |
| P3 - Medium | [X] business days |
| P4 - Low | [X] business days |
Note: Resolution targets are goals, not commitments. Response times are commitments.
5.4 Escalation Procedures
| Stage | Timeframe | Escalated To |
|---|---|---|
| Level 1 | Initial | Support Team |
| Level 2 | After [X] hours | Support Manager |
| Level 3 | After [X] hours | Service Director |
| Executive | After [X] hours | VP/Executive |
6. SERVICE CREDITS
6.1 Availability Credits
| Monthly Availability | Service Credit |
|---|---|
| 99.0% - < Commitment | 10% of monthly fee |
| 95.0% - < 99.0% | 25% of monthly fee |
| 90.0% - < 95.0% | 50% of monthly fee |
| < 90.0% | 100% of monthly fee |
6.2 Performance Credits
| SLA Breach | Service Credit |
|---|---|
| Response time breach (>10% of requests) | 10% of monthly fee |
| Accuracy breach | 15% of monthly fee |
| Support response breach (P1/P2) | 10% of monthly fee |
6.3 Credit Cap
Maximum monthly service credits: [50/100]% of monthly fees
6.4 Credit Request Process
- Customer must request credits within [30] days of incident
- Request must include incident details and impact
- Provider will verify and respond within [X] days
- Approved credits applied to next invoice
6.5 Credit Exclusions
Credits not available for:
☐ Breaches caused by Customer
☐ Breaches during excluded periods
☐ Customers not in good standing (payment)
☐ Beta or preview features
7. MONITORING AND REPORTING
7.1 Provider Monitoring
Provider shall:
☐ Monitor service availability continuously
☐ Monitor performance metrics
☐ Monitor AI model accuracy
☐ Maintain dashboards accessible to Customer
☐ Send proactive alerts for issues
7.2 Status Page
Provider maintains status page at: [URL]
Information includes:
☐ Current service status
☐ Scheduled maintenance
☐ Historical uptime
☐ Incident history
7.3 Reports
| Report | Content | Frequency | Delivery |
|---|---|---|---|
| Availability Report | Uptime, downtime, incidents | Monthly | [METHOD] |
| Performance Report | Response times, throughput | Monthly | [METHOD] |
| Accuracy Report | Model accuracy metrics | [FREQUENCY] | [METHOD] |
| Support Report | Tickets, resolution times | Monthly | [METHOD] |
7.4 Customer Monitoring
Customer may:
☐ Access real-time dashboards
☐ Set up custom alerts
☐ Query metrics via API
☐ Export historical data
8. INCIDENT MANAGEMENT
8.1 Incident Classification
| Severity | Definition | Examples |
|---|---|---|
| Critical | Complete service outage | API completely down |
| Major | Significant functionality unavailable | Core feature broken |
| Minor | Partial degradation | Slow response times |
| Low | Minimal impact | Cosmetic issues |
8.2 Incident Response
Provider will:
☐ Acknowledge incident within response time
☐ Provide regular updates: [FREQUENCY]
☐ Perform root cause analysis
☐ Provide post-incident report within [X] days
8.3 Post-Incident Review
For Critical/Major incidents, Provider will provide:
☐ Incident timeline
☐ Root cause analysis
☐ Impact assessment
☐ Remediation actions
☐ Prevention measures
9. CHANGE MANAGEMENT
9.1 Model Updates
Provider will:
☐ Notify Customer [X] days before significant model updates
☐ Provide changelog and impact assessment
☐ Allow opt-out period for major changes: [PERIOD]
☐ Maintain previous versions for: [PERIOD]
9.2 API Changes
| Change Type | Notice Period |
|---|---|
| Breaking changes | [X] days |
| Deprecation | [X] days |
| New features | [X] days |
| Security fixes | As soon as practical |
9.3 Version Support
Provider will support previous versions for [X] months after new release.
10. DATA AND SECURITY
10.1 Data Processing SLA
| Metric | Commitment |
|---|---|
| Data processing latency | [X] seconds |
| Data retention | Per Data Processing Agreement |
| Backup frequency | [FREQUENCY] |
| Recovery time objective | [X] hours |
| Recovery point objective | [X] hours |
10.2 Security Incident Response
| Severity | Response Time |
|---|---|
| Critical security incident | [X] hours |
| High security incident | [X] hours |
| Medium security incident | [X] hours |
11. CUSTOMER RESPONSIBILITIES
11.1 Usage Requirements
Customer shall:
☐ Use service within documented limits
☐ Implement proper error handling
☐ Follow integration best practices
☐ Maintain current API versions
☐ Report issues promptly
11.2 Cooperation
Customer shall:
☐ Provide information needed for troubleshooting
☐ Implement recommended fixes
☐ Participate in incident resolution
12. SLA REVIEW AND MODIFICATION
12.1 Review
This SLA will be reviewed:
☐ Annually
☐ Upon significant service changes
☐ Upon Customer request (reasonable)
12.2 Modification
Modifications require:
☐ [30] days written notice
☐ Mutual agreement for material changes
☐ Customer may terminate if materially adverse
13. TERM
This SLA is effective from [DATE] and continues for the term of the Master Agreement.
SIGNATURES
PROVIDER:
Signature: _________________________________ Date: _____________
Name: [NAME] Title: [TITLE]
CUSTOMER:
Signature: _________________________________ Date: _____________
Name: [NAME] Title: [TITLE]
APPENDIX A: DEFINITIONS
Availability: Percentage of time the service is operational and accessible.
Downtime: Period when service is unavailable or fails to perform within specifications.
Response Time: Time to begin processing a request.
P50/P95/P99: 50th, 95th, and 99th percentile response times.
Service Credit: Credit applied to Customer's account for SLA breaches.
APPENDIX B: SERVICE CREDIT REQUEST FORM
Customer Information:
- Customer Name: _________________________________
- Account ID: _________________________________
- Contact: _________________________________
Incident Information:
- Incident Date(s): _________________________________
- Incident Duration: _________________________________
- SLA Breached: _________________________________
- Impact Description: _________________________________
Credit Requested: _________________________________
Supporting Documentation: ☐ Attached
Signature: _________________________________ Date: _____________
This AI Performance SLA Agreement template is provided for informational purposes. Legal counsel review is recommended.
About This Template
Jurisdiction-Specific
This template is drafted for general use across all U.S. jurisdictions. State-specific versions with local statutory references are also available.
How It's Made
Drafted using current statutory databases and legal standards for contracts agreements. Each template includes proper legal citations, defined terms, and standard protective clauses.
Important Notice
This template is provided for informational purposes. It is not legal advice. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.
Last updated: February 2026