how it works

Capture. Read. Write. Cite.

Uoink turns raw sources into a local corpus your AI can use. One source card travels from capture to library to Writing Studio to your agent.

Get Uoink See sources

Capture - Library - Workspace - Iterate - Distribute

Uoink dashboard showing a populated local library of source cards — The library is the home base. Source cards stay searchable, citable, and ready for agents.

the five-step loop

From source to output, without losing the receipts.

The browser path and the agent path share one spine: save the source, keep it on disk, write from it with citations.

01step

Capture

Click the Uoink button, right-click a source, or queue a feed. The helper extracts transcripts, screenshots, comments, and metadata while you keep working.

02step

Library

Every source lands as markdown on disk and gets indexed in local SQLite search. Your corpus keeps titles, creators, timestamps, and source links intact.

03step

Workspace

Group source cards around a topic, channel, claim, or launch thread. The same card can open in Claude, feed a draft, or expose an MCP call.

04step

Iterate

Writing Studio pulls from the corpus, checks Voice DNA, keeps creator credit visible, and lets you revise from evidence instead of memory.

05step

Distribute

Copy the draft, open it in X, cite the creator, or let an agent pull the same source through Uoink's local MCP tools.

same card, different verbs

One source card serves creators and developers.

Creators click Study hooks, Write thread, or Pull evidence. Developers copy the MCP call, open the corpus file, or hand it to Cursor. Same source, different next move.

source cardkarpathy-intro-to-llms.md

hook: curiosity_gap + stakescreator: Andrej Karpathy / source: YouTubeentities: OpenAI, transformer, tokenization, RLHFactions: Study hooks / Write thread / Copy MCP callcitation: source URL + timestamps preserved

two paths after capture

Paste it yourself, or let your agent pull it.

creator path

Uoink this video, paste the corpus into Claude or ChatGPT, and ask for a hook breakdown.

The answer cites transcript moments, screenshots, and audience comments from the saved source.

developer path

uoink_video(url)
get_job_status(job_id)
get_uoink_corpus(corpus_id)
classify_hook(corpus_id)
agent drafts from the cited corpus

Creator workflow Developer setup