LAB TOPIC / API DESIGN
API design connects your vocabulary to the software that uses it. Explore stable IDs, predictable fields, versioning, and explicit failure states. Start with the foundations guide, then compare how different domains adapt the same contract to their own context.
4 CONNECTED ARTICLES
Imagine two teams exchanging topic assignments without sharing the same code. Use the design articles to decide which values both teams must interpret identically: concept identifiers, document revisions, vocabulary releases, and result states. Ask how the receiving team would reconcile a partially successful batch or distinguish a deliberate reclassification from a duplicate request. Document those answers before inventing additional endpoints.
Then review the contract through a change scenario. A display label is corrected, a concept is split, or an input document is replaced. Which change preserves the old assignment, and which needs new evidence? The schema and domain guides offer concrete examples for that discussion. Finish with one readable success record, one valid empty result, and one review case, each paired with the action its consumer should take.
Prediction coverage needs careful boundaries between the subject, the statement, and its time horizon. Build a document contract that preserves uncertainty and provenance without presenting extracted labels as forecasts or probabilities.
Read the article : Design Prediction Topic Contracts Without Inventing Forecasts
Valid JSON is the first check in a longer workflow. Design topic extraction around an allowed vocabulary, verifiable evidence, explicit outcomes, document revisions, and validation that connects a generated label to its source.
Read the article : LLM topic extraction: a JSON contract you can actually validate
Financial document labels need more than company names. Separate the document type, entities, reporting periods, and evidence so readers can find relevant material without confusing topic classification with a financial conclusion.
Read the article : Classify Financial Documents Without Losing Entity and Time Context
Build a topics API contract that readers, editors, and developers can understand. Explore stable identifiers, evidence, uncertainty, document revisions, and vocabulary changes through practical examples for content classification.
Read the article : Topics API design: IDs, labels, and useful JSON contracts