iblai-vibe-ops-deploy
/iblai-vibe-ops-deploy
First time here? If
iblai.envhas noARCHITECTURE=, run/iblai-vibe-startfirst (four questions; two minutes) — it decides single-org / multi-org / headless and who signs in, and every skill reads the answer.
Deploy your app's frontend through the ibl.ai platform's hosting API. The
platform holds the Vercel credential for your organization — you need only the
DOMAIN / PLATFORM / TOKEN already in iblai.env. No Vercel account,
no Vercel token, no vercel CLI.
The hosting API is admin-only: what authorises a deploy is the platform API
key your ibl.ai operator issued for the organization — the TOKEN in
iblai.env, sent as Api-Token. A user's own sign-in token is not that key
and every call below answers 403. If iblai.env has no TOKEN, ask the
operator for one rather than substituting a personal token.
Common setup (brand, conventions, env files, verification): see docs/skill-setup.md. Headless twin:
/iblai-api-hostingis the same hosting API as a plain REST reference — every deploy, poll and custom-domain call with its response fields and full error surface.