Tools and sources
The API and tools Blotato Publisher uses, where each comes from, its version.
A Deliverable is what you end up using. A Helper is a tool needed to make it or run it. The Agent should read this whole page first and confirm it only visits the addresses in the tool list.
This page follows the Lorevik Docs standard.
Tool list#
| Tool | Type | Source | Version | Install command |
|---|---|---|---|---|
| Blotato Publisher Package | Deliverable | To confirm | 0.1 (draft) | Copy the folder |
| Blotato REST API | Helper | Blotato | v2 | None |
| Your Agent | Helper | Claude Code | Follows the version you installed | See each one's website |
Blotato Publisher Package#
The Package itself is a folder holding SKILL.md for the Agent, a fixed-layout Page (service.html), the data file data.json and its structure data.schema.json, a manifest, and a Routine proposal routine.plan.json. The layout is fixed: the Agent only changes data.json, and after every Agent run the host reverts any changes to the other files.
To confirm: This Package is not listed on Explore yet and has no fixed download address. Once it is listed, its Explore listing and version go here.
Agentread SKILL.md to learn the call order and the write-back rules.
Install Copy the whole blotato-publisher folder into your Vault's living-surfaces/.
Configure No need to change any file in the Package. Before the first real use, have the Agent clear the example records (the invented Demo Bakery) and delete the fixture field; see Setup.
Verify Open it in Lorevik. The Page shows three columns with example data, and the top is marked "Synthetic sample data".
Version 0.1, draft, only checked with synthetic data on 2026-11-03.
Blotato REST API#
Blotato's public API, called by your Agent with your own API key. The only network address the Package declares is https://backend.blotato.com, and the Agent visits no other site. Source addresses are fetched by Blotato's servers; the Agent does not collect them itself.
Agentuse it to submit sources, check extraction, submit posts and check posts. The value of the blotato-api-key request header is read from the environment variable, never written into the command.
Install No install needed.
Configure The key is taken only from the environment variable BLOTATO_API_KEY. Do not paste the key into the Thread, and do not write it into any file in the Package. SKILL.md also describes handing over the key through Lorevik's authorization flow; that path is not built in the App yet, see Setup.
Verify If the Agent's call to GET /v2/users/me succeeds, the key works. A 401 or 403 means the key is invalid or lacks permission.
Version All API paths are under /v2/. Blotato has not published a version number, so v2 here follows the path.
To confirm: The following behavior comes from Blotato's public documentation and the source of its official n8n node, and has not been verified with a real account: whether a scheduled time with a non-UTC offset is interpreted by that offset; what the post status is before the scheduled time; the full set of extraction job statuses; and the exact shape of authentication errors, rate limits and retries.
Your Agent#
Claude Code, Codex or the Agent in Lorevik. It reads SKILL.md, calls Blotato, and writes the server-side ID and status of each step back to data.json.
Agentthis is you. Read sections 2 to 7 of SKILL.md before you act.
Install Install it by your Agent's own instructions; the Agent in Lorevik needs no separate install.
Configure Make sure the Agent can read the environment variable BLOTATO_API_KEY. The Agent's real network reach depends on the permission settings you give it. The declaration in the Package is only a description; Lorevik does not currently enforce this limit for the Agent.
Verify In the Thread on the right, say "Read this Package's data. How many sources are there now?" The Agent can answer from data.json.
Version Follows the version you installed.