sto.care
sto.care · Debrid · 1 record · JSON
sto.care (ul.sto.care) Debrid
caveatanonymousno cardMpull-count
| Free tier | 3-day expiry and a JSON link from a single PUT, no account. The site advertises 'a retention period that depends on file size' and the upload reply carried expiresAt three days out. unit requests; metered on request-count; The upload host is ul.sto.care and the download host is trystocare.com; the brand and both domains disagree. |
|---|---|
| Price | USD 0 |
| Per-object cap | unverified: no size cap is stated on the pages read; 1 MiB was accepted |
| Retention | expiresAt 2026-10-26T02:22:40.454Z for an upload at 2026-10-23T02:22:40Z, so 72 hours (3 days) |
| Egress | Downloads are served from trystocare.com. The site advertises a 10-download limit per link, which makes the link a distribution budget rather than a store. free_allowance: none published |
| Identity | anonymous A bare PUT with no cookie, no account and no email returned a link. |
| Limits |
The download limit was not exercised: 10 fetches of one link would settle it, and the second fetch is the interesting one because the first may not count. |
| Binding | pull-count At 1 TiB a month no published byte cap was hit, but a 10-download link means a re-fetch of the same object fails once ten readers have had it, and 72 hours bounds it again; the pull count is the first of the two that a busy object meets. |
| Interface | rest, cli curl -T file https://ul.sto.care/<name> returns JSON {url, expiresAt}, with the download URL on a different host. endpoint: https://ul.sto.care/ |
| Tooling | Any HTTP client that can PUT a file; the transfer.sh one-liner works with the hostname swapped |
| Composes with | A transfer.sh-shaped PUT is the cheapest thing to wire into a script that already speaks that idiom, and the JSON reply makes the link parseable, but 3 days and a per-link download count make it a hand-off, not a mirror. |
| Reliability | The upload host and the download host are different domains, so a client that allow-lists the upload domain breaks at retrieval. |
| Notes | A credible transfer.sh replacement that actually answers, and the only measured relay that returns a machine-readable expiry. The caveat is that its own documentation lives in blog posts rather than a docs page. |
| Evidence rung | measured Upload and read-back at 1 MiB with a matching SHA-256; the cap and the 10-download limit are vendor claims and were not pushed. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
| Parsed numbers |
|
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe:https://ul.sto.care/ | PUT of 1 048 576 bytes -> HTTP 200 body {'url':'https://trystocare.com/c8aujwob94','expiresAt':'2026-10-26T02:22:40.454Z'} |
| 2026-10-23 | probe:https://trystocare.com/c8aujwob94 | read-back 1 048 576 bytes, sha256 da0099c231f1182a5d411c8ac5149dfb7a2e3578a3970928490cb78ba92aecc9, full-body hash matched |
| 2026-10-23 | sto.care/blog/file-io-alternative/ | 'You get a JSON link that allows 10 downloads over 72 hours' - the vendor's own blog, which is the only place either number is stated |
| 2026-10-23 | sto.care/blog/0x0-st-alternative/ | the service positions itself as a 0x0.st and transfer.sh replacement with a curl one-liner |
More fields (2)
{
"download_host": "trystocare.com",
"expires_at": "2026-10-26T02:22:40.454Z"
}