Use your brand's data with AI agents
Let an AI agent such as Claude answer questions about your brand's creators, videos, campaigns and pay, or read the same data with the Bloss API. Scale plan.
You can let an AI agent, such as Claude, read your brand's data and answer questions about it in plain language: how this week went, who's behind on posting, how much of a budget is left. If you write code, you can read the same data through the Bloss API instead. Both are read-only: nothing in your brand can be changed through them.
Both need the brand to be on the Scale plan. See What you need.
What you can ask
Here are some questions an agent can answer, and the data it reads to answer them.
| Ask | The agent reads |
|---|---|
| "How did we do this week?" | The current payout cycle, the videos and views for it, day by day, and the week's top and quiet creators. |
| "Which creators haven't posted in the last 7 days?" | Your roster, your posting cadence from SettingsRules, and each creator's views per day and posting compliance. |
| "How are the creators on trial doing?" | Each creator's trial progress: qualifying videos so far and days left. |
| "Which tags bring the most views?" | Your tags with their stats, as on the Tags page. |
| "What were our ten most-viewed videos in September?" | Your videos as the Video Vault lists them, with views and the set each belongs to. |
| "Any new recruitment applications or support tickets?" | Applications from your recruitment page and the tickets creators sent you. |
| "How much have we spent on the September and October cycles, and how much of the 5,000 USD budget is left?" | Campaign spend (base pay plus the CPM bonus) for those cycles, against the budget you give it. Full admins only. |
| "What do we still owe creators for this cycle?" | The cycle's totals and each creator's payout in it. Full admins only. |
| "What's waiting in the Base pay queue?" | Sets waiting for instant base pay review. Full admins only. |
The agent can only read. It can't pay, approve, invite or change a setting. Do those in Bloss.
What you need
- The Scale plan. The brand must be on Scale. On another plan, the agent doesn't get brand tools, and API requests about the brand answer
plan_required. The agency owner changes the brand's plan in agency billing. See Plans and features. - Brand admin access. You need to be a brand admin, full or limited, to use your own token. Creating a brand key needs a full admin.
- An AI agent that supports MCP, such as Claude Code or Cursor, or your own code for the API.
Who can see pay data
Full admins onlyPay rules, payouts, campaign spend, the Base pay and Bonus pay queues, referral payouts and funds are money data:
- Full admins can read them, if the token or key has a permission marked Money data.
- Limited admins can't. The agent answers that it needs a full admin, even if the token has the money permissions. Everything else, from creators to campaign reach, works for limited admins. See Full vs limited admins.
- The brand's subscription is visible only to the agency owner, as on the agency's Billing page.
Leave the Money data permissions unticked for an agent that doesn't need pay figures.
Your own token or a brand key
You can connect with either.
| Your API token | A brand key | |
|---|---|---|
| Belongs to | You | The brand |
| Reads | Every brand you administer on Scale, or only those you pick, plus your own creator data | This brand only |
| Sees pay data | If you're a full admin and it has the Money data permissions | If it has the Money data permissions |
| Stops working | When you revoke it, it expires, or you lose admin access | When it's revoked or expires |
| Create it in | AccountAPI tokens | SettingsIntegrationsAPI Keys |
- Use your own token for your own AI agent or scripts, and when you look after several brands. It reads as you, so it never sees more than you do.
- Use a brand key for something that belongs to the brand rather than to a person: a client dashboard, a shared reporting script, a team assistant. It keeps working when people join or leave the team.
Set it up
Create a token or a key
Your own token: go to AccountAPI tokens and click Create token. Tick Your account: name, email, roles and memberships, then what you need under Brand (Scale plan), for example The brand's creators and their profiles, The brand's videos, sets and tags and The brand's analytics and exports. Add Payout settings, cycles and payouts if you're a full admin and want pay figures. See API tokens.
A brand key: go to SettingsIntegrationsAPI Keys and click Create key. Tick the permissions under Creators and content, Brand and workspace and, if needed, Money. See Brand keys.
Either way, it's shown only once, in the window that opens after you create it.
Connect your agent
In the window that shows your new token or key, pick your app under Connect an AI agent (MCP): Claude Code, Cursor, VS Code, Claude Desktop or another. The setup already includes the token or key, so you copy one command or click Add to Cursor or Add to VS Code. Full steps: AI agents (MCP).
Ask away
Ask a question about your brand, like the ones above. If you look after several brands, name the one you mean.
Prefer code?
The same data is available from the Bloss API, so you can pull it into a spreadsheet, a client report or your own dashboard. See Brand API. If you already use the Campaign API, it keeps working; the Brand API reads the same campaign numbers and much more.
Stay in control
- It can't change anything. No paying, approving, inviting or editing settings through an agent or the API.
- It sees only what you allow. A token reads only the permissions you ticked, and never more than you can see in Bloss. A brand key reads only its own brand.
- Payout details stay masked. Even with money permissions, full payment details never appear.
- Turn it off any time. Revoke the token in AccountAPI tokens, or the key in SettingsIntegrationsAPI Keys, and access stops right away.
Related
Last reviewed Oct 23, 2026