External application setup

The integration contract

An API key authenticates the application. The project App Setup profile controls what a generic colomboai/mc-1 selection means and which MC-1 product families the integration intends to use. Configuration is project-scoped, so rotating a key does not silently change routing behavior.

• Open App Setup in the MC-1 Console.
• Choose Smart Routing or an executable exact model.
• Enable the available MC-1 product families required by the integration.
• Activate the profile, then create or reuse a project API key.

Detect setup before connecting

Call the authenticated setup endpoint only from your application server. Return the non-secret readiness payload to the browser, then open setup_url when setup_required is true. The URL is supplied by the runtime from MC1_CONSOLE_URL; clients must not hardcode the Console hostname.

export async function readMc1Setup() {
  const response = await fetch(`${process.env.MC1_BASE_URL}/app-setup`, {
    headers: { Authorization: `Bearer ${process.env.MC1_API_KEY}` },
    cache: "no-store",
  });
  if (!response.ok) throw new Error(`MC-1 setup check failed: ${response.status}`);
  return response.json(); // Return this non-secret payload from your own backend.
}

Routing behavior

• Smart Routing leaves colomboai/mc-1 logical and selects among eligible model-provider routes per request.
• Exact model replaces a generic MC-1 selection with the saved executable model before policy and provider selection.
• A request that explicitly names another executable model remains explicit and is not overwritten.
• Existing clients that do not perform readiness discovery retain Smart Routing until a profile is activated.

Product configuration

Core, Intelligence FinOps, Agent Identity + Guard, MC-1 Everywhere, and—when deployed—MC-1 Forward are visible in App Setup. The readiness response exposes enabled_capabilities and a configuration_url for every product, so an integration can show only enabled product actions and direct an administrator to the correct Console workflow. Plan, feature, policy, identity, provider, and runtime gates continue to be enforced independently.

API reference