API Terms of Service

1. API ACCESS AND LICENSE

1.1 License Grant. Subject to your compliance with these API Terms, REPLR grants you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the REPLR API solely to develop, test, and operate applications that integrate with the REPLR Service ("Client Applications").

1.2 API Keys. Access to the API requires authentication via API keys issued through your REPLR account. API keys are confidential credentials. You shall: (a) keep API keys secure and confidential; (b) not share API keys with unauthorized parties; (c) not embed API keys in client-side code, public repositories, or otherwise expose them; and (d) immediately revoke and regenerate any API key you believe has been compromised. You are responsible for all activity that occurs using your API keys.

1.3 Account Requirements. API access requires a Pro tier subscription or above. The features, rate limits, and capabilities available through the API correspond to your subscription tier as described in our rate limits documentation.

2. PERMITTED AND PROHIBITED USES

2.1 Permitted Uses. You may use the API to: (a) create, manage, and interact with REPLRs programmatically; (b) integrate REPLR conversation capabilities into your own applications and services; (c) build tools that complement the REPLR ecosystem; and (d) access your own account data for backup, analytics, or integration purposes.

2.2 Prohibited Uses. You shall not:

• Resell, redistribute, or sublicense API access without prior written permission from REPLR
• Use the API to build a product or service that competes directly with the REPLR platform
• Circumvent, disable, or interfere with rate limits, authentication mechanisms, or other security features
• Use the API to scrape, extract, or systematically collect data from the REPLR platform for purposes other than your authorized use
• Use API-generated content to train, fine-tune, or develop machine learning models without REPLR's prior written consent
• Misrepresent your Client Application's affiliation with or endorsement by REPLR
• Use the API in any manner that violates the Acceptable Use Policy or applicable law
• Exceed the number of API keys or accounts permitted under your subscription tier

3. RATE LIMITS AND QUOTAS

3.1 Limits. The API is subject to rate limits and usage quotas that vary by subscription tier and endpoint. Current rate limits are documented at /docs/rate-limits. Rate limit information is also provided in response headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset).

3.2 Exceeding Limits. Requests that exceed applicable rate limits will receive an HTTP 429 (Too Many Requests) response. Persistent or intentional circumvention of rate limits may result in temporary or permanent revocation of API access.

3.3 Changes. REPLR reserves the right to modify rate limits and quotas at any time. We will provide at least fourteen (14) days' notice before reducing rate limits for existing subscription tiers.

4. DATA HANDLING AND PRIVACY

4.1 User Data. If your Client Application collects, processes, or transmits personal data of end users to or through the REPLR API, you must: (a) maintain a privacy policy that accurately discloses your data practices, including the use of third-party AI services; (b) obtain all necessary consents from end users for the processing of their data; (c) comply with all applicable data protection laws, including the GDPR and CCPA where applicable; and (d) promptly notify REPLR of any data breach affecting data transmitted through the API.

4.2 Data Retention. Data transmitted to the REPLR API is processed and stored in accordance with our Privacy Policy. Conversation data created through the API is subject to the same retention policies as data created through the REPLR web interface.

4.3 Data Processing Agreement. If your use of the API involves processing personal data of individuals in the European Economic Area, United Kingdom, or Switzerland, the Data Processing Agreement applies to such processing.

5. SERVICE LEVELS

5.1 Availability. REPLR targets 99.9% uptime for the API but does not guarantee any specific level of availability. The API is provided on an "as is" and "as available" basis. Scheduled maintenance windows will be communicated at least forty-eight (48) hours in advance when practicable.

5.2 No SLA. Unless you have entered into a separate Enterprise Agreement with REPLR that includes specific service level commitments, no service level agreement applies to your use of the API. REPLR shall not be liable for any downtime, latency, or unavailability of the API.

6. API CHANGES AND VERSIONING

6.1 Versioning. The API is versioned (currently v1). REPLR will maintain backward compatibility within a major version to the extent commercially reasonable.

6.2 Breaking Changes. If REPLR needs to introduce breaking changes, we will: (a) provide at least thirty (30) days' notice; (b) release the changes under a new API version where possible; and (c) maintain the previous version for a minimum of ninety (90) days after the new version is released.

6.3 Deprecation. REPLR may deprecate API endpoints or features by providing notice through the API documentation and response headers. Deprecated features will continue to function for at least sixty (60) days following deprecation notice.

7. INTELLECTUAL PROPERTY

7.1 REPLR IP. The API, its documentation, and all associated intellectual property remain the exclusive property of REPLR. Nothing in these API Terms grants you any right to REPLR's trademarks, logos, or branding. You shall not use REPLR's marks in a manner that suggests endorsement, sponsorship, or affiliation without prior written consent.

7.2 Your IP. You retain all rights to your Client Applications. REPLR claims no ownership over applications you build using the API.

7.3 Feedback. If you provide feedback, suggestions, or ideas regarding the API, you grant REPLR a perpetual, irrevocable, royalty-free license to use such feedback for any purpose without obligation to you.

8. TERMINATION

8.1 By You. You may stop using the API at any time by revoking your API keys.

8.2 By REPLR. REPLR may suspend or terminate your API access immediately upon notice if you breach these API Terms, the Terms of Service, or any other applicable REPLR policy. REPLR may also suspend API access temporarily to address security vulnerabilities, prevent abuse, or comply with legal obligations.

8.3 Effect. Upon termination, your license to use the API immediately terminates. You must cease all API usage and delete any cached REPLR data obtained through the API within thirty (30) days, except as required by applicable law.

9. DISCLAIMER AND LIMITATION OF LIABILITY

THE API IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, REPLR DISCLAIMS ALL WARRANTIES, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. REPLR'S TOTAL LIABILITY UNDER THESE API TERMS SHALL NOT EXCEED THE FEES PAID BY YOU FOR API ACCESS IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM.

10. CONTACT

For questions about these API Terms or API access, contact us at api@replr.ai or legal@replr.ai.