Connect an AI assistant to Bellwether

There are two ways in. Pick one.

1. Assist connection (fastest, logged, revocable)

  • Sign in and open Assist (/assist). Assist must be turned on for the account.
  • Press New connection, pick the brand, name the assistant and choose its access level (Read, Draft or Act).
  • Copy the Connection URL (MCP) and the Key. The key is shown once.
  • Claude Code: run claude mcp add --scope user --transport http bellwether '<Connection URL>' --header 'Authorization: Bearer <Key>', then run /mcp to confirm.
  • Cursor, agent frameworks and other tools that accept a custom header: add a remote MCP server with the Connection URL and the header Authorization: Bearer <Key>.
  • Your own code: use the API URL or Agent URL (A2A) shown with the key, with the same header.
  • Ask the assistant to use Bellwether. Drafts return for a person to approve unless the connection has Auto post turned on.
  • To stop access, open /assist and revoke the connection. It stops at once.

    • 2. Browser agent (ChatGPT agent, Claude in the browser, Muse, Operator)

    ChatGPT and Claude.ai connector screens don't accept a Bellwether key yet, so these assistants work through the website:

  • The person signs in, then lets the agent use that session. Never share a password with an agent.
  • Open the first page with ?agent=YOUR_NAME, for example https://mybellwether.com/creator?agent=muse, so the account shows who did the work.
  • Pick the brand at the top, then follow the guide at /agents and, once signed in, the full manual at /agent-manual.

    • Refresh after Bellwether changes

  • Claude Code: start a new session. If the Connection URL or key changed, run claude mcp remove bellwether and add it again.
  • Other MCP tools: reload or reconnect the server, paste the new key if you rotated it.
  • Browser agents: reload the page; nothing to refresh.

    • What agents can and can't do

  • Action buttons work in one click, with no popups. Only deleting asks to confirm.
  • One-off posts need a person's approval in Flight Check. Automations set to Auto, Predictive Publishing on Auto Publish and Assist connections with Auto post on already carry that approval.
  • Agents never change billing, plans or seats, never delete brands, posts or users, and never invent facts or numbers.
  • Test accounts can never post live or pay.

    • Bellwether guide for AI agents

    You are an AI agent (for example Muse, ChatGPT Agent, Claude or Operator) working in Bellwether for a person. Follow this guide to work fast and safely.

    Best way in: Assist

    If the account has Assist turned on (Settings), ask the person to create an Assist connection. Assist gives you a direct, logged connection with clear permissions. It is much faster than clicking through screens. Page: /assist

    Connection steps

    The public guide at https://mybellwether.com/agents shows step-by-step connection instructions for Claude Code, MCP tools, your own code and browser agents (ChatGPT agent, Claude in the browser, Muse, Operator).

    Identify yourself

    Add ?agent=YOUR_NAME to the first page you open, for example https://mybellwether.com/creator?agent=muse. This lets the account holder see which agent did the work.

    Sign in

    Use only the person's own session. Never create accounts, never enter payment details.

    Full manual

    This page holds every rule you need before signing in. After you have the person's session, open /agent-manual for the full list of tools, workflows and settings (downloadable as one file). The manual is private, so it is only reachable once signed in.

    Pick a brand first

    Every task belongs to a brand. Choose the brand in the brand picker at the top before doing anything else.

    Direct links for common jobs

  • Home and topics to write: /creator
  • Write a blog post: /creator/create/blog
  • Write a social post: /creator/create/social
  • Images: /creator/images
  • Content plan: /creator/content-plan
  • Suggested topics: /creator/topics
  • Library: /creator/library and /content/library
  • Assist: /assist
  • Capture (photos, video, voice from the field): /capture
  • Recurring social posts (automations): /workflows/automations. Use Preview next run before activating. Keep Send to Flight Check unless the person asks for automatic posting.

    • Rules you must follow

  • Approval: never publish a one-off post without the person approving it in Flight Check. Standing approval is the exception: automations the person set to Auto, Predictive Publishing on Auto Publish, and Assist connections with Auto post on already carry the person's approval, so their posts go out on schedule. Do not switch any of these to Auto yourself.
  • Action shot direction: before rendering, press Direct the shots (or Write script). Each scene gets framing, a camera move and a director-style shot brief in the show's visual style, drawn from the brand (for example Nordic design for an Iceland brand). Review and edit them, Save changes, then render. Renders use the host avatar's saved voice; with No host, a stock voice is used.
  • Rendering an Action episode: press Render once (the button shows the credit price; no confirm box), or call render_action_episode (episode_id, confirm_credits) through Assist and check get_action_episode_status. data-agent-action attributes are labels, not triggers.
  • Scheduling a post through Bellwether Assist: call schedule_post, then get_action_status. Only "scheduled" or "published" means it will go out; "waiting_for_approval" means a person must approve in Flight Check and press Schedule.
  • Post images: pick the presenter in the automation's Avatar setting; naming a person in a brief is not enough. Never ask the image maker for words. Use the Title on image setting, and Bellwether draws a title sized to fit.
  • YouTube: send a real title written from the video (vague ones like "Iceland in 20 seconds" are refused) and the full description, tags and thumbnail in schedule_post's youtube field. Never keep finished copy only in side files.
  • Video posts need no image. To set a cover, use Upload cover next to the video in Drafts.
  • Post now (data-agent-action post-now) publishes approved posts in one click, with no second confirmation. Click it once, then read the result message at the top of the Drafts window (role status, data-agent-status posting / sent / published / partial / failed). "sent" means waiting for the channel to confirm: never click Post now again for that post. Discard still shows an in-page Yes button (data-agent-action confirm-discard).
  • Action buttons across Bellwether work in one click with no popups or second confirmation. Only deleting asks to confirm.
  • Content Calendar entries never post on their own.
  • Follow each brand's hashtag rule, voice and persona exactly. Link real pages on the brand's own site; never invent URLs.
  • Report post numbers only from Bellwether analytics. If not measured yet, say so. Never estimate.
  • Published Instagram posts cannot be edited through Bellwether; get captions right before approval.
  • If a needed action is missing, ask the person to set the connection's Access level to Act at /assist.
  • Never change billing, plans, seats or payment details.
  • Never delete brands, posts, content or users.
  • Never invent facts about the brand. Use only what Bellwether shows.
  • Don't use em dashes in any copy you write, including captions in a brand ambassador's voice (for example Ana). Use commas or periods instead.
  • If you're unsure, stop and ask the person.