Create a knowledge hub from websites

Creates the hub immediately with status processing and enqueues the build: every website is crawled (subpages too where includeSubPages is true), the content is synthesized into knowledge pages, and a company name — and, when name was omitted, the hub name — are generated. Poll GET /business/knowledge-hubs/{hubId} until status is complete; draft means the build did not finish — it exhausted its retries (hubs saved as drafts in the web app carry the same status without ever having been built). Until the build finishes a hub created without a name carries the placeholder "Processing...", and websites lists only what you sent — the crawler's subpages appear later. Building does not debit credits. Inline file attachments are not accepted here: add them per note via POST /business/knowledge-hubs/{hubId}/attachments once the hub is complete. A team holds one knowledge hub, shared by everyone on it: this answers 409 KNOWLEDGE_HUB_ALREADY_EXISTS while your team's is processing or complete, and the hub it creates is always your default one (isDefault in the body is ignored). A draft hub does not count: creating a hub replaces it as your default.

Errors:

• 409 KNOWLEDGE_HUB_ALREADY_EXISTS — Your team already has a knowledge hub that is built or building, and a team holds one. Add to it with PATCH /business/knowledge-hubs/{hubId} instead.
• 422 VALIDATION_FAILED — The body failed validation locally, or a website URL the crawler cannot parse was rejected by the builder.
• 500 UNEXPECTED_ERROR — The build workflow could not be enqueued (upstream STATE_MACHINE_ERROR); no hub was created — retry.
• 429 RATE_LIMITED — More than 30 knowledge-hub/campaign requests in a minute (or 1000 in a day). Knowledge hubs share the campaigns bucket.

Requires one of the following token scopes: campaigns.