Ora
How it works Financial model Actions & workflows Console
Sign in Sign up

Terms of Service

Last updated October 30, 2026

These Terms of Service ("Terms") govern your use of Ora, including the website at oramodel.com, the console, the Ora API and related documentation (together, the "Service"). The Service is provided by [Company legal name] ("Ora", "we", "us"). By creating an account, creating an API key or otherwise using the Service, you agree to these Terms. If you use the Service on behalf of an organization, you agree to them on its behalf and confirm that you are authorized to do so; "you" then means that organization as well.

Contents

  1. Who may use the Service
  2. Accounts and organizations
  3. API keys and security
  4. Acceptable use
  5. Prepaid credits, pricing and billing
  6. Your content and how we use it
  7. Outputs are probabilities, not advice
  8. Third-party destinations
  9. Availability and changes to the Service
  10. Suspension and termination
  11. Intellectual property
  12. Disclaimers
  13. Limitation of liability
  14. Indemnity
  15. Changes to these Terms
  16. Governing law and disputes
  17. General
  18. Contact

1. Who may use the Service

You must be at least 18 years old and able to form a binding contract. You may not use the Service if you are barred from doing so under applicable law, including export control and sanctions laws, or if we have previously terminated your account.

2. Accounts and organizations

You need an account to use the console and the API. Give us accurate information and keep it up to date. You are responsible for everything that happens under your account, so keep your password private and tell us promptly at [legal@oramodel.com] if you suspect unauthorized access.

API keys, usage, credits, connections, saved queries and workflows belong to an organization. Owners and admins of an organization can invite and remove members, change organization settings and create or revoke keys. The organization is responsible for what its members do in it.

3. API keys and security

An API key is shown once, when it is created; we store only a one-way hash of it. Treat keys like passwords:

  • Keep them out of client-side code, public repositories and shared documents.
  • Give each application its own key, and revoke a key in the console as soon as you no longer need it or suspect it has leaked.
  • Requests made with your keys are your responsibility and are billed to the organization that owns them, whether or not you authorized them, until the key is revoked.

Do not attempt to access accounts, keys or data that are not yours, or to probe, scan or test the vulnerability of the Service without our written permission. If you find a security issue, please report it to [legal@oramodel.com].

4. Acceptable use

You agree not to, and not to let anyone else:

  • use the Service in violation of any law or regulation, including securities, consumer protection, privacy and anti-spam laws, or to infringe anyone's rights;
  • send content you do not have the right to send, or personal data you are not permitted to process;
  • use outputs as the sole basis for decisions with legal or similarly significant effects on individuals (such as credit, employment, housing or insurance decisions) without appropriate human review;
  • evade or interfere with rate limits, usage metering, billing or security controls, or overload the Service;
  • copy, reverse engineer or attempt to extract the models, their weights or training data, including by systematically querying the Service to build a competing model;
  • resell, sublicense or provide the Service to third parties as a standalone product without our written agreement;
  • use actions, webhooks or workflows to send spam or unsolicited messages, or to target systems you do not own or have permission to use.

We may investigate suspected violations and take the steps described in Suspension and termination.

5. Prepaid credits, pricing and billing

The Service is billed per input token from prepaid credits held by your organization. The price in force is shown in the console, and usage and the remaining balance are visible there. Usage is charged at the price in force when the request is made.

  • Credits. Credits are purchased in advance or granted by us (for example as a trial or promotion). Granted credits may carry an expiry date, which is shown with the grant. Credits have no cash value, cannot be transferred between organizations unless we agree, and are used before any other payment method.
  • Running out. When an organization's balance is used up, we may stop serving its requests until more credits are added.
  • Price changes. We may change prices. Changes apply to usage after the change takes effect, and we will announce them in the console in advance.
  • Refunds. Purchased credits are non-refundable, except where required by law or where we determine that you were charged in error. Granted credits are never refundable. If we terminate your account for convenience (not for a breach of these Terms), we will refund unused purchased credits.
  • Taxes. Prices exclude taxes unless stated otherwise. You are responsible for applicable taxes other than taxes on our income.
  • Payments. Until card payments are available in the console, credits are arranged with us directly. Card payments will be handled by a third-party payment processor; we will not store full card numbers.

6. Your content and how we use it

"Your Content" means what you send to or store in the Service: the state and questions in requests, and the saved queries, workflows, watchlists, actions and connections you create. You keep all rights in Your Content. You give us a limited licence to host, process and transmit it only as needed to provide, secure and support the Service for you, and to comply with law.

Requests. The content of API and Playground requests is processed to produce answers and is not stored, unless you save it (for example as a saved query or workflow) or your organization turns on model improvement.

Model improvement. Each organization has a "Help improve the model" setting, which is off by default and can be changed by its owners and admins. While it is on, the organization allows us to read and analyze its inputs and outputs to understand where the model is weak and to improve it. Turning it off stops this for future requests.

