Browse docs

Brands

Create brand profiles, run URL analysis, link social accounts, and use brands from chat, MCP, API, or CLI.

Brands store the voice, visuals, and linked social accounts that auto-social.io should follow when generating content.

In the app

  1. Open Brands.
  2. Create a brand with a name and optional website or social URLs.
  3. Link connected accounts from Social accounts. One social account belongs to at most one brand.
  4. Run Analyze so auto-social.io extracts tone, colors, logos, and messaging from your URLs.
  5. Optionally enable weekly refresh (100 credits per run after your first free analysis).

The first brand analysis per user is free. Later manual or weekly runs cost 100 credits each.

What analysis gives you

After a successful run, the brand profile typically includes:

  • Source URLs and linked social accounts
  • Tone and messaging notes
  • Colors and logo assets when found
  • Structured fields you can edit later in the brand detail page

Use Get brand in the UI, or the get_brand agent tool, to read the stored profile. Prefer get_brand over polling analysis unless you just enqueued analyze_brand.

Agent tools

Available on MCP, REST API, CLI, and in-app chat:

ToolPurpose
list_brandsList brands (id, name, slug, account count)
get_brandRead an existing brand profile
create_brandCreate a brand (optional URLs and account links)
update_brandPatch brand fields, URLs, integrations, or refresh settings
delete_brandDelete a brand (sensitive, needs confirmation_code on MCP/API/CLI)
analyze_brandEnqueue async analysis; returns run_id
get_brand_analysis_runPoll a run after analyze_brand only
assign_brand_integrationsReplace social accounts linked to a brand
set_brand_weekly_refreshEnable or disable weekly refresh (day, time, timezone)

Typical agent flow:

  1. create_brand with sourceUrls and/or integrationIds
  2. analyze_brand
  3. Poll get_brand_analysis_run until complete
  4. Later reads use get_brand

See also: Agent guide, MCP server, REST API.