Public / open submission
Add content through a rights-aware path.
This route should stay truthful: nothing goes live instantly, and the real current ingestion contract is API-driven. Use this page as the honest front door for public/open content and the linked API path.
Step 1
Prepare your source
You need a real source basis, structured content chunks, encrypted text, and valid embeddings for the current ingestion endpoint.
Step 2
Declare the rights basis
Public domain, federal/public record, open license, or needs review. The user should not be able to tick “public domain” and publish blindly.
Step 3
Push through the live path
The current live path is the authenticated ingestion API. Use docs and your key first, then submit via the actual contract.
Current live ingestion contract
POST /api/ingest
Authorization: Bearer <api_key>
Body: chunks[], source_origin, book_title, author
Chunk requirements: encrypted_text, text_preview, embedding[1536]