cofounder CLI

Sign in with the CLI, then create a durable company API key with cofounder company api-keys create --name <name>, as declared in integrations.json. The returned cfk_… secret is then sent as Authorization: Bearer <key> to the REST API or exported as COFOUNDER_API_TOKEN for CLI automation. The owner declaration also notes it can be revoked with cofounder company api-keys revoke.

First sign in with cofounder auth login, then run cofounder auth token to print a bearer token, as declared in integrations.json. Use it as Authorization: Bearer <token> for the REST API or directly against the MCP endpoint, or export it as COFOUNDER_API_TOKEN for non-interactive CLI use.

With an admin CLI session, run cofounder company api-keys create --name <name> (POST /cofounder-cli/v1/company/api-keys). The cfk_… secret prints once. Send it as Authorization: Bearer <key> to the REST API, or export it as COFOUNDER_API_TOKEN for the CLI. Keys authenticate as the company that minted them and can be revoked with cofounder company api-keys revoke. Accepted by the REST API and CLI — the hosted MCP endpoint takes OAuth or session tokens instead.

After cofounder auth login, run cofounder auth token (or cofounder auth token --json) to print a Supabase access token for the signed-in user. Send it as Authorization: Bearer <token> to the REST API or the MCP endpoint, or export it as COFOUNDER_API_TOKEN for the CLI. It expires with the session — mint a company API key for durable automation.