About Sleevy

Why it exists

Most reading lists ask you to file a link before you have read it. You are asked to pick a folder, add tags, and decide what the thing is for — at the exact moment you have the least idea, because you have not read it yet. So the link goes in an open tab instead, and the tab stays open for a month.

Sleevy takes the link first and asks questions later. Saving is one action from wherever you are. Titles, images, and a short summary are fetched in the background, so an item that arrived as a bare URL has something to recognise it by when you come back to it. Folders and tags are there when you want them, and ignoring them entirely is a perfectly good way to use the app.

Built to be driven by other software

Everything the apps can do is available over a documented REST API. There is an OpenAPI 3.1 description, an API key you can create yourself in settings without talking to anyone, idempotent writes so a retry cannot save the same link twice, and cursor-based paging for walking a long queue.

Sleevy also runs a Model Context Protocol server, so an AI assistant can save a link for you, tell you what is in your queue, mark something read, or tidy your folders — with your permission, scoped to exactly what you approved, and revocable at any time from the same settings screen.

How it treats your data

Your queue is yours. Sleevy stores the links you save and the metadata it fetches about them; it does not sell that, and it does not need it for anything except showing you your own reading list. A profile is private until you deliberately publish a folder to it. You can delete your account, and the data with it, from settings. The privacy policy says all of this in more detail.

Get in touch

Sleevy is a small, independently built product. Questions, bug reports, and feature requests all reach a person: see the contact page, or read the developer documentation if you are here to build something against the API.