Regenerate Global Context

Regenerate Studio (Global Context) documents against a website.

Why this exists. Studio docs are generated once at onboarding from the company profile's website. If that profile was wrong at the time — the common case for self-serve orgs, which seed graph8's own profile when no domain is given — every downstream ICP, persona, TAM and campaign is built on the wrong company, and there was no machine path to fix it:

• the internal POST /global-context/generate-all refuses forever once the first pipeline completes (409 ... Contact support to reset and regenerate);
• POST /global-context/generate/{doc_type} has no such lock but was JWT-only, so an agent or API key could not call it.

This endpoint wraps the per-document path, which means it is not subject to the one-shot pipeline lock and can be run whenever the source of truth changes.

Requires intelligence data for website_url to exist already — run the intelligence analyze step first for a newly-changed domain, otherwise this returns 404 rather than regenerating stale content.