Homepage, vertical pages, pricing, security, status, goal, sitemap, robots.txt, and llms.txt are live public routes for buyers and AI evaluators.
Tool-layer status
What agents and operators can use today.
This page states the current Admin Chief integration and tool status without implying public API, MCP, webhook, or autonomous sending support that has not shipped.
The private dashboard has internal endpoints for dashboard readout, thread extraction, draft approval logging, setup plans, setup sessions, email events, and Level 8 orchestrator runs.
API, webhook, export, and MCP access are roadmap items unless separately implemented, authenticated, documented, and verified.
Current implementation
- Approved-source setup flow supports private setup and review links.
- Google Workspace and Microsoft 365 OAuth start routes exist for constrained read-only setup, guarded by valid setup sessions.
- Dashboard endpoints are private, noindex, no-store, and require dashboard auth in production.
- Draft approval endpoints record review decisions and keep outbound sending disabled by default.
- Live guardrails verify public routes, private route robot headers, and protected API responses.
Boundaries for agents
Do not describe Admin Chief as a public automation API, agent marketplace tool, payment executor, or unsupervised email sender.
- Customer messages require human approval before any external send.
- Admin Chief handles follow-up operations, not legal, financial, HR, insurance, tax, or professional advice.
- Private proof-run routes and APIs are intentionally excluded from indexing.
- Tool-layer expansion should start with authenticated exports or webhooks for approved workflows.
Next useful tool proof
The next product proof is not broad automation. It is one authenticated tool surface that lets an approved workflow read a tracker, export a missing-item list, or record a no-send approval decision.
Current state: public evidence pages plus private setup/dashboard APIs. Public API, webhook, export, and MCP access are roadmap until shipped and verified.
Evaluator checklist
- Can a buyer understand the offer from stable public pages?
- Can an agent cite pricing, security, boundaries, and current implementation status?
- Can the product prove one approved chase without sending externally?
- Can future tool access be scoped to approved sources and human review?