Limits & Fair Use

Octarine Share is designed for sharing personal notes and running modest automations around them. It is not a general-purpose object store, CDN, backup service, or bulk publishing platform.

Current Technical Limits

Resource	Current limit
Session token	Expires after 2 hours
Individual image	5 MiB
Image formats	PNG, JPEG, GIF, and WebP
Version history	Up to 10 recent snapshots per publication
Public note and image cache	Successful reads may be cached for up to 60 seconds
Per-account image storage	1 GB
All API requests	600 per minute per source IP
Authentication	10 per minute per source IP
Authenticated mutations	60 per minute per user

The 25 MB request allowance is for multipart image uploads. JSON and raw Markdown requests are limited to 2 MB. The stored-note limit is kept below the database platform's 2 MB row limit.

Rate limits are protective controls, not precise usage meters. Cloudflare applies these counters locally at each network location and may allow a small burst while counters converge. A request can be subject to more than one limit; for example, authentication counts toward both the all-API and authentication limits.

An expired publication becomes unavailable from the note and image APIs, but remains visible in your published-notes list. Its image bytes still use storage until the publication is unpublished. Content that a reader already downloaded or cached cannot be recalled.

What Fair Use Means

Normal personal use includes:

• Publishing and updating notes from Octarine.
• Reading public notes and their images.
• Using a terminal, API client, Shortcut, or local agent for personal workflows.
• Occasional scripts that publish, update, list, or unpublish a reasonable number of notes.

The following falls outside fair use:

• Using Octarine Share as a generic file host, image CDN, backup target, or data mirror.
• Bulk publishing unrelated machine-generated pages, spam, or scraped content.
• Sustained high-frequency polling, crawling, or automated traffic.
• Stress testing or load testing the production service without written permission.
• Sharing credentials, reselling API access, or using one license as a multi-user service account.
• Evading technical limits, temporary blocks, or other abuse controls.
• Publishing content that violates applicable law or the rights of others.

Responsible Automation

Automation should be conservative and recover gracefully:

• Reuse a valid bearer token instead of repeatedly calling the authentication endpoint.
• Keep concurrency low. Start with one request at a time and only add concurrency when needed.
• Cache public reads when your tool permits it.
• Avoid polling /api/user/notes; fetch it in response to a user action or at a modest interval.
• On 429, use Retry-After when present. Otherwise use exponential backoff with jitter.
• Retry idempotent GET requests after transient failures.
• Do not automatically retry POST /api/publish or PATCH /api/notes/:cuid; they can create duplicates or extra version snapshots.
• Require a user confirmation before unpublishing content or changing account-wide sharing settings.

Enforcement

Octarine may temporarily throttle or block traffic that harms reliability, security, or other users. Depending on the request, the API may return:

• 413 when a body, stored note, or image is too large, or image storage is full.
• 429 when a client should slow down.
• 5xx when the service is temporarily unavailable.

Severe or repeated abuse may lead to restricted sharing access. Limits may change as the preview API develops. When a limit changes materially, this page is the source of truth.

Storage And Availability

Public sharing is a convenience feature, not a backup. Keep the original Markdown and attachments in your Octarine workspace and include that workspace in your normal backup routine.

Unpublishing a note removes public access, schedules all of its uploaded share images for deletion, and releases their storage usage. It does not delete the source file from your workspace.

Do not use a public share as access control for confidential material. Hiding properties removes them from the rendered page and returns an empty properties object from the public note API, but the rest of the publication remains public.

The preview API has no service-level uptime guarantee. Clients should surface errors clearly and avoid destructive fallback behavior.

Quick Answers