What’s in it

The profile is one structured record per workspace. It captures the company and its market so every downstream surface starts from the same picture instead of re-deriving it:

• Company — company name, industry, and sub-industry.
• Who you sell to — your ideal customer profile (ICP) and the content themes that matter to them.
• Competitors— each with a name, a short description, how you differ, and the content leaders they’re known for.
• Where your market lives — industry keywords, the communities and media your buyers read, and the must-follow leaders in your space.

It’s auto-discovered: from just your company name and domain, Amdahl runs web research to fill the profile in. Then it’s yours to edit, and your edits are preserved — a later re-discovery enriches the gaps without overwriting what you changed by hand.

In the app

Open Settings → Business Profile. It’s an accordion editor — each section (company, ICP, competitors, keywords, communities) expands to edit in place. The first time you open it on a fresh workspace it kicks off discovery automatically and shows a discovering… status strip while the web research runs; the fields fill in as it completes.

Already have a profile but it’s gone stale? Hit Refresh from the webto re-run discovery. It re-researches the company and tops up the profile, leaving anything you’ve hand-edited intact.

Over the API

The profile is a REST surface under /api/context-library/:businessId/business-profile. Authenticate with the X-API-Key header (see Using the API).

Read the profile

GET …/business-profile returns the current profile record.

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

{
  "companyName": "Acme",
  "industry": "B2B SaaS",
  "subIndustry": "Revenue intelligence",
  "icp": "Series A–C GTM teams, 20–200 reps, data-rich CRM + call corpus.",
  "contentThemes": ["pipeline hygiene", "rep productivity"],
  "competitors": [
    {
      "name": "Northwind",
      "description": "Enterprise revenue platform",
      "differentiator": "Enterprise-first, slow to ship",
      "knownContentLeaders": ["J. Rivera"]
    }
  ],
  "industryKeywords": ["revenue intelligence", "conversation analytics"],
  "mustFollowLeaders": ["A. Chen"]
}

Edit the profile

PUT …/business-profile replaces the record with the body you send. Your edits stick — a later refresh enriches missing fields without clobbering them.

curl -X PUT \
  https://app.amdahl.co/api/context-library/b1f4c2a0-7e3d-4a59-9c81-2f6e0d5a8b14/business-profile \
  -H "X-API-Key: amdahl_sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "companyName": "Acme",
    "industry": "B2B SaaS",
    "icp": "Series A–C GTM teams, 20–200 reps, data-rich CRM + call corpus."
  }'

Discover from the web

POST …/business-profile/refresh kicks off web discovery and returns immediately. Poll GET …/business-profile/status while it runs, then read the profile back when it reports done.

# Start a (re)discovery
curl -X POST \
  https://app.amdahl.co/api/context-library/b1f4c2a0-7e3d-4a59-9c81-2f6e0d5a8b14/business-profile/refresh \
  -H "X-API-Key: amdahl_sk_live_your_key_here"

# Poll while it's discovering
curl https://app.amdahl.co/api/context-library/b1f4c2a0-7e3d-4a59-9c81-2f6e0d5a8b14/business-profile/status \
  -H "X-API-Key: amdahl_sk_live_your_key_here"

{ "status": "discovering" }

Not sure of the exact route or input shape? Call /api/platform/v1/operations — it returns the catalog of every operation your key can call, each with its JSON schema.

From an MCP agent

Over MCP the profile is read-only. An agent reaches it two ways:

• The context tool’s summaryaction — it folds the business profile into the workspace’s context summary, so an agent gets company, ICP, and competitors in one call before it drafts or researches.
• The business_profile:// resource — read the profile record directly the same way an agent reads any other resource URI.

Editing is console + REST only. Writing the profile is deliberately noton MCP — the company profile is workspace configuration that shapes every agent’s context, so a human (or a REST integration) sets it, and agents read it. Discovery is the one write that runs on its own: it happens automatically when a profile is empty, no tool call required.