Developers
REZICS receives proposals, never full text.
People with access to a text use their own AI agent and model to extract characters, aliases, relations, events, and places chapter by chapter. Each item includes a location and short quote for human review in REZICS. The toolkit does not connect to the internet or report usage.
Boundary
What stays and what gets sent
The original files and full chapter text stay on your computer. The toolkit converts them and records locations offline. REZICS receives characters, aliases, relations, events, and places, each with a location and short quote, along with the agent and model used and whether inference ran locally or in the cloud.
When you use a cloud model, text read by the agent is sent to that model provider. You choose whether to do this. To keep everything local, use a local model and disable cloud tools that can read files.

Steps
From a file to a proposal
rezics-wiki units novel.epub
rezics-wiki verify novel.epub \
- < locator.jsonSplit into passages
rezics-wiki unitsConvert TXT, EPUB 2/3, or plain text visual novel scripts (.rpy) into passages. Each includes a rezics-locator-v1 location and the file’s SHA-256 hash.
Give it to your agent
skill/SKILL.mdThe toolkit includes a skill that guides the agent through each chapter and helps distinguish narration, dialogue, rumors, and assumptions.
Match and precheck
wiki_candidates · wiki_validateCheck existing names and aliases first. Results are grouped as matched, new, unclear, or unavailable. Then precheck quote limits and missing chapter references.
Submit for review
wiki-extraction-v1A proposal is published only after human review. Reviewers with the same version can verify every quote on their own computer.
Add new chapters
wiki-delta-v1Submit later chapters as delta proposals. Existing content not mentioned in the proposal stays as it is.
Limits
Supported formats and limits
TXT, EPUB, .rpy
Supported file formats.
200
Maximum characters per quote.
128 MiB
Maximum size for one file.
No decryption or circumvention; protected files fail to open.
The toolkit cannot decrypt files, recover keys, or bypass protections, and does not recommend plugins that do. The toolkit and protocol use Apache-2.0 and do not include REZICS AGPL code. No REZICS account is required, and the toolkit works with any compatible server. Examples use only public-domain works or works you have permission to use.
Developers
More pages
- API and SDKSafe retries for writes, with fixed error codes
- MCP serverAI agents connect at /mcp and see tools allowed by their permissions
- Connected appsAuthorize with OAuth and revoke access at any time
- Zone themesCreate a custom layout for a community site
- Open sourceAGPL-3.0 platform, Apache-2.0 standalone packages
Build your tools on one API.
Use your own code to read and write works, library entries, and community data. Every operation follows REZICS identity and authorization rules.