Widget Config - BeforeQuery

The widget calls this endpoint on load to discover server-side configuration. Useful if you’re building a custom UI and need the same runtime flags.

GET https://api.agents.beforequery.com/api/v1/public/projects/:projectId/widget-config

curl https://api.agents.beforequery.com/api/v1/public/projects/proj_xxx/widget-config \
  -H "X-Client-Key: bq_pk_..."

Response

{
  "project_name": "Acme Docs",
  "captcha_required": true,
  "recaptcha_site_key": "6Lc...",
  "hide_branding_allowed": false
}

Field	Type	Description
`project_name`	`string`	Display name — the widget uses it in the header and placeholder when no `data-product-name` is set
`captcha_required`	`bool`	Whether this client key enforces reCAPTCHA v3; when `true`, chat requests must include a token (see Authentication)
`recaptcha_site_key`	`string`	Site key to render the reCAPTCHA v3 challenge client-side
`hide_branding_allowed`	`bool`	`true` only for enterprise-plan workspaces — gates the widget’s `data-hide-branding` option. On other plans the “Powered by BeforeQuery” footer stays visible even if the attribute is set

Fetch widget-config on load.
If captcha_required, load reCAPTCHA v3 with recaptcha_site_key and obtain a token before each chat call (X-Captcha-Token header, or captcha_token on WebSocket frames).
Respect hide_branding_allowed when deciding whether to show attribution.