Service data. We collect metadata about your use of the Service, such as the model used, token counts, status codes and timings. We use it to operate, bill, secure and improve the Service, and we may publish statistics about the Service only in aggregated form that does not identify you or Your Content.

Feedback. If you send us suggestions or feedback, we may use them without obligation to you.

Our handling of personal data is described in the Privacy Policy.

7. Outputs are probabilities, not advice

Answers from the Service are model estimates: probabilities, choices and scores calculated from the state you send or, for the financial model, from market data we obtain from third-party sources. Outputs can be wrong, incomplete or out of date, and similar requests can give different answers as models are updated.

Market data and answers are provided for information only. Nothing in the Service is investment, financial, legal, tax or other professional advice, a recommendation or solicitation to buy or sell any security or other instrument, or a guarantee of any future price, return or outcome. We are not a broker-dealer or an investment adviser. Past data does not predict future results.

You are solely responsible for how you use outputs, including any trades, orders or automated actions your systems take based on them. Evaluate outputs for your use case and keep appropriate human oversight for consequential decisions.

8. Third-party destinations

Actions and workflows can deliver messages to destinations you configure, such as Slack incoming webhooks and HTTPS webhooks on your own systems. When you configure a destination, you instruct us to send the configured content to it, and you confirm you are allowed to. Destinations are operated by third parties under their own terms and privacy policies; we are not responsible for them, for what they do with delivered content, or for deliveries that fail because of them. Keep webhook URLs and signing secrets confidential; we store them encrypted.

9. Availability and changes to the Service

We work to keep the Service available and fast, but we do not promise uninterrupted or error-free operation and, unless we have signed a separate agreement with you, we offer no service-level commitment. We may perform maintenance, apply rate limits and change, add or remove features.

Model names such as ora1 are aliases that move to newer versions; each response names the exact version that answered. Features described as beta, preview or "coming soon" may change or be withdrawn and are provided as is. If we remove a material feature you use, we will try to give reasonable notice.

10. Suspension and termination

You may stop using the Service at any time and ask us to close your account by writing to [legal@oramodel.com].

We may suspend or restrict your access, disable API keys or connections, or terminate your account if you breach these Terms, if your use creates a security, legal or operational risk to the Service or others, if payment fails, or if required by law. Where reasonable, we will tell you in advance and give you a chance to fix the problem. We may also terminate for convenience on 30 days' notice.

On termination your right to use the Service ends, keys stop working, and we delete account data as described in the Privacy Policy. Sections that by their nature should survive (including billing obligations, outputs, disclaimers, limitation of liability, indemnity and governing law) survive termination.

11. Intellectual property

The Service, including its models, software, documentation and branding, is owned by us or our licensors and is protected by intellectual property laws. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable right to use the Service for your internal business purposes during your subscription. Code samples in the documentation and console may be used and adapted freely in your applications. No other rights are granted.

12. Disclaimers

To the fullest extent permitted by law, the Service and all outputs are provided "as is" and "as available", without warranties of any kind, whether express, implied or statutory, including warranties of merchantability, fitness for a particular purpose, accuracy, title and non-infringement.

13. Limitation of liability

To the fullest extent permitted by law, neither party will be liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, trading losses or data, even if advised of the possibility. Our total liability arising out of or relating to these Terms or the Service will not exceed the greater of (a) the amounts you paid us for the Service in the 12 months before the event giving rise to the claim and (b) US$100.

These limits do not apply to your payment obligations, your indemnity obligations or your breach of Acceptable use, and do not limit liability that cannot be limited by law.

14. Indemnity

You will defend and indemnify us and our affiliates, officers and employees against third-party claims, and the resulting losses and reasonable costs, arising from Your Content, your use of outputs (including trading or automated actions), your breach of these Terms or your violation of law or of anyone's rights.

15. Changes to these Terms

We may update these Terms. We will post the new version here with a new "Last updated" date and, for material changes, notify account owners by email or in the console at least 15 days before they take effect. Changes do not apply retroactively. If you keep using the Service after changes take effect, you accept them; if you do not agree, stop using the Service.

16. Governing law and disputes

These Terms are governed by the laws of [Governing law], without regard to conflict-of-laws rules. The courts of [Venue] have exclusive jurisdiction over any dispute arising from these Terms or the Service, except that either party may seek injunctive relief in any competent court. Before filing a claim, each party agrees to try to resolve the dispute informally by contacting the other for at least 30 days.

17. General

These Terms, together with the Privacy Policy and any order form or agreement we sign with you, are the entire agreement between you and us about the Service and replace earlier understandings. If a provision is unenforceable, the rest remains in effect. Our failure to enforce a provision is not a waiver. You may not assign these Terms without our consent; we may assign them in a merger, acquisition or sale of assets. Neither party is liable for delays caused by events beyond its reasonable control. Notices to you may be sent to your account email or shown in the console.

18. Contact

[Company legal name]
[Address]
Email: [legal@oramodel.com]

Ora © 2026 Ora
Terms Privacy Sign in