API Terms of Use

1. These terms and the Terms of Use

These API Terms govern your use of the Orior application programming interface, API keys, webhooks and documentation (together, the "API"). They supplement the Orior Terms of Use and the Privacy Policy, which continue to apply to everything you do through the API. If these API Terms conflict with the Terms of Use, these API Terms control for use of the API. By creating an API key or calling the API, you accept these terms on behalf of yourself and, if applicable, the organisation you represent.

2. Eligibility and API keys

• The API is available to accounts with an active Influencer or Agency plan (paid or gifted). Access ends automatically when the plan ends.
• API keys are confidential credentials. Keep them on your servers; do not embed them in mobile apps, browser code or public repositories.
• You are responsible for all activity and all credits spent through your keys, including by your team members, contractors and your own customers.
• Revoke a key immediately in Dashboard → Developers if you suspect it was exposed. Charges made before revocation remain valid.
• We may disable a key that we reasonably believe is compromised or misused, and will tell you why when we can.

3. Pricing, credits and refunds

• API requests spend the same Orior credits as the app, from the same balance (team members spend the team owner's balance).
• Each API operation costs twice the app's credit price for the same work, rounded up. The price of every model and option is published at GET /v1/models and can be checked before running with POST /v1/quote. The response of every request states the credits charged.
• Generations reserve their price when accepted. If a generation fails or is cancelled before it starts, the reserved credits are returned automatically.
• Social publishing costs 1 credit per destination (3 credits for an X/Twitter post that contains a link). Failed destinations are refunded. Social accounts connected through the API beyond your plan's included number cost 50 credits per account per 30 days; if that fee cannot be charged, posting to the account through the API is paused until it is paid.
• You may set a monthly credit limit on each key. We are not responsible for spend within limits you set or for spend on keys without a limit.
• Credits have no cash value and are governed by the Terms of Use. Prices may change with at least 14 days' notice by email or in the documentation; requests accepted before a change keep their price.

4. Limits and fair use

• Requests are rate-limited per key and the number of jobs running at once is limited per account, as shown in the documentation and at GET /v1/account. Respect 429 responses and the Retry-After header.
• Write requests require an Idempotency-Key. Use a new key for each new request; reusing one returns the first response and never charges twice.
• Do not attempt to bypass limits, for example by creating multiple accounts, rotating keys to multiply limits, or reselling access in a way designed to exceed them.
• We may temporarily throttle traffic that threatens the stability of the service for other users.

5. Acceptable use and your customers

The Acceptable Use rules in the Terms of Use apply to all content generated or published through the API, whether the request comes from you or from your end users. In addition, you must not:

• Upload photos of a real person to create a character, or generate or publish content depicting them, without that person's documented consent.
• Use the API to build a product whose main purpose is producing deepfakes, sexual content, impersonation, political disinformation or harassment.
• Submit media you do not have the rights to use, or remove watermarks, provenance or AI-disclosure information that we or a platform apply.
• Publish to social accounts you do not own or are not authorised to manage, or evade a platform's own rules, including disclosure of AI-generated content.
• Scrape, benchmark for the purpose of building a competing model, or attempt to extract model weights, prompts or provider credentials.

If you offer the API's capabilities to your own customers, you must bind them to terms at least as protective as these, handle their reports of misuse, and pass on to us any notice of infringing content. Our content filters may reject requests; rejected requests are refunded and must not be retried with attempts to circumvent the filter.

6. Social media connections

Social publishing uses our publishing partner. Account connections are made through the platform's own authorisation screen and can be removed at any time with the API, in the app, or at the platform. Each platform's terms apply to what is published. Scheduled posts are published by the partner at the requested time; delivery depends on the platform and is not guaranteed.

7. Data, storage and retention

• Outputs of API requests are stored in your Orior library and remain available at their URLs until you delete them (DELETE /v1/generations/{id}) or delete your account.
• Media uploaded or imported as inputs through the API is deleted after 7 days unless you attach it to a character or product.
• Idempotency records are kept for 24 hours, webhook delivery logs for 30 days and API request logs (method, path, status, timing and key; never request bodies) for 90 days.
• As between you and us, you control the personal data you send through the API. Where your requests contain personal data of others, you are the controller and we process it on your behalf to provide the API, as described in the Privacy Policy. You are responsible for having a lawful basis, including consent for face images.
• We process API inputs with the AI model providers needed to fulfil each request. We do not use your API inputs or outputs to train our own models.

8. Ownership

Ownership of inputs and outputs is as set out in the Terms of Use. We retain all rights in the API, its documentation and the Orior service. You may use the Orior name only to state accurately that your product uses the Orior API.

9. Changes, versioning and availability

• The API is versioned (/v1). We may add fields, endpoints, models and events without notice; build clients that ignore unknown fields.
• We will give at least 30 days' notice before removing or incompatibly changing a documented part of v1, except where needed for security, legal compliance or because a model provider withdraws a model.
• The API is provided on an "as is" and "as available" basis without a service-level commitment. Generation times and model availability depend on third-party providers.

10. Suspension and termination

You may stop using the API at any time by revoking your keys. We may suspend or terminate API access, with notice where practical, if you breach these terms or the Terms of Use, if your use creates security or legal risk, or if your plan ends. Sections 3 (for charges already incurred), 5, 7, 8 and 11 survive termination.

11. Liability and indemnity

The disclaimers and limitations of liability in the Terms of Use apply to the API. To the extent permitted by law, our total liability arising from the API in any 12-month period is limited to the amount you paid us for credits spent through the API in that period. You will indemnify us against third-party claims arising from content you or your end users submit or publish through the API, or from your breach of these terms.

12. Contact

Questions about the API or these terms: support@oriorai.com (subject line "API").