The platform A library runs methods.
A library runs methods.
Its endpoint serves what they find.
Bring a podcast, a newsletter, a shelf of papers or a table of records. The engine reads every passage through typed questions, builds a graph, a table, a trajectory or a codebook, and serves it as one endpoint, to you and to any agent, every finding traceable to the passages it came from.
How it goes
- 1Bring a source. Paste a feed, connect Zotero or Zoom, upload a table. The adaptor lists what it holds before anything is fetched.
- 2Say what kind of reading it is. People in conversation, one voice giving talks, a writer’s essays, papers, or records for an instrument. The adaptor proposes.
- 3See the program and the price. The method shows itself as steps, with an estimate from the ledger, before it runs.
- 4Watch it read. Jev answers on every passage, the frontier names what no option fits, code builds the structure.
- 5Use the endpoint. One MCP endpoint per library, for your apps and any agent. Every number with its interval, every quote a slice of a source.
- 6Grow and publish. Add a card, start the codebook, review what it proposes, freeze what settles into a method others can run.
For agents
Every library is an MCP endpoint. What it offers follows what it runs.
POST /mcp/<library>
Authorization: Bearer ido_…
{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"overview","arguments":{}}} The tools follow the methods. A library that keeps a graph offers entities, moments, speakers, search. One that runs a card offers method, indicators, evidence; one that follows subjects through time, reports; one that grows a codebook, codebook.
Paid tools are capped per token per day. Every paid call is a row in the ledger.