faq

paste it, version it, share the link. docbin turns markdown, html, code, or plain text/logs into a rendered document with a stable url under your handle. every update to the same name becomes a new immutable version - old links keep working - and the content renders on its own sandboxed origin, never inside your session.

no. POST /api/docs/paste/anon takes a raw body with zero auth - handy for scripts, crash reporters, and game mods. anonymous docs land under the reserved anon handle with a generated name, are always unlisted, and expire after 30 days. they're also rate limited harder than everything else.

signing in with github gets you your own handle, named docs, visibility control, api keys, and docs that never expire unless you say so.

three levels: private (only you, plus anyone you grant by handle, share a token with, or give the passphrase), unlisted (anyone with the link - the default), and public (listable, shows in your atom feed).

yes. a free account gets named docs that never expire, every visibility and sharing option, api keys, the mcp server, uploads up to 5 mib, and up to 20 files per group. docbin pro raises those limits (25 mib uploads, 50 files per group, higher rate limits) for people who need more. nothing currently free moves behind the paywall.

markdown gets a full rich render (code blocks, tables, math, mermaid), html renders as-is in a sandbox, and code/text render highlighted. unpinned docs follow the reader's light/dark preference; you can pin a theme per doc (paper, dark, terminal, book). your settings also pick the syntax-highlight palette used for each color mode - every theme highlight.js ships.

code docs cover plain text and logs too: pass a language - including log formats like log and accesslog - and the doc renders highlighted and soft-wrapped; skip it and you get clean plain text.

your call. docs from an account default to never expiring; you can pick 10 minutes, 1 hour, 1 day, 1 week, 2 weeks, 1 month, 6 months, or 1 year at upload (or change it later from edit). expired docs return 410 gone and are purged on a daily sweep. anonymous docs always expire - 30 days at most, sooner if the paste asks for it.

there's also burn-after-reading and max-view budgets if a doc should disappear after it's been seen.

pasting to the same name appends an immutable version. /you/notes always shows the latest; /you/notes/v3 stays version 3 forever. deleting a doc deletes all of it.

yes, if it's yours. the edit form at /you/notes/edit prefills the content, type, title, and description; saving forks a new immutable version under the same name, so the url never changes and old /vN links keep working. renaming isn't a thing - a new name is a new doc.

yes - upload more than one file and they become a group under a single url, gist style. the app view lists the files and renders them stacked; each file is also reachable on its own (/you/proj/main.rs) and on the raw origin. free groups hold up to 20 files, pro up to 50.

free accounts: 5 mib per upload. pro: 25 mib. anonymous pastes are capped at 1 mib. for a group the cap is the total across every file in it.

yes. a private doc has three opt-in layers you manage from its sharing panel: a passphrase (readers unlock with it in the app view), @handle grants (name specific docbin users who can view it while signed in), and revocable share links (tokens that also work on the raw origin for embedding). revoke any of them whenever you want.

add ?raw=1 to a doc url, or hit the raw origin (raw.docbin.app/you/notes) for the unrendered bytes - handy for curl, embedding, and diffing. the raw origin is sandboxed and never shares your docbin.app session.

as little as possible: view counts and a salted daily visitor fingerprint that can't be reversed or linked across days. no ad networks, no third-party trackers, no cookies for readers. the privacy policy has the full picture.

everything the ui does, the api does. curl --data-binary @notes.md -H "Authorization: Bearer <key>" https://docbin.app/api/docs/paste returns the url as plain text. multipart file uploads work too (-F file=@crash.log), and there's an mcp server for claude and other clients. see the api reference.

mint keys in settings. the secret (dbk_...) is shown once - store it then. keys act as you, are scoped to the rest api, and can be revoked any time. mcp uses github oauth instead of keys, so connecting an mcp client never needs one.

yes. point a client at https://mcp.docbin.app/mcp - claude mcp add --transport http docbin https://mcp.docbin.app/mcp - and sign in with github in the browser the first time. no api key to paste.

delete any doc from your dashboard or the api; that removes every version of it. to delete your whole account and its data, email support@cryptik.consulting.

every doc page has a report action - no account needed. reports go straight to moderation; actioned content is removed and repeat offenders banned.

yes - docbin pro raises your upload size, creation rate limits, and how many files you can group into one doc. everything currently free stays free. see pro membership in settings to upgrade or manage your plan.

no illegal content, malware, phishing, leaked credentials or personal data, harassment, or spam, and no poking at docbin's security or rate limits. the full list is in the acceptable use policy. break it and the content comes down and the account gets banned - see the terms for the rest.