TAVONEL
Menu
PricingOpen the compiled sample
Chapters

Product guide

How to use what TAVONEL offers today, screen by screen, and where each screen stops.

What this guide covers

No API key needed for this chapter.

This guide walks through the parts of TAVONEL anyone can use today without an account: the public Compiled World with its evidence, changes and relations, the signed sample package, the API reads that take no key, the developer files and the MCP bridge. Each chapter says where to click and where the screen stops.

“A finished Compiled World is open to read in full today, with its evidence attached. Compiling your own sources is set up with us rather than enabled by a plan purchase.”

Note “We arrange intake for your own sources with you.”

WhereExplore a Compiled WorldContact

What TAVONEL makes

No API key needed for this chapter.

TAVONEL compiles documents into a Compiled World: semantic objects, the relations between them, and the evidence each object rests on.

Evidence is a page and a region on that page, bound to a source version by digest. An object with no evidence is not published.

A compile produces a candidate. A person activates it in a signed-in session, and answers are served from the active version only. No API key can activate a candidate, and no compile activates itself.

Note “Activation is always an explicit human decision.”

WhereConceptsCompiled World

Open the public World

No API key needed for this chapter.

/explore is a read-only sample World compiled from Apple's public SEC filings. It opens without signing in.

  1. Open /explore. The note at the top names the sample and the date its sources were captured.
  2. Under Find a sample question, choose a prepared question, or type to filter them.
  3. Read the answer under Retrieved source passage. It is the complete text of the source regions the retriever selected, not a rewrite of it.
  4. Each row under the passage names its source file and page. Choose a row to open that page; on a phone, Result and Source switch between the passage and the page.

Note “Prepared retrieval results from this artifact. Free-form AI queries are not running in this public demo.”

Follow a result to its source in the public World
Transcript
  1. First, the analytics notice: No thanks.
  2. A public sample World that opens without signing up: a read-only sample compiled from Apple's public SEC filings.
  3. Prepared retrieval results from this artifact. Free-form AI queries are not running in this public demo.
  4. Pick one of the prepared questions.
  5. The answer is a source passage chosen by retrieval. Under it, the page says it is a quotation, not an independently checked conclusion.
  6. Each excerpt names its source file and page. Choosing a row opens that page.
  7. The source page opens, with the region the excerpt came from marked on it.
  8. The source version is pinned by its content hash, and each piece of evidence has a permanent link.
  9. The evidence inspector opens one object beside the source region that supports it.
  10. Next steps through the source regions behind this object, one at a time.
  11. Change sets the World built from the annual filing beside the same World after later filings arrived.
  12. Each filing that arrived is shown with its source page.
  13. The comparison runs object by object and counts rebuilt and unchanged identities separately. It is a comparison recorded in this sample.
  14. A page with no region is marked as such, and nothing in this World stands on it.
  15. The Evidence page shows every region a World read from one page.
  16. Each region carries a locator: its page, its box coordinates and the source hash.
  17. Open this region in Explore takes the same region back into Explore.
  18. We arrange intake for your own sources with you.

WhereExplore a Compiled World

Read the evidence

No API key needed for this chapter.

The source pane shows the page the passage came from, with its region marked, and the exact passage under it. The pane's header says whether you are looking at the original PDF or a reference render of that page.

  1. Source version names the version of the document the region is bound to: the document plus the sha256 of its sanitized bytes.
  2. Permanent evidence link is an address for this piece of evidence that you can copy and share.
  3. Open full evidence inspector opens the object beside the source region that supports it, with its state, its evidence and its relations. When the object has more than a single region, Previous and Next step through them.

Note “This is a quotation selected by retrieval, not an independently verified conclusion.”

WhereExplore a Compiled WorldEvidence, in Concepts

See what changed

No API key needed for this chapter.

Changes sets the World compiled from Apple's 2025 Form 10-K beside the same World after the 2026 filings arrived.

  1. Choose Changes on /explore.
  2. Read the counts: Objects reached and Unchanged object identities, with the objects added, removed and rebuilt in place beneath them.
  3. FILINGS THAT ARRIVED shows each filing with the page it was read from, and opens the original PDF or its reference render.
  4. HOW THIS WORLD WAS REACHED lists each step with what it added, rebuilt in place, removed and left unchanged.
  5. Objects, relations and evidence as a list marks every object AFFECTED or UNCHANGED in words.

This is the comparison recorded in this sample, not a live feed of new filings.

Note “Both snapshots are complete compiles of the corpus as it stood, compared object by object. Every count below is measured from that comparison.”

WhereChanges

Relations

No API key needed for this chapter.

Relations opens the World as a graph of its compiled objects and the relations between them.

  1. Choose Relations on /explore.
  2. Select an object. Directly connected lists each relation by its name and the object at its other end.
  3. When the object has evidence, Open source evidence takes it to the region that supports it.
  4. Objects, relations and evidence as a list gives the same graph as text. It is open from the start when your system asks for reduced motion.

Note The line under the graph says how many of the World's graph nodes are on screen.

WhereRelations

Verify a signed package

Some steps in this chapter need an API key.

/demo follows a synthetic source through compile, review and activation to an answer and a signed export.

  1. Open /demo and go to Signed export. It shows the Ed25519 signature check over the sample manifest, with the manifest schema, the package files, the key and the signed payload digest.
  2. Download the offline verifier gives you tavonel-verify-export.mjs, the file /developer/channel.json lists for checking an export.
  3. GET /api/export/trust publishes the key record exports are signed with, or refuses with EXPORT_SIGNER_NOT_CONFIGURED where no signer is configured.
  4. The verifier checks an archive, and downloading an archive of a World takes an API key with the collections:download scope.

Note “A valid signature proves manifest integrity. It does not certify semantic quality, customer approval, or current activation status.”

WhereSigned product pathExportsCLI and package verification

Call the API without a key

No API key needed for this chapter.

The API reference at /api opens with Try it, with no key: “Three unauthenticated reads, run from this page against TAVONEL. No signup, no credential, nothing that spends.”

  1. What TAVONEL can read runs GET /api/v1/capabilities, the same list the upload route validates against.
  2. What is open right now runs GET /api/status, including whether compiling your own files is open.
  3. The shape of an answer runs GET /reproducibility/sample-world: object, evidence, source version, page and region, from a fixed sample.
  4. Recipe 2 on Integration recipes makes the same read from a published Python script that recomputes the response's Content-Digest header over the bytes it received.

Note “A deterministic product fixture, unsigned and labelled as such in its own disclosure field. Build against the shape; do not judge extraction from it.”

First API and CLI calls, without a key
Transcript
  1. The API reference runs unauthenticated reads from the page: no signup, no credential, nothing that spends.
  2. What TAVONEL can read: the same list the upload route validates against.
  3. The deployment's own state, including that compiling your own files is not open here.
  4. A fixed product sample that shows the shape of an answer. Build against the shape; do not judge extraction from it.
  5. The response carries a Content-Digest header.
  6. Now a terminal. This screen replays a captured session: the commands that ran and the output they printed, unedited.
  7. The hash computed from the bytes received equals the Content-Digest the server stated.
  8. The published Python recipe is downloaded and matched against its hash in the channel manifest.
  9. The recipe recomputes the digest and prints each piece of evidence with the page and region it points at.
  10. The sample labels itself a product sample, not customer proof.
  11. The CLI file is matched against the channel manifest the same way.
  12. The CLI's status command runs without a key. It reports reading the public World as open, and compiling your own documents as closed.
  13. A finished Compiled World is open to read in full today. Compiling your own sources is set up with us.

WhereTry it, with no keyRecipe 2: Python over the public sample World

Get the developer files

Some steps in this chapter need an API key.

/developer/channel.json lists every file TAVONEL publishes for developers, each with its URL and sha256, under a single channel version.

  1. Download the file you need from the URL channel.json gives for it.
  2. Compute its sha256 and compare it with the value in channel.json: sha256sum on Linux, shasum -a 256 on macOS, certutil -hashfile with SHA256 on Windows.
  3. node tavonel-cli.mjs status prints the public status and needs no key.
Fetch the CLI, check it, ask for status
curl -fsS https://tavonel.com/developer/channel.json
curl -fsSO https://tavonel.com/developer/tavonel-cli.mjs
sha256sum tavonel-cli.mjs
node tavonel-cli.mjs status

Note The CLI has no upload command. Its usage text names the key as “Scoped tvnl_live_... token (required except status)”.

Wherechannel.jsonCLI and package verification

Connect the MCP bridge

Some steps in this chapter need an API key.

The MCP server is a single file, tavonel-mcp.mjs, with nine read-only tools. There is no npm or PyPI package: you download the file and point your client at it.

  1. Download tavonel-mcp.mjs and check its sha256 against /developer/channel.json, as in the previous chapter.
  2. node tavonel-mcp.mjs --version prints the exact build.
  3. Register it with Claude Desktop (claude_desktop_config.json) or Claude Code (.mcp.json) by its absolute path. /docs/mcp carries the block.
  4. node tavonel-mcp.mjs --doctor checks the key, the channel pin and a real read, and names the first check that failed.

The server refuses to start if a tool that writes is ever added to it. There is no activation tool: activation stays with a person in a browser.

Note Without a key the tool list still answers, and every tool call returns “API_KEY_MISSING: set TAVONEL_API_KEY to a key from your workspace”. Keys and your own World are set up with us.

The read-only MCP bridge, as far as it goes without a key
Transcript
  1. The Developers page: how agents and code read a Compiled World over MCP and the API.
  2. No write tool, and the server refuses to start if one is added.
  3. The read-only MCP server is one downloadable file. There is no package to install.
  4. The channel manifest lists the version and a hash for every file.
  5. Now a terminal. This screen replays a captured session: the commands that ran and the output they printed, unedited.
  6. The file is downloaded, hashed, and compared with the manifest value. They match.
  7. --version prints the exact build.
  8. No TAVONEL variable is set in this shell, so everything below ran without a key.
  9. The JSON-RPC requests sent over stdin: initialize, tools/list and one tools/call.
  10. The server's responses, exactly as printed.
  11. Filtered to names: the tool list. None of them writes.
  12. Without a key, the tool call stops at API_KEY_MISSING. This is the real response.
  13. --doctor names what is missing and exits with a failure code.
  14. The Claude Desktop config block from the MCP docs: the absolute path to the downloaded file, and a placeholder where a key goes.
  15. The key lives in the client's env block or its secret facility, never in args.
  16. The Claude Desktop app itself is not part of this recording.
  17. The docs' tool table, and the note that there is no write tool and no activation tool.
  18. A finished Compiled World is open to read in full today. Compiling your own sources is set up with us.

WhereRegistering it with a clientMCP and agents

Estimate a cost

No API key needed for this chapter.

/pricing carries a calculator, What will this run cost? Enter the sources in the run and the pages in the longest source.

  1. It first shows how that run meets the compile ceilings, row by row.
  2. Then it shows the Developer and Team totals, the pages beyond Developer, and the maximum if every extra page escalates.

“All figures in US dollars, excluding tax.”

Note Buying a plan starts with a conversation: the plan actions on /pricing go to /contact.

WhereWhat will this run cost?Contact

Status and trust

No API key needed for this chapter.

  1. /status shows the configuration and activation state, the scheduled dependency checks and the incident history.
  2. /trust lists what is in place, what is coming and what is absent, each row linked to the page that states it.
  3. /security describes how document processing is controlled: the enforced processing boundary and the controls customers can rely on.
  4. /benchmarks/gdp-pdf publishes a two-arm run on the public GDP.pdf task set, with its result as the page's headline.

Note “No SOC 2 report, ISO 27001 certificate or independent penetration-test report exists yet.”

WhereStatusTrust CenterSecurityGDP.pdf run

Start with your files

No API key needed for this chapter.

  1. /sources lists every source TAVONEL reads and what survives the read, format by format.
  2. /evaluation sets out how an evaluation of your documents is agreed: permissions, questions, limits, costs and evidence quality before processing begins.
  3. /contact asks you to “Tell us what your documents need to become, without sending the documents themselves.”

Note “We arrange intake for your own sources with you.”

WhereSourcesEvaluate your documentsContact

Getting help

No API key needed for this chapter.

“Email to support@tavonel.com is acknowledged within 1 business day (KST). That is an acknowledgement target and not a resolution time: no resolution time is committed, and security reports to security@tavonel.com are read first rather than queued behind product questions.”

Every documentation section ends with Report an issue with this page, which opens an email to support@tavonel.com with the page named in the subject. This guide ends with the same link.

Wheresupport@tavonel.comContact

Glossary and revision log

No API key needed for this chapter.

TermMeaning
Compiled WorldWhat a set of sources compiles into: semantic objects, relations between them, and the evidence each object rests on.
CandidateA compile result nobody has accepted yet.
ActivateMake a candidate the active version, the version answers are served from. A person does it in a signed-in session; no API key can.
EvidenceA page and a region on that page, bound to a source version by digest.
RegionThe area of a page a passage was read from, as a box in the page's 0-1000 coordinate frame.
Source versionThe document plus the sha256 of its sanitized bytes. It changes when the file changes.
DateChange
2026-10-19First edition: chapters 0 to 13 and this appendix.

WhereConcepts

Reviewed 19 October 2026

Something here out of date or wrong? Report an issue with this page.