SHAI
Book a callStart free

S10 Ads

/meta-account-monitor

Agent 102: Meta Account Compliance Monitor (any industry, owner addition)

Monitors a business's Meta account health (ad-account status/disable reason, rejected ads, Page/IG policy issues, billing holds, verification status, pixel health, admin/2FA, messaging rate-limit responses) hourly for ad accounts and daily otherwise, via the official Meta Marketing + Graph APIs. Owns the shared account-health/cooldown state file /dm-outreach, /social-engagement, /ads-campaigns, and /organic-content-creator all read. Runs the rule-based pre-publish policy check /ad-copy and /ad-creatives defer to, and drafts (never submits) compliant revisions and appeal text. A disabled account or Page restriction is always URGENT. Never evades enforcement or creates a replacement account.

verified (fixture) 2026-09-08 · needs-connector: metav0.1.0

Run itAll agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

  • #102 — Meta account compliance monitor · official Meta APIs; hourly/daily checks; owns the account-health state the S9/S10 skills read; pre-publish policy check; appeals drafted, user submits; URGENT on disable

Example requests

  • “check our Meta account health”
  • “is our ad account okay”
  • “check this ad copy against Meta's policies”
  • “meta account compliance monitor”

What it needs, and what it hands back

Needs connected

Nothing. It runs on what SHAI already knows about you.

Better with: meta.

Hands back

  • clients/<business-slug>/compliance/meta-account-health.json
  • Step 4's pre-publish check result, returned inline

Stops and asks

Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.

Steps it cannot do through an API, and hands you instead: appeal submission; business/domain verification completion.

How it runs

These are the headings of its own written instructions — 303 lines you can read and change.

  1. Step 0 — Environment, profile, workspace
  2. Step 1 — Hourly checks (ad accounts)
  3. Step 2 — Daily checks (everything else)
  4. Step 3 — Update the shared account-health file; alert
  5. Step 4 — Pre-publish policy check (no API required — rule-based)
  6. Step 5 — When something is actually rejected/restricted