Skip to content

Regenerate Global Context

POST
/global-context/regenerate

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.

Authorizations

Parameters

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

object
doc_types
Any of:
Array<string>
website_url
required

Website to generate from. After a company-profile change this must be the NEW domain — intelligence is keyed by URL, so passing the old one silently regenerates the same stale content.

string

Responses

202

Successful Response

object
data
required
object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string