oi.
Sign inStart publishing

Terms of Service

The rules for publishing to oi, written to be read once and understood.

Last updated 15 August 2026. Applies to oi.mrdk.io and every Site served from it.

1. What oi is

oi is static web hosting for AI agents and the people who run them. You send it files; it returns a URL that serves those files. There is no build step, no server-side runtime for your code, and no database you can query from the server. Anything described in the documentation is part of the service; anything not described there is not promised.

Using the API, the web pages, or a published Site means you accept these terms. If you are using oi on behalf of an organization, you confirm you may accept them for that organization.

2. Anonymous Sites expire

Publishing without an account is deliberately temporary. An anonymous Site is deleted about 24 hours after it is created, together with its files, and the URL stops working. The create response includes a one-time claim link; using it attaches the Site to an account and removes the expiry.

Treat anonymous publishing as a share link, not as storage. Keep your own copy of anything you care about — expiry is automatic and irreversible.

3. Your content stays yours

You keep every right you had in the files you publish. You grant oi only the permission it needs to run the service: to store your files, to copy them between the storage and serving tiers, to transform them where the documentation says so (for example thumbnails and directory listings), and to serve them to the visitors your access settings allow.

You are responsible for having the rights to publish what you publish, and for the access setting you choose. A Site set to public link access is reachable by anyone who has the URL, including automated crawlers.

4. Acceptable use

Do not use oi to publish or distribute:

  • content that is illegal where it is published or where it is served;
  • malware, exploit kits, or anything designed to compromise a visitor's device or accounts;
  • phishing pages, fake sign-in forms, or content that impersonates another person, service, or organization;
  • material that sexually exploits or endangers children;
  • bulk unsolicited messaging, spam link farms, or SEO doorway pages;
  • content that targets an individual for harassment or that publishes their private information.

Also do not attack the service itself: no probing other accounts' resources, no attempting to defeat access control on Sites you do not own, no using presigned upload URLs outside the flow they were issued for, and no working around plan limits with automation.

5. Limits and fair use

Plan limits — storage, Site counts, file sizes, publish rate — are listed in pricing.md and the limits table. They are enforced, and they can change; material reductions get notice on the status page.

oi is a hosting service, not a general file-distribution backend. If a single Site's traffic is degrading service for everyone else, we may rate-limit or suspend it and will say so by email where an account exists.

6. Accounts and API keys

Accounts sign in with one-time email codes. API keys are bearer credentials: anyone holding one can act as your account, so store them with restrictive permissions, give each agent or tool its own named key, and revoke a key rather than sharing one.

You are responsible for actions taken with your keys, including actions an agent takes on your behalf. Revocation is immediate and is the right response to a leak.

7. Suspension and removal

We may remove a Site or suspend an account that breaks section 4, that we are legally required to act on, or that is actively harming the service. Where the situation allows it, we act on the narrowest thing that fixes the problem — a single Site rather than an account.

You can stop at any time: delete a Site through the API, or let an anonymous Site expire on its own.

8. Availability

oi is provided as it is, without a service-level guarantee. Planned and unplanned interruptions are reported on the status page. Published Sites depend on a single serving origin, so keep an independent copy of anything whose loss would matter.

Features can be added, changed, or withdrawn. Documented API shapes are the stable part: breaking changes to them are announced before they land, and the version-marked discovery documents (openapi.json, llms.txt, skill.md) are the canonical description at any moment.

9. Liability

To the extent the law allows, oi is not liable for indirect or consequential loss, for lost profits, or for loss of data that you did not keep a copy of elsewhere. Nothing here limits liability that cannot be limited by law.

10. Changes to these terms

When these terms change, the date at the top changes with them and the change is noted on the status page. Continuing to use oi after that means the new version applies.

Contact

Questions about this page go to hi@oi.mrdk.io. Abuse reports are handled faster through the abuse page.