Workbooks
Any answer, packed as something that runs: a notebook, a pinned environment, the exact model file, an MCP server and a SKILL.md. The workbook is the artifact and the conversation is the means, so a workbook outlives the thread that produced it and stays pullable long after the tab is closed.
A workbook is reached through the listing. Each entry in your listing says what the workbook inside contains — enough to tell one from another without unzipping anything — and every workbook in the listing can be downloaded, including by an agent without the browser that made it. A pull only returns a workbook that has passed the workbook spec, and never one carrying a claim the index did not make, so the artifact you unpack matches what the index said.
The limit to design around is ownership. A workbook is served only to the account that owns it, so an agent pulling without a browser still has to pull as that account, and no pull from any other account is served.
Tags @api @workbook
Call it
GET https://api.bighugger.com/v1/workbooks
curl -X GET https://api.bighugger.com/v1/workbooks \
-H 'authorization: Bearer $BIGHUGGER_API_KEY'
Every call is authenticated with an API key as a bearer token. A key carries scopes, so a key that cannot reach this endpoint is refused rather than silently returning less.
What it guaranteesgraph LR
cap["Workbooks"]
b0("Every workbook in your listing<br/>can be downloaded")
b1("A workbook is only ever served<br/>to the account that owns it")
b2("Every workbook is validated<br/>against the workbook spec<br/>before it is served")
b3("A workbook never contains a<br/>claim the index did not make")
b4("A listing says what is inside<br/>without unzipping anything")
b5("An agent pulls a workbook<br/>without the browser that made<br/>it")
cap --> b0
cap --> b1
cap --> b2
cap --> b3
cap --> b4
cap --> b5
classDef cap fill:#eef2ff,stroke:#1d4ed8,stroke-width:1px,color:#1d4ed8
classDef beh fill:#fffdf2,stroke:#eeb900,stroke-width:1px,color:#14161a
class cap cap
class b0,b1,b2,b3,b4,b5 behAlways true
Given a thread that has produced an answer with sources
Every workbook in your listing can be downloaded
Download access is what makes a finished workbook useful to customers; without it, a build they can see would still be one they cannot use.
Given a workbook that has finished building
When it appears in your listing
Then it is downloadable by id
Vocabulary workbook
A workbook is only ever served to the account that owns it
Without an ownership check, one account's workbooks would be visible to another, so cross-account isolation depends on every request being filtered to its owner.
Given workbooks belonging to several accounts
When a workbook is requested
Then it is returned only to the account that owns it
And a request for another account's workbook is refused
Every workbook is validated against the workbook spec before it is served
A half-written workbook would otherwise be served as though it were complete, quietly delivering less than it promises.
Given a manifest and a notebook written by the model
When the workbook is assembled
Then it is checked against the completeness rules in the workbook spec
And a workbook that fails those rules is never served
Vocabulary workbook
A workbook never contains a claim the index did not make
If a partial workbook could add claims of its own, readers would have no way to tell verified content from invention.
Given a workbook that could not be generated in full
When it is built from the sources alone
Then it covers less ground than a full workbook
And every claim in it is one the index already made
And it passes the same validation
Vocabulary workbook
A listing says what is inside without unzipping anything
The listing lets a reader judge a workbook's contents and provenance at a glance, so nothing inside it has to be unpacked or opened to be understood.
Given a workbook that took the repair path or the fallback
When the build finishes
Then the listing carries its origin, runtime, cell count and entities
And it says whether the workbook was packed from sources alone
Vocabulary workbook
An agent pulls a workbook without the browser that made it
A workbook must outlive the browsing session that produced it, otherwise it stays trapped wherever it was made and no later agent can reach it.
Given a caller with an API key
When the workbook is requested by id
Then it is served to the same account that owns it
And the thread it came from is not needed to fetch it
What to know
Treat GET /v1/workbooks as a complete map of what you can pull: every workbook it shows is downloadable, so there is no listed-but-unfetchable case for your client to handle. The listing also says enough about each workbook's contents that you can decide what to fetch without unzipping anything, and what you eventually pull will never claim more than the listing did. That makes the index a safe basis for displaying, filtering, or gating on your side — you can render descriptions from the listing without bracing for surprises inside the package.
Access is enforced strictly by account: a workbook is served only to the account that owns it, so the one failure mode worth engineering for is a request for work that belongs to someone else. Expect a refusal rather than a copy, and if you are building anything that shares or embeds across accounts, route each caller through their own credentials instead of assuming one account's pull can be replayed by another. On the happy path you can be stricter than usual — anything served to you conforms to the workbook spec, so a strict parser beats a defensive one. Pulls are also self-contained: an agent can fetch a workbook without the browser that produced it, and it stays pullable long after the conversation that created it is gone, so nothing in your code should tie availability to an open tab or a live session.