API Service Level Agreement.
These clauses outline the service levels for the Emmi Climate Risk APIs.
- API Availability
The Licensor will use commercially reasonable efforts to make the API available on a continuous basis.
The Licensor does not guarantee uninterrupted or error-free operation of the API.
The Licensor operates with a Service Level Objective of ≥ 99% availability, calculated per API endpoint, per Calendar Month.
Availability does not include downtime resulting from:
- planned maintenance;
- emergency maintenance;
- force majeure events;
- failures of third-party infrastructure, networks, cloud service Licensors or internet connectivity;
- issues caused by the Licensee’s systems, integrations or misuse of the API.
The Licensor may perform planned maintenance from time to time and will use reasonable efforts to provide advance notice where such maintenance is expected to materially impact API availability.
- Performance and Rate Limiting
The Licensor may impose reasonable technical limits on API usage, including request rate limits, concurrency limits, payload size limits and usage quotas, in order to protect service stability and performance.
The Licensor does not guarantee specific response times or latency, but will use commercially reasonable efforts to ensure consistent performance under normal operating conditions.
If usage exceeds permitted limits, the Licensor may throttle requests, return error responses (including HTTP 429), or temporarily suspend access.
The Licensor operates with a Service Level Objective of having p99 response time at <1 minute, and an error-rate below 1% of requests, calculated per API endpoint, per day.
- Support and Incident Management
The Licensor will provide reasonable technical support to the Licensee during normal business hours (AEDT/AEST).
Support requests must be submitted via email to support@emmi.io, and must include sufficient detail to allow investigation, including relevant endpoints, timestamps and error messages.
The Licensor will use reasonable efforts to respond to incidents based on severity, prioritising issues that materially affect API availability or security.
- API Changes, Versioning and Deprecation
The Licensor may update, modify or enhance the API from time to time, including adding new endpoints, fields or functionality.
The Licensor will not intentionally introduce breaking changes to the API without providing reasonable prior notice, except where required for security, legal or operational reasons.
The Licensor may deprecate API versions or features. Where reasonably practicable, the Licensor will provide advance notice of deprecation and allow a reasonable transition period before removal
- Data Accuracy, Quality and Corrections
The Data is derived from third-party sources, proprietary models and analytical processes and may contain inaccuracies, omissions or errors.
The Licensor does not warrant that the Data is complete, accurate, current or error-free.
If the Licensee becomes aware of a suspected material error in the Data, it may notify the Licensor. The Licensor will use commercially reasonable efforts to investigate and, where appropriate, correct such errors within a reasonable timeframe.
Corrections to the Data may be applied prospectively and do not obligate the Licensor to reprocess, restate or correct historical outputs unless expressly agreed in writing.
- Data Freshness and Updates
The Licensor may update the Data on a periodic or event-driven basis. Any stated update frequencies are indicative only and not guaranteed.
The Licensor may modify, backfill or revise Data as methodologies, inputs or sources change.
Timestamps or “as at” indicators provided with the Data reflect the Licensor’s internal processing times and may not correspond to real-world event timing.
- Security and Authentication
Access to the API is controlled through authentication credentials issued by the Licensor.
The Licensee must:
- keep credentials secure and confidential;
- rotate credentials where required by the Licensor;
- implement reasonable security controls to prevent unauthorised access.
The Licensor may revoke or rotate credentials if it reasonably believes security has been compromised.
Each party must maintain commercially reasonable administrative, technical and organisational safeguards to protect the Data and API.
- Monitoring and Abuse Prevention
The Licensor may monitor API usage to:
- ensure compliance with the Agreement;
- detect misuse, abuse or security incidents;
- calculate Fees and royalties;
- improve service performance.
The Licensee must not attempt to bypass or interfere with monitoring, rate limiting or access controls.
- Status Notifications
The Licensor may maintain a service status page or other notification mechanism to communicate service incidents, maintenance and operational updates.
The Licensor will use reasonable efforts to notify the Licensee of material service disruptions and to provide updates during significant incidents.
- No Service Credits
Unless expressly agreed in writing, service availability issues, performance degradation or data inaccuracies do not entitle the Licensee to service credits, refunds or fee reductions.
