Endpoints Reference
44 Endpoints
| Method | Endpoint | What It Does |
|---|---|---|
Core |
||
GET |
|
Health check — document counts, system status |
GET |
|
Repository metrics — 1,855 pages across 20 categories |
GET |
|
127 antora.yml attributes — single source of truth |
Content — Pages & Search |
||
GET |
|
List pages with category and type filtering |
GET |
|
Full page content, metadata, and include directives |
GET |
|
Full-text search across 3,486 files with ranked results and context |
Standards & Governance |
||
GET |
|
All 20 standards with STD-NNN identifiers and lifecycle status |
Projects |
||
GET |
|
All projects with compliance metadata |
POST |
|
Scaffold project per STD-001 |
PATCH |
|
Update project status in metadata partial |
Case Studies |
||
GET |
|
Operational records across 5 types (incidents, changes, RCAs, deployments, TAC) |
GET |
|
Filter by type — list incidents, changes, RCAs, deployments, TAC |
GET |
|
Full case study content |
POST |
|
Create incident report per STD-011 |
POST |
|
Create change request per STD-005 |
POST |
|
Create root cause analysis per STD-010 |
Skills |
||
GET |
|
All Claude Code automation skills with frontmatter |
GET |
|
Skill detail — the full SKILL.md content |
Worklogs |
||
GET |
|
Daily worklogs, filterable by year and month |
GET |
|
Specific worklog by date |
Knowledge Systems |
||
GET |
|
Pattern Journal organized by Aristotelian taxonomy |
GET |
|
Patterns in a specific domain (security, ai, networking) |
GET |
|
CLI reference library — 17 categories with page counts |
GET |
|
Entries in a category (bash, vim, git, awk) |
GET |
|
AI collaboration session captures |
Education (44% of site) |
||
GET |
|
808 pages across certifications, training, literature, math |
GET |
|
Subcategory listing |
Portfolio & Reference |
||
GET |
|
77 project entries across 12 categories |
GET |
|
Commands, diagrams, math, music, systems |
GET |
|
Subcategory listing |
Infrastructure |
||
GET |
|
ISE, Vault, pfSense, WLC, Keycloak, OpenAI API docs |
GET |
|
Vendor-specific API documentation |
GET |
|
Operational procedures and guides |
GET |
|
Strategic goals, certifications, career |
Meta & Tracking |
||
GET |
|
Strategic systems, velocity metrics, retrospectives |
GET |
|
Progress dashboards and task tracking |
GET |
|
20 document type templates |
GET |
|
Work in progress documents |
GET |
|
Micro-learning captures |
Reusable Content |
||
GET |
|
1,135 reusable content blocks by category |
GET |
|
Specific partial content |
GET |
|
496 code files across 21 categories |
GET |
|
Specific example file content |
Graph Analysis |
||
GET |
|
Backlink analysis — who links to this page? |
40 read endpoints. 4 write endpoints. 44 total. Every content category in domus-captures has a dedicated endpoint. Every write operation produces files that comply with the same standards a human would follow. The API does not bypass governance — it enforces it.