Integrations — What Cromus Works With
Cromus integrates with your stack in four ways: it compiles governed skills to agent platforms, connects to assistants through a hosted MCP server, reasons about model providers through a verified registry, and exports workflows to open-source frameworks. Every capability listed is shipped.
Skill Studio's Platform Selector compiles a single Cromus SKILL.md to six targets, each with platform-specific validation: Cromus Native, Replit Agent (the .agents/skills/ layout), AgentSkills.io, OpenClaw (ClawHub registry), Claude Managed Agents (Anthropic Agent endpoint config), and Google AI Studio (Gemini API config plus the Interactions API typed-steps template). The governance travels with the artifact; Cromus never sits between your agent and the model.
Cromus runs a hosted, streamable MCP server with nine deterministic tools and zero LLM calls in the diagnostic path — usable from Claude, Claude Cowork, Claude Code, and OpenAI Codex CLI, or any MCP client via OAuth 2.1 (PKCE-mandatory) or a legacy API key with read/score/write scopes.
Cromus reasons about cost across a verified registry of 78 active models from 12 providers (OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral, Meta, Cohere, Amazon, Microsoft, Qwen, and Z.ai), grouped into four ecosystem tiers by setup effort: Mainstream, Managed, Aggregator, and Infra. The Open Workflow Ecosystem exports to LangGraph, CrewAI, AutoGen, n8n, and more, and automation templates cover Zapier, Make, and n8n. The deepest integration is the open-spec contract itself: SKILL.md, ETHOS.md, and MEMORY.md, each with a free public validator. Cromus is upstream of the runtime — it compiles, scores, and governs before execution, and never proxies model calls.