Rentry.co

rentry.co · Storage · 1 record · JSON

Rentry.co Storage

fails: quotainstitutionno cardRwrite-gated

rentry.co · anonymous-dump · storage/rentry-co · JSON · compare

Free tier	200,000 characters per entry (hard, enforced at API), unlimited entries, no account required. Entries kept 'forever' unless they break rules. unit unlimited; metered on unstated
Price	none stated
Per-object cap	not stated
Retention	200,000 characters per entry (hard, enforced at API), unlimited entries, no account required. Entries kept 'forever' unless they break rules
Egress	free direct GET, no metering; behind Cloudflare so it is CDN-cacheable at the edge.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: 200,000 characters per entry (hard, enforced at API), unlimited entries, no account required. Entries kept 'forever' unless they break rules. No throttling at 8 request
Limits	request-rate 8 requests/second source write-gated application and stated in the 400 error, so silent truncation does not happen — writes fail source 200,000 chars per entry; custom URL 2-100 chars; edit_code required to modify; no per-account quota and no per-IP cap observed (8 rapid anonymous POSTs all returned 200); URL squatting reclaimed after 12 months idle.
Binding	write-gated the write is a queue with a person or a rule in it, so the upload rate is set by somebody else
Interface	rest, cli rest
Tooling	Official Python client github.com/radude/rentry (593 stars) + pip package 'rentry'; single-file CLI with zero dependencies.
Composes with	unlimited anonymous entries x 200,000 chars (~150 KB of base64 binary after the 4/3 encoder penalty). To reach 500 GB you would need ~3.5M entries, so this is a control-plane / manifest store, not a data tier — unless an unlimited free identity source is added, and even then the operator's storage is the ceiling.
Reliability	No throttling at 8 requests/second-ish, but a 200k-character ceiling is enforced by the application and stated in the 400 error, so silent truncation does not happen — writes fail loudly. Bulk write volume is the untested risk.
Notes	200,000 characters per entry (hard, enforced at API), unlimited entries, no account required. Entries kept 'forever' unless they break rules.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:request-rate 8.0 requests

Evidence (4)

date	source	what it proved
2026-10-21	rentry.co/what	'200000 characters for text field', 'Your entries will be kept forever'
2026-10-21	rentry.co/api/new	probe: POST with form fields url/edit_code/text -> {"status":"200","url":"https://rentry.co/n7f74b9t","edit_code":"..."}; page then contained the probe string
2026-10-21	withheld	probe: POST with 293,336 chars -> {"status": "400", "errors": "Ensure text field has at most 200000 characters (it has 293336)."}
2026-10-21	withheld	probe: 8 sequential anonymous creations -> 200 x8, no rate limit

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "200,000 characters per entry (hard, enforced at API), unlimited entries, no account required. Entries kept 'forever' unless they break rules.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (7)

$.evidence[2].url private-url
$.evidence[3].url private-url
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted