Documint V1 backend for repo-native documentation operations
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"documint-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Documint Documint is a repo-native documentation operations product for teams that ship APIs, SDKs, and MCP servers. The first customer is this repository itself. V1 is deliberately narrow: - Git is the source of truth. - documentation changes happen through commits and PRs, - the public site lives at `documint.xyz`, - the backend detects doc drift and exposes a published-docs MCP surface, - the product is not considered ready until it can keep its own docs current. ## Product surfaces - `/` marketing and positioning - `/docs` published repo-backed documentation - `/app` the authenticated operator console for onboarding, traces, findings, patches, PRs, publishes, and tokens - `/p/:workspace/:project/docs/...` hosted public docs generated from persisted publish deployments ## Stack - `apps/web`: Next.js site and dashboard - `src/documint_mcp`: Python backend, persistent control plane, drift engine, GitHub App integration, and MCP-style API - `content/docs`: published docs content for the self-dogfood project - `alembic`: schema migrations for the control-plane database ## Local development ### 1. Install dependencies ```bash npm install cd apps/web && npm install && cd ../.. python -m pip install -e ".[dev]" ``` ### 2. Create or migrate the database ```bash documint db upgrade ``` For local dogfooding, schema creation and self-bootstrap can also be driven by env flags: - `DOCUMINT_AUTO_CREATE_SCHEMA=true` - `DOCUMINT_AUTO_BOOTSTRAP_DEFAULTS=true` ### 3. Run the backend ```bash npm run dev:api ``` ### 4. Run the site ```bash npm run dev:web ``` The site expects the backend at `http://127.0.0.1:8000` by default. Override with `DOCUMINT_API_URL` if needed. ### 5. Bootstrap the self project explicitly when auto-bootstrap is off ```bash documint workspaces bootstrap-self ``` ### 6. Run the queue worker when `DOCUMINT_JOB_EXECUTION_MODE=queue` ```bash documint worker ``` ### 7. Run the full dogfood smoke loop ```bash npm run dogfood ``` This bo…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.