Reference
Definitions, route inventory, API surfaces, and configuration controls for MARCUS.
The Reference section is where you come when the question is not "how do I use MARCUS today?" but rather "what does this term mean," "which page owns this behavior," or "how is this capability exposed in the product and API?"
What This Section Covers
Glossary
Definitions for the core MARCUS concepts and where they show up in practice.
Page Reference
Route-level map of the public site, authenticated app, and admin surfaces.
API Reference
Practical overview of the main endpoint families, headers, request shapes, and streaming events.
Configuration Reference
Environment variables and configuration groups that most directly shape runtime behavior.
Who Usually Needs Reference
Reference is most useful for:
- support and operations staff
- product and informatics reviewers
- technical leads
- developers integrating with or extending MARCUS
- power users who want precise definitions before using advanced features
How To Use This Section
Use Glossary for vocabulary, Page Reference for navigation and route ownership, API Reference for integration planning, and Configuration Reference for deployment and behavior controls.
If you are new to the product, start in Getting Started or Guides first. Reference works best when you already have a rough mental model and need precision.