Legal
Terms of Service
Last updated
1This agreement
These Terms of Service are a contract between you and Octri, LLC (“Octri”, “we”, “us”), a limited liability company formed in Delaware, United States, with its registered office at [Registered address to be confirmed before launch]. They govern your use of the Octri dashboard, the documentation sites we host for you, the SDKs and MCP servers we generate, the monitoring service, the CLI, and our public API.
You accept these terms by creating an account or by using the service. If you accept on behalf of a company, you confirm you are authorised to bind it, and “you” means that company.
You must be at least 16 years old to hold an account. Where local law sets a higher age for entering a contract without a guardian, that age applies instead.
Two documents form part of these terms: the Fair Use Policy, which sets out how plan allowances and rate limits behave, and the Privacy Policy, which explains how we handle personal data. Where an Enterprise order form or a signed agreement conflicts with these terms, that document wins.
2What Octri provides
You give us an OpenAPI description of your API. From it, Octri can:
- generate and host a documentation site, served on an
octri.devsubdomain or on a custom domain you control, with public, password, or SSO access; - generate client SDKs in TypeScript, Python, Go, Java, Ruby, PHP, Rust, Swift, Kotlin and Dart, and, on your instruction, publish them to package registries or to a Git repository you connect;
- generate an MCP server so agents can call your API;
- answer questions from your documentation using retrieval-augmented AI (“Ask the docs”);
- collect errors, logs, traces, performance data and uptime checks from your API through our monitoring service;
- keep your spec in step with a connected GitHub repository, and let your team author docs, guides, components and changelogs in the dashboard.
Which of these you get depends on your plan. Feature availability by plan is published on our pricing page and enforced in the product. We may add, change or remove features; where a change materially reduces what your paid plan includes, we will tell you before it takes effect and you may cancel under section 6.
Features labelled beta, preview or experimental are provided for evaluation. They can change or be withdrawn at any time and are excluded from any availability commitment.
3Accounts and organisations
Your account belongs to a person. Your projects, billing and data belong to an organisation. An account can belong to several organisations and switch between them.
Each organisation has an owner. The owner and members with the right permissions can invite people, set roles, grant per-project access, and remove members. Anything a member does with valid credentials is treated as done by the organisation, so choose who you invite and keep roles current.
You are responsible for keeping credentials secret. This includes passwords, two-factor codes and recovery codes, API keys, and the ingest and registry credentials you connect. We offer authenticator-app two-factor authentication on every plan and SAML single sign-on on Enterprise, and we recommend you turn one of them on. Tell us at founders@octri.dev as soon as you suspect an account has been compromised.
You may not share one account between several people, or resell access to the dashboard as if it were your own product. Building a product on top of the docs and SDKs we generate for you is exactly what the service is for and is not resale.
4Plans, allowances and AI credits
We offer a Free plan and paid plans (Starter, Growth, Business and Enterprise). Each plan sets a limit on projects, API endpoints, monitoring data and AI credits, and bundles a number of SDK languages. The current figures are on the pricing page and in the Fair Use Policy.
Paid plans start at $49 per month and run to $249 per month for Business. Every SDK language beyond your plan’s bundle is a flat $50 per month, added to your subscription and prorated when you add it mid-cycle. Annual billing takes 15% off the base package price; language add-ons bill at twelve times the monthly rate with no discount. Enterprise pricing is agreed in an order form.
AI features are metered in credits. Generating documentation for an endpoint and answering an Ask-the-docs question each cost credits at the rates published on the pricing page. Paid plans receive a credit allowance that is restored at the start of each billing cycle and does not roll over. The Free plan receives a one-time trial grant that is not refilled.
You can buy credit packs at any time. Purchased credits do not expire and are consumed only after your plan allowance is exhausted. You can also enable auto-refill, which authorises us to charge your saved payment method for a chosen pack on a schedule or when your purchased balance falls below a threshold you set. Auto-refill turns itself off after repeated failed charges. Credits are a prepaid metering unit, not currency: they have no cash value, cannot be transferred between organisations, and are not refundable once consumed.
Running out of credits stops the AI features. It does not take down your documentation, your SDKs or your monitoring.
5Payment
Paddle.com Market Ltd is our reseller and merchant of record. When you buy a subscription or a credit pack, your contract of sale is with Paddle, and Paddle’s buyer terms apply to that transaction alongside these terms. Paddle handles payment collection, invoicing, sales tax and VAT. Your receipts come from Paddle, and card details are held by Paddle, never by us.
Subscriptions renew automatically at the end of each billing period until cancelled. By subscribing you authorise recurring charges for the base plan, for any language add-ons on your subscription, and for any auto-refill you have enabled, at the prices in force when each charge is taken.
Prices are exclusive of tax unless stated otherwise at checkout. We may change prices for a renewal term with at least 30 days’ notice by email; the new price takes effect at your next renewal, and you can cancel before then.
If a payment fails, we retry it and email you. While an account is past due we may restrict paid features until the balance is settled. If it stays unpaid, we may downgrade the organisation to the Free plan or suspend it under section 12. Where a payment is reversed by a chargeback or refund, we reverse the entitlement it bought, including any unused credits it granted.
6Cancellation and refunds
You can cancel at any time from the billing portal. Cancellation stops the next renewal. Your plan stays active until the end of the period you have already paid for, and then the organisation moves to the Free plan.
We do not give refunds for unused time. That applies to subscriptions, language add-ons and credit packs, and to mid-cycle downgrades and language removals, which take effect at the end of the current period rather than immediately. Nothing here limits rights you have under consumer law that cannot be waived. Consumers in the UK and the EU keep their statutory cancellation rights, and any refund claim on that basis is handled by Paddle as merchant of record.
If you drop to a plan with lower limits, or to Free, anything above the new limits stops working: extra projects and endpoints become read-only, SDK languages no longer build, and the credit allowance changes to the new plan’s. Purchased credits survive a downgrade.
You can delete a project from its settings, which removes its documentation site, specs, analytics and generated artifacts immediately and cannot be undone. Closing an organisation ends your access; everything we hold for it, monitoring data included, is erased within 30 days, as set out in the DPA. Take an export first if you need one. Deletion does not entitle you to a refund of the current period.
7Your content
Your content is yours. That covers your OpenAPI specs, the documentation and guides you write or generate, custom components and code, logos and branding, the data your application sends to monitoring, and everything else you upload or connect.
To run the service, you grant us a worldwide, non-exclusive, royalty-free licence to host, copy, transmit, index, embed, transform and display your content, for as long as you keep it on the platform and only for the purposes below:
- operating the features you have turned on, including AI generation and search;
- publishing your documentation to the domain you configured, and publishing generated SDKs where you have asked us to publish them;
- backups, security, debugging and support you have asked us for.
The licence ends when you delete the content or the organisation, except for backup copies that expire on their normal cycle and for anything you have deliberately published to a public registry or public documentation site, which we cannot recall from third parties.
You confirm you have the rights to everything you upload, and that publishing it through Octri does not infringe anyone else’s rights or break any law.
Do not put secrets in your spec. Live API keys, tokens, passwords and personal data in an OpenAPI description end up in generated documentation, and in published SDKs, where they may become public.
8AI-generated output
Documentation prose, examples, error guides and chat answers are produced by large language models. As between you and us, the output belongs to you and you may use it however you like, subject to these terms.
AI output can be wrong. It can describe behaviour your API does not have, invent a parameter, or answer a support question incorrectly. It is a draft for you to review, not a statement of fact about your API, and you are responsible for what you publish. We give no warranty that generated content is accurate, complete or fit for any purpose.
Similar prompts produce similar output, so we cannot promise your generated text is unique or that comparable text will not be generated for someone else.
To generate output we send the relevant parts of your spec and documentation to the model providers listed on our subprocessors page. We do not use your content to train our own models, and we do not permit our providers to train on it: the providers we use process API traffic without training on it under their commercial terms.
9Generated SDKs and publishing
The SDKs, MCP servers and code samples we generate from your spec are yours to use, modify, distribute and license on your own terms, including commercially. We claim no ownership of them and no royalty. We keep ownership of the generator itself, its templates and the platform.
If you connect a package registry (npm, PyPI, Maven Central, crates.io, RubyGems, Packagist, pub.dev) or a Git repository, publishing happens under your credentials and in your name. You decide what gets published and when, you are responsible for the result, and you must follow each registry’s own rules. Auto-publish, where your plan includes it, publishes on the triggers you configure. You can disconnect a registry at any time.
We do not verify that a generated SDK is correct, secure or suitable for production. Review it, test it and take responsibility for it before you ship it to your users.
10Acceptable use
You may not use Octri to:
- break the law, infringe intellectual property, or breach someone’s privacy;
- publish or host malware, phishing pages, illegal content, or documentation for a service whose purpose is fraud or unauthorised access to systems;
- attack the platform: probing, scanning, load testing without written permission, denial of service, or attempting to reach data belonging to another organisation;
- reverse engineer the platform, scrape it at scale, or use it to build a competing documentation or SDK-generation product;
- work around plan limits, metering or billing, including by spreading one team’s work across multiple free organisations;
- resell, sublicense or provide the dashboard to third parties as a service of your own.
Allowances, rate limits, and what happens when you exceed them are set out in the Fair Use Policy. Security researchers acting under our disclosure policy are not in breach of the testing rules above.
11Third-party services
Octri connects to services you choose: GitHub, package registries, your DNS provider for custom domains, and your own applications for monitoring. Your use of those services is governed by their terms, not ours. We are not responsible for their availability, their pricing, or what they do with data you send them directly.
When you install our GitHub App or link a registry account, you grant us access scoped to what the feature needs. You can revoke that access from the provider at any time; the feature stops working when you do.
Our own vendors, the ones that process data on our behalf, are listed on the subprocessors page.
12Availability and support
We target 99.9% monthly availability for hosted documentation and the API on paid plans. It is a target, not a contractual service level: outside a signed Enterprise SLA it carries no service credits. Planned maintenance, problems at a third party, and anything caused by your own configuration are excluded.
The Free plan is provided without any availability commitment and may be rate limited or changed at short notice.
Support channels by plan are described on the support page. We do not publish response times outside an Enterprise agreement.
13Suspension and termination
We may suspend or terminate an account or an organisation if:
- an invoice stays unpaid after we have contacted you;
- section 9 or the Fair Use Policy is being breached;
- usage is threatening the stability or security of the platform or of other customers;
- we are required to by law, or by a valid legal request.
Except where the problem is urgent, illegal, or a security risk, we will contact you first and give you a chance to fix it. Where we can suspend narrowly, for example throttling one feature, we do that instead of cutting off the account.
You may terminate at any time by cancelling and deleting your organisation. After termination we delete your content on our normal schedule, described in the Privacy Policy. Export anything you need first.
Sections covering your content licence for already-published material, intellectual property, disclaimers, liability, indemnity and governing law survive termination.
14Our intellectual property
The platform, the generators, the templates, the dashboard, the documentation renderer, our brand and the Octri name are ours or our licensors’. These terms grant you a limited, non-exclusive, non-transferable right to use the service while your account is in good standing, and nothing more.
If you send us feedback, ideas or feature requests, we may use them without restriction or payment. You do not have to send us feedback.
15Confidentiality
Each of us may learn non-public information about the other. We will not disclose your non-public content or configuration except to the vendors listed on our subprocessors page, to staff who need it to run the service or answer your support request, or where the law requires it. Where we are legally compelled to disclose your data, we will tell you unless we are prohibited from doing so.
16Disclaimer
The service is provided “as is” and “as available”. To the fullest extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing.
We do not warrant that the service will be uninterrupted or error-free, that generated documentation or SDKs will be accurate or defect-free, or that AI answers will be correct.
Some jurisdictions do not allow these exclusions. Where that is the case, the exclusions apply to the maximum extent permitted, and your non-waivable statutory rights are unaffected.
17Limitation of liability
To the fullest extent the law allows, neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost data or loss of goodwill, even if advised such loss was possible.
Our total aggregate liability arising out of or relating to the service in any twelve-month period is limited to the greater of the fees you paid us in the twelve months before the event giving rise to the claim, or US$100.
Nothing excludes liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot be excluded by law.
18Indemnity
You will defend and indemnify Octri against third-party claims arising from your content, from what you publish through the service, from your breach of these terms or of the Fair Use Policy, or from your infringement of someone else’s rights. We will tell you promptly about any such claim and let you control the defence, provided any settlement that admits fault or imposes an obligation on us needs our agreement.
19Changes to these terms
We may update these terms. For material changes we will email account owners and post the new version here at least 30 days before it takes effect, unless a change is required sooner by law or to address a security risk. Continuing to use the service after a change takes effect means you accept it. If you do not, cancel before the effective date. Every version carries the date it was last updated.
20Governing law and disputes
These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules. The state and federal courts located in Delaware have exclusive jurisdiction, and both parties submit to their venue.
If you are a consumer resident in the EU, the UK or another jurisdiction whose law gives you the right to bring proceedings locally and to the protection of your local mandatory consumer-protection rules, that right is unaffected by this section.
Before filing anything, email founders@octri.dev. Most disputes are quicker to resolve that way.
21General
These terms, together with the Fair Use Policy, the Privacy Policy and any order form, are the entire agreement between us on this subject and replace anything said earlier.
If a provision is held unenforceable, the rest stays in force and that provision is narrowed to the minimum extent needed to make it enforceable. Not enforcing a term is not a waiver of it.
You may not assign this agreement without our written consent. We may assign it to an affiliate or in connection with a merger, acquisition or sale of assets, on notice to you.
Neither party is liable for delay or failure caused by events outside its reasonable control.
We send notices to the email address on the account owner’s profile. Keep it current. Send notices to us at founders@octri.dev.
22Contact
Octri, LLC
[Registered address to be confirmed before launch]
- Legal: founders@octri.dev
- Support: support@octri.dev
- Privacy: support@octri.dev
- Security: founders@octri.dev