Terms of service
Last updated:
These terms govern your use of Oimo: the website at oimo.com, the web app, the API, webhooks, the command-line tool (CLI) and usage connectors (together, the "Service"). The Service is operated by [Oimo legal entity name] ("Oimo", "we", "us"), [registered address].
By using the Service you agree to these terms. If you use it for a company or other organization, you agree on its behalf and confirm that you may do so; "you" then means that organization too. Our Privacy policy explains how we handle personal data, and our vendor-data disclaimer explains the limits of the price and terms data. Both are part of these terms.
1. A free public beta
Oimo is in public beta. It is free during the beta. We will announce pricing before it applies to you, at least [number] days in advance Decision needed, and nothing you use today becomes paid without that notice.
During the beta:
- there is no service level agreement: the Service may be slow, unavailable or interrupted, and we do not promise any uptime;
- features, limits, the API and webhook payloads may change. We document API and payload changes in the changelog, and a breaking change to a webhook payload gets a new payload version;
- we may suspend or end the beta, or any part of it, with [number] days' notice where we reasonably can Decision needed;
- features marked "Beta" in the app, such as usage connectors, are earlier still and may change or be withdrawn without notice.
2. Accounts and workspaces
You must be at least [minimum age] years old to use the Service. You sign in through our authentication provider (see the Privacy policy); keep your sign-in details secure and tell us at support@oimo.com if you believe someone else has used your account.
Your webhooks, API keys, connectors and teammates belong to a workspace. The person who creates a workspace becomes its admin. Admins invite and remove members and change their roles; every member can manage webhooks and API keys. You are responsible for what happens under your account, your workspace's API keys and the people you invite.
Limits apply: you can create a workspace only while you belong to fewer than 3, and a workspace can send 20 invitations in any 24 hours. Oimo staff can open any workspace to support you and to keep the Service running. In the app, staff view a workspace read-only and cannot see its signing secrets or connector credentials.
3. API keys and rate limits
API keys are read-only and belong to a workspace (up to 20 per workspace). Keep them secret: do not put them in browser code, public repositories or support emails. If a key is exposed, delete it in the app.
Requests are rate-limited: 5 requests a second (bursts of 20) per API key or signed-in user, 10 a second (bursts of 40) per workspace, and 2 a second (bursts of 5) for price history. The current limits are always on Limits and pricing. We may change limits; we may also slow down or block traffic that threatens the Service.
4. Webhooks
A webhook sends signed events to an https address you register (up to 20 per workspace). Only register addresses you control or are allowed to use. You should verify each event's signature and use its id to ignore duplicates.
- Your endpoint has 5 seconds to answer with a 2xx status. A failed delivery is retried after 5 minutes, 30 minutes, 2 hours, 8 hours and 24 hours (6 attempts in all), then marked failed.
- A webhook is paused after 5 delivery attempts in a row have failed over at least 24 hours, until someone in your workspace resumes it.
- For each attempt we keep the time, the status, any error and the first 1,024 characters of your endpoint's response body, so you can see them under Deliveries, for 30 days after the delivery's last attempt. Do not return secrets or personal data in webhook responses.
- Delivery is best effort: events can arrive late, more than once or, rarely, not at all. Do not rely on webhooks alone for anything critical.
5. Usage connectors (Beta)
Workspace admins can connect accounts at AI and cloud providers by giving us credentials (for example an admin API key or service-account key) and account identifiers. By connecting an account you confirm that you are allowed to give us access to it and to its usage and cost reports. We use the credentials only to check access and to collect your organization's usage and cost reports from that provider, as described in the Privacy policy. Collected usage is not shown in the app yet.
For Google Cloud (your Cloud Billing export in BigQuery) and Snowflake, checking access and collecting usage run queries inside your own project or warehouse. Those queries use your compute or credits, which your provider may bill you for, and leave job and query history in your account.
You can pause or disconnect a connector at any time. Disconnecting schedules deletion of the stored credentials; usage already collected is kept until your workspace is deleted, or until you ask us to delete it Decision needed. Your agreements with the provider still apply to you, including any rules about sharing credentials with third parties.
6. Acceptable use
Do not:
- exceed or get around rate limits or other limits, for example with several accounts, workspaces or keys, or scrape the website or API beyond them;
- resell, redistribute or publish the data in bulk, or use it to build or feed a competing price dataset or service (see section 7 for what you may do) Decision needed;
- misuse webhooks: point them at systems you do not control or may not use, use them to probe private networks, internal addresses or cloud metadata services (server-side request forgery), or to send unwanted traffic to anyone;
- probe, scan or test the security of the Service without our written permission. If you find a vulnerability, report it to support@oimo.com;
- interfere with the Service or other customers, or upload malware or harmful code;
- reverse engineer the Service, except where the law allows it;
- share your sign-in with others (invite them to your workspace instead), or impersonate anyone;
- present the data as a vendor's official price, quote or terms, or as endorsed by a vendor or by us;
- use the Service in breach of any law, sanctions or export rules.
7. Our data and your content
The Oimo data. The prices, price history, terms-of-service records, comparisons, alias groups and status information in the Service are compiled by Oimo from vendors' public sources (see the vendor-data disclaimer). While you use the Service we give you a limited, non-exclusive, non-transferable right to access and use this data for your own internal business purposes, including in your own systems through the API and webhooks. Whether and how customers may show the data publicly (for example with attribution) is not settled yet. Decision needed Everything else about the Service, including its software and design, stays ours.
Your content. What you put into the Service stays yours: workspace and webhook settings, API key names, provider requests, alias proposals, saved views and connector credentials and usage. You let us host, copy and process it only to provide, secure and support the Service. Alias groups are shared by every customer: if staff approve an alias proposal of yours, the resulting group is published to everyone, without your name.
Feedback. If you send us ideas or feedback, we may use them without any obligation to you.
8. Vendor data
The price and terms data come from vendors' public pages and APIs. They can be wrong, late or incomplete, and the vendors are not affiliated with us. Always check with the vendor before you buy or rely on a price or term. The vendor-data disclaimer sets this out in full.
9. Suspension and termination
You can stop using the Service at any time. Admins can delete webhooks and API keys and disconnect connectors in the app. To delete your account or a workspace and its data, email support@oimo.com from the account's address; there is no self-service deletion yet. We delete it within [number] days of the request Decision needed, as the Privacy policy describes.
We may suspend or close your access, or a workspace, if you breach these terms, if your use puts the Service, other customers or vendors at risk, if the law requires it, or when we end the beta. Where we reasonably can, we will tell you first and give you a chance to fix the problem. When access ends, these terms stop applying to future use, but sections 7 (as to our rights), 10, 11, 12 and 14 continue.
10. Disclaimers
The Service and the data are provided "as is" and "as available", during the beta and after. To the extent the law allows, we disclaim all warranties, express or implied, including warranties of accuracy, completeness, timeliness, merchantability, fitness for a particular purpose and non-infringement. We do not promise that the Service will be uninterrupted or error-free, that every vendor change will be detected, or that webhooks will always be delivered.
11. Limitation of liability
To the extent the law allows, Oimo is not liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, savings or data, or for decisions you make based on the data, even if we were told they were possible. Our total liability for all claims about the Service is limited to the greater of the amount you paid us for the Service in the 12 months before the claim and [amount] Decision needed. Some places do not allow some of these limits; there, they apply as far as the law permits.
12. Your responsibility to us
If a third party makes a claim against Oimo because of your content, your webhook endpoints, accounts you connected or your breach of these terms, you will cover our reasonable costs of that claim, to the extent the law allows. Decision needed
13. Changes to these terms
We may update these terms. We will post the new version here and change the "Last updated" date. If a change materially reduces your rights, we will tell you by email or in the app at least [number] days before it applies Decision needed. If you keep using the Service after a change applies, the new terms apply to you; if you do not agree, stop using the Service.
14. Governing law and disputes
These terms are governed by the laws of [governing law], without regard to its conflict-of-laws rules. Disputes will be resolved in the courts of [venue], except where the law gives you the right to bring a claim elsewhere.
15. General
These terms, with the Privacy policy and the vendor-data disclaimer, are the whole agreement between you and Oimo about the Service. If a part of them cannot be enforced, the rest still applies. Not enforcing a right is not a waiver of it. You may not transfer your rights under these terms without our consent; we may transfer ours to a successor of our business. Neither of us is liable for delays caused by events outside reasonable control.
16. Contact
Questions about these terms: support@oimo.com. Postal address: [Oimo legal entity name], [registered address].
Open questions for review
Not part of the text: what the draft could not settle from the code. Placeholders look like [this]; sentences waiting for a decision are marked Decision needed.
- Legal entity name. The repository names no operator of Oimo. "Oimo AI, Inc." appears only as the GitHub enterprise name (
infra/docs/github-sso.md); "Oimo Inc., a Delaware corporation" appears only in sample contract text (services/relay/src/contracts/samples.ts), which is not authoritative. - Registered address for the contact and postal notices.
- Governing law and venue (section 14).
- Minimum age, and whether the Service is for business use only (which affects consumer-law terms).
- Notice periods: before pricing applies (section 1), before ending the beta (section 1), before material changes to these terms (section 13).
- Liability cap amount for a free service (section 11), and whether to include the indemnity (section 12).
- What customers may do with the data: internal use only, or also public display with attribution; how to define "in bulk" for the redistribution ban (sections 6 and 7).
- Retention of collected usage after a connector is disconnected (section 5): today it is kept; the automated deletion of a workspace's usage data is not built yet (
services/infrarates-usage/README.md). - Deletion deadline after an account or workspace deletion request (section 9); there is no self-service deletion.
- Acceptance at sign-up. Sign-up happens on the authentication provider's hosted page, whose Terms of service and Privacy policy links are not set (WorkOS Production branding:
authkitSignUpTermsOfServiceUrlandauthkitSignUpPrivacyPolicyUrlare empty). Decide whether sign-up should require accepting these terms once final, and set those links then.