Chief is your AI Chief of Staff, and now has a public API.
If you're building on top of AI and want memory, context, and organizational intelligence without building any of that infrastructure yourself, Chief's API is worth an hour of your time. You can vibe code against it with Claude Code or Codex.
dev.Chief.bot
Most of the AI apps being vibe-coded right now have a ceiling: the model is stateless, has no memory of your actual business, and has never sat in a single one of your meetings.
Chief is different. It's been in every call. It knows your projects, your decisions, your customers, and your patterns — across every transcript, doc, and conversation you've thrown at it.
As of today, that intelligence is programmatically available.
A few things you can now build in an afternoon:
- Your own meeting debrief pipeline. POST a prompt scoped to specific assets or labels, get back a structured Chief response. Wire it into a Slack bot, a Notion page, or a daily email. Done.
- An intelligent RFP or proposal generator. Upload a client brief via the asset upload API, then query Chief to synthesize your internal context against it. Chief will pull from past proposals, decisions, and call history automatically.
- A custom research agent. Set intelligence mode to research, point it at a label (say, "competitor intel"), and run a nightly job that writes a summary back to wherever your team actually reads things. Zero manual effort.
- Context injection into your Claude Code sessions. Pull structured intelligence out of Chief and pipe it into your coding agent's context — your architecture decisions, your product spec evolution, your customer feedback themes. Your coding sessions get smarter because Chief has been paying attention when you weren't.
The API handles chats, multi-turn conversations, asset uploads, and label management. You choose the intelligence mode (fast, expert, or full research) and can preload any of Chief's skills or personas per call. It's async with a clean polling pattern, so it fits naturally into any agent loop.
Coming next week: MCP support, so Chief slots directly into Claude, Cursor, and any other MCP-compatible client as a tool. And Actions management via the API — meaning you'll be able to programmatically create, edit, and trigger Chief's proactive monitoring workflows. Think: your Claude Code session spins up a Chief action that watches for a specific signal and alerts you when it fires.
Our CEO
@DROdio would love to hear about your experience if you try it.