API Terms of Service

These API Terms of Service ("API Terms") govern your use of the Ratio Ready application programming interface (API). These API Terms supplement and are incorporated into the Ratio Ready Terms of Service. In the event of a conflict, these API Terms take precedence with respect to API usage. By accessing or using the Ratio Ready API, you agree to be bound by these API Terms.

1. API Access & Authentication

Access to the Ratio Ready API requires a valid API key or JSON Web Token (JWT). API keys are generated from your account profile page and must be included in the Authorization header of every request as a Bearer token.

• Personal API keys (pk_ prefix) are tied to your individual account. All processing credits are deducted from your account balance.
• Partner API keys (ptr_ prefix) are issued to approved integration partners and are subject to additional partner terms.

You are solely responsible for the security of your API key. Do not embed API keys in client-side code, public repositories, or any location accessible to unauthorized parties. If you believe your key has been compromised, revoke it immediately from your profile page and contact us at [email protected].

2. Rate Limits & Fair Use

API usage is subject to the following rate limits to ensure fair access for all users:

• General API calls: 100 requests per minute per account
• Processing endpoints: 20 requests per minute per account
• Queue capacity: A maximum number of concurrent jobs may be queued. When the queue is full, subsequent requests receive a 429 Too Many Requests response.

Rate-limited responses include a Retry-After header indicating when you may retry. Automated clients should implement exponential backoff when receiving 429 responses.

We reserve the right to adjust rate limits at any time. Abusive usage patterns — including high-frequency polling, deliberate queue flooding, or coordinated overloading — may result in temporary or permanent suspension of API access.

3. Acceptable Use

In addition to the acceptable use terms in our general Terms of Service, the following rules apply specifically to API usage:

• Legitimate automation only: The API is designed for integration with workflow automation platforms (e.g., Make.com, n8n), custom applications, and batch processing scripts. Automated access outside these purposes is prohibited.
• No credential sharing: Each API key is for a single account or integration. You may not share, resell, or sublicense API credentials to third parties.
• No reverse engineering: You may not reverse-engineer, probe, or test the vulnerability of the API infrastructure.
• No scraping: You may not use the API to scrape, index, or aggregate data from the service beyond what is needed for your own processing workflows.
• Error handling: API clients should handle error responses gracefully. Repeatedly sending requests that result in errors (e.g., invalid input, insufficient credits) without corrective action may be treated as abuse.

4. Data Handling

All data handling via the API is subject to our Privacy Policy. Key points specific to API usage:

• Image data: Images uploaded via the API are processed and stored temporarily under the same retention policy as dashboard uploads — approximately 30 minutes for processed files and up to 24 hours for batch ZIP archives.
• No persistent storage: The API does not provide long-term file storage. You are responsible for downloading results before temporary files are deleted.
• SSL required: All API requests must be made over HTTPS. Plaintext HTTP requests are rejected.
• Request/response logging: We log request metadata (endpoint, status code, timestamp) for operational monitoring. We do not log request bodies or image data.

5. Credits & Billing

API processing consumes credits from your account at the same rates as dashboard processing. The per-operation credit costs are available at the Pricing page and programmatically via the GET /v1/pricing/costs endpoint.

• Credits are deducted when a processing job begins. If the job fails due to a system error, credits are automatically refunded.
• Your application should check the user's credit balance before submitting jobs to avoid 402 Payment Required errors.
• Credit purchases must be made through the Ratio Ready dashboard or checkout flow — the API does not provide endpoints for purchasing credits.

6. Availability & Support

We make reasonable efforts to maintain API availability but do not guarantee a specific uptime percentage. The API may be temporarily unavailable due to maintenance, deployments, or infrastructure issues.

API status and known issues are communicated via our support channels. For API-specific questions or integration support, contact us at [email protected].

We may introduce new API versions or deprecate existing endpoints. Where practical, we will provide advance notice of breaking changes. It is your responsibility to update your integrations accordingly.

7. Limitation of Liability

To the maximum extent permitted by applicable law, Ratio Ready shall not be liable for any damages arising from API downtime, rate limiting, data loss during temporary storage expiry, or changes to the API. The limitations of liability set out in our general Terms of Service apply fully to API usage.

The API is provided "as is" without warranties of any kind. We do not warrant that the API will be uninterrupted, error-free, or free of vulnerabilities.

8. Suspension & Termination

We reserve the right to suspend or revoke API access immediately and without notice if:

• Your usage violates these API Terms or the general Terms of Service
• Your usage threatens the stability or security of the service
• Your account is terminated for any reason

You may discontinue API usage at any time by deleting your API key from your profile page. Remaining credits in your account are subject to the standard credit validity and refund policies.

9. Changes to API Terms

We may update these API Terms at any time. Changes will be posted on this page with an updated "Last updated" date. Material changes affecting existing integrations will be communicated via email where possible. Your continued use of the API after changes take effect constitutes acceptance of the revised terms.

10. Contact Us

If you have any questions about these API Terms of Service, please contact us at [email protected].