# Blog: brand marketing, leads and distribution at scale

Practical guides for agencies: one brand voice, per-account lead measurement, client approvals and posting at scale without getting blocked.

- [From Client Brief to Published Posts: A Full Week Run by an Agent, Call by Call](https://shager.ai/en/blog/from-brief-to-published): A worked example of one client week through Shager: brief, media upload, per-account drafts, review, client approval, scheduling, delivery checks and reporting.
- [How Should an AI Agent Handle Holidays When It Posts for Many Different Audiences?](https://shager.ai/en/blog/holiday-aware-posting-for-agents): How an AI agent should schedule around holidays: map each account to its traditions, call get_holidays, read calendar_notes and block the evening before.
- [The Agent Content Pipeline, End to End: Brief In, Per-Account Posts Out, Clicks Back, With Every Shager Call in Order](https://shager.ai/en/blog/agent-content-pipeline-end-to-end): A full agent pipeline on Shager in TypeScript: brief, media, per-account captions, draft, client approval, staggered scheduling, delivery checks and clicks.
- [First-Comment Lead Links With Agents: One Tracked Link per Account, Posted Right After the Post](https://shager.ai/en/blog/first-comment-lead-links-with-agents): How an agent uses Shager's first comment and per-account tracked links for leads: where links work on each network, which fields to set and how to measure it.
- [Posting at Scale Without Getting Blocked: Pacing, Variety and Original Content](https://shager.ai/en/blog/avoid-spam-blocks-when-posting-at-scale): How agencies publish to dozens of accounts without restrictions: official APIs, staggered pacing, original content per account, and the networks' own rules.
- [How to Choose a Distribution Platform for AI Agents: 12 Criteria](https://shager.ai/en/blog/choosing-a-distribution-platform-for-agents): Twelve criteria for choosing a social distribution platform an AI agent can run: MCP and API access, scoped keys, audit, per-account variation and pricing.
- [Multilingual Content Agents: Localising for Hebrew, Arabic and English Accounts Without Translating](https://shager.ai/en/blog/multilingual-content-agents): Running content in several languages with AI agents: localisation versus translation, Hebrew and Arabic right-to-left pitfalls, and per-account captions.
- [A Weekly Distribution Routine as a Claude Skill: Monday Drafts, Client Approvals, Friday Click Report](https://shager.ai/en/blog/skill-weekly-distribution-routine): A Claude Code skill that runs an agency week in Shager: drafts from plan files, client approvals, scheduling only what's approved, and a Friday click report.
- [Making a Website Agent-Ready: llms.txt, Markdown Pages, OpenAPI, api-catalog and MCP Server Cards](https://shager.ai/en/blog/agent-ready-websites-llms-txt): What an agent-ready website publishes: llms.txt, Markdown page versions, OpenAPI, the RFC 9727 api-catalog and an MCP server card, with shager.ai as example.
- [API Keys for Agents: Read, Write, Publish, and an Audit Trail You Will Actually Check](https://shager.ai/en/blog/api-keys-scopes-and-audit): Giving AI agents Shager API keys safely: what read, write and publish allow, the sandbox claim, key storage, rate limits, key rotation and the audit log.
- [Build a Claude Skill for Shager: SKILL.md, Folder Layout and the Rules That Make Multi-Account Posting Repeatable](https://shager.ai/en/blog/build-a-claude-skill-for-shager): Package Shager distribution as a Claude Agent Skill: frontmatter that triggers well, reference files, a REST helper script, and where the skill should live.
- [A Client Approval Workflow That Doesn't Stall Your Content Calendar](https://shager.ai/en/blog/client-approval-workflow-for-agencies): How agencies build client approvals that work: what needs sign-off, clear deadlines, approval links instead of email threads, and rules for silent clients.
- [MCP Explained for Marketers: What It Is and Why Your Tools Need It](https://shager.ai/en/blog/mcp-explained-for-marketers): A plain-language guide to the Model Context Protocol for marketers: what MCP is, what servers and tools mean, how agents use them, and what to ask vendors.
- [One Agent, Twelve Clients: Keeping Brands, Accounts and Links From Bleeding Into Each Other](https://shager.ai/en/blog/one-agent-many-clients): How an agency runs one AI agent across many clients in Shager: a workspace per client, per-client context folders, naming rules and guards against cross-posts.
- [Per-Account Lead Attribution: UTMs, Short Links and the First Comment](https://shager.ai/en/blog/utm-per-account-lead-attribution): A practical guide to attributing leads to each page and profile: a consistent UTM scheme, one short link per account, first-comment links, and CRM handoff.
- [The Weekly Client Report, Written by an Agent Every Monday Before You Wake Up](https://shager.ai/en/blog/weekly-client-report-by-agent): Build a weekly client report that an agent compiles from Shager: what was published, what failed, clicks per account and post, and how to join it to CRM leads.
- [Client Connect Links: Access to Client Social Accounts Without Passwords](https://shager.ai/en/blog/client-connect-links): How agencies get publishing access to client Facebook, Instagram and YouTube accounts with a connect link: no shared passwords and no Shager account needed.
- [Keeping One Brand Voice Across Dozens of Social Accounts](https://shager.ai/en/blog/brand-consistency-across-many-accounts): How agencies managing dozens of pages and profiles keep one consistent brand voice without duplicating posts: style guides, templates, groups and QA.
- [Six Prompts That Make a Content Agent Safe to Run on Client Accounts](https://shager.ai/en/blog/prompts-for-a-content-agent): Copyable prompts for an AI content agent working through Shager: standing rules, weekly drafts, caption variation, scheduling, review and failure triage.
- [Shager REST API Quickstart: From a Fresh Key to a Tracked Post on 40 Accounts in Seven Calls](https://shager.ai/en/blog/shager-rest-api-quickstart): A working tour of Shager's REST API in curl and TypeScript: auth, workspaces, channels, media, per-account drafts, scheduling, status checks and clicks.
- [Scheduling Strategy for Agents: Time Zones, Staggering and Not Flooding Forty Pages at 9:00](https://shager.ai/en/blog/scheduling-strategy-for-agents): How an AI agent should schedule posts across many accounts: ISO 8601 offsets, time zones and DST, stagger math, splitting groups across days, and safe cancels.
- [Caption Variation per Account: Letting AI Rewrite Without Losing the Brand](https://shager.ai/en/blog/caption-variation-per-account-with-ai): How an AI agent can write a different caption for every account in a campaign while claims, offer and voice stay fixed, using per_channel in one create_post.
- [One Vertical Video, Forty Accounts: How an Agent Ships Reels and Shorts Through Shager](https://shager.ai/en/blog/agent-short-video-distribution): A hands-on playbook for agents distributing short video: format checks, Reels and Shorts metadata, per-account captions, staggered dispatch and real MCP calls.
- [Agent Self-Signup: How an AI Agent Opens a Shager Sandbox in One Call, and Why a Human Still Holds the Publish Button](https://shager.ai/en/blog/agent-self-signup-and-claim): An agent can open its own Shager sandbox with one POST. Here is the call, what the sandbox allows, the human claim step, and how publish rights get granted.
- [Safety Rules for AI Agents Posting to Hundreds of Accounts](https://shager.ai/en/blog/safety-rules-for-agents-posting-at-scale): A rulebook for AI agents publishing to many social accounts: official APIs, scoped keys, varied captions, staggered dispatch, network limits and a stop plan.
- [Can ChatGPT Post Through Shager? What Works Today, What Waits for OAuth, and the Three Routes That Ship Now](https://shager.ai/en/blog/shager-and-chatgpt): ChatGPT's MCP connectors need OAuth or no auth, so Shager's API-key server can't plug in yet. Here are the routes that work today and what OAuth will change.
- [Measuring Leads From Agent-Published Content, Account by Account](https://shager.ai/en/blog/measuring-leads-from-agent-content): How to tell whether agent-published posts produce leads: per-account short links and UTMs, campaign labels, get_analytics, CRM hidden fields and a weekly read.
- [Add Shager to Cursor With .cursor/mcp.json: Turn Release Notes Into Drafts for Every Client Account](https://shager.ai/en/blog/connect-shager-to-cursor): Configure Shager's remote MCP server in Cursor with a url and an env-backed Authorization header, then turn a changelog into per-account social drafts.
- [Human Approval for Agent-Written Posts: Where to Put the Gate](https://shager.ai/en/blog/human-approval-for-agent-posts): Where human approval belongs when an AI agent writes and schedules social posts: scoped keys, draft-first runs, client approval links and what reviewers check.
- [Shager in OpenAI Codex: config.toml, bearer_token_env_var and a Tool Allowlist That Keeps Drafts as Drafts](https://shager.ai/en/blog/connect-shager-to-codex): Set up Shager's remote MCP server in Codex CLI via config.toml or codex mcp add, read the key from an env var, restrict tools, and create a first draft.
- [The Agency Operating Model When AI Agents Handle Distribution](https://shager.ai/en/blog/agency-operating-model-with-agents): How a social agency restructures roles, weekly rhythm, client workspaces and API keys when AI agents do distribution and people own strategy and approval.
- [Connecting Shager to Claude Desktop: Custom Connector With Request Headers, or the mcp-remote Route](https://shager.ai/en/blog/connect-shager-to-claude-desktop): Two working ways to connect Claude Desktop to Shager's API-key MCP server: a custom connector with request headers, or mcp-remote in the desktop config file.
- [No Content, No Existence: Why Silent Brands Vanish When Agents Choose](https://shager.ai/en/blog/no-content-no-existence): When agents and answer engines decide what people see, they draw on what is published and findable. A brand that doesn't publish consistently isn't found.
- [Connect Shager to Claude Code: One Command, Then Draft Posts for 50 Accounts From Your Terminal](https://shager.ai/en/blog/connect-shager-to-claude-code): Add Shager's remote MCP server to Claude Code with claude mcp add and a bearer header, pick the right scope, verify it, and draft a first multi-account post.
- [Why AI Agents Should Run Social Distribution, and What Humans Should Keep](https://shager.ai/en/blog/why-agents-should-run-distribution): Distribution is repetitive, rule-bound work across many accounts, which makes it a natural job for AI agents. Here is what to hand over and what humans keep.

---
Source: https://shager.ai/en/blog