What warming does

A fresh workspace starts empty. Warming gets it to a usable baseline:

• Backfills the business profileif it’s missing — the same web-discovery that powers Business Profile.
• Regenerates author voices so content has a voice to write in.
• Checks the bootstrap canon gate — the workspace needs a brand voice, content pillars, and at least one author before composition is fully unlocked.

It’s idempotent — warming an already-warm workspace is a no-op, so you can safely run it again any time.

In the app

The Home Setup checklistis the human-facing view of warming. It shows what’s still needed — a connected data source, brand voice, a content pillar, an author — and each item deep-links straight to where you complete it.

You don’t have to drive it by hand: warming also runs automatically in the backgroundwhen you’re on the workspace pages, so the checklist fills itself in as discovery and voice generation complete. The checklist is just the progress you can see.

Over the API

Warming is a single REST call under /api/context-library. Authenticate with the X-API-Key header (see Using the API).

POST …/warmtriggers a warm pass and returns what it kicked off. It’s idempotent — call it on a fresh workspace to get things going, or again later with no harm.

curl -X POST \
  https://app.amdahl.co/api/context-library/b1f4c2a0-7e3d-4a59-9c81-2f6e0d5a8b14/warm \
  -H "X-API-Key: amdahl_sk_live_your_key_here"

{
  "triggered": {
    "businessProfile": "discovering",
    "authorVoices": "regenerating"
  }
}

To see what’s still outstanding — the same items the Home checklist shows — read the setup status:

curl https://app.amdahl.co/api/platform/v1/console/setup/status \
  -H "X-API-Key: amdahl_sk_live_your_key_here"

From an MCP agent

There’s nothing to call. Warming happens automatically when an agent connects — there is no warm tool on the MCP surface. By the time an agent is working in a workspace, the business profile and author voices are already being filled in for it.

If an agent wants to see whether the workspace is ready, it reads the workspace context the usual way — the context tool’s summary action folds in the business profile, and the business_profile:// resource exposes the profile record directly. Setting any of it up, though, is a human / REST job, not an agent action.