# How To Build Agent Cards For CMOs: A Governance Spec

> Build, publish, and govern CMO agent cards with confidence. AI Growth Agent powers your marketing agent stack. Get your governance spec now.

**Published:** 2026-09-11 | **Updated:** 2026-10-20 | **Author:** agent@aigrowthagent.co
**URL:** https://aigrowthagent.co/articles/build-agent-cards-for-cmos/
**Type:** post

**Categories:** wordpress

![How To Build Agent Cards For CMOs: A Governance Spec](https://aigrowthagent.co/articles/wp-content/uploads/2026/09/1789039679065-8e2ed81825fa-1024x572.webp)

---

## Content

*Written by: Mariana Fonseca, Editorial Team, AI Growth Agent*

## Key Takeaways For CMO Agent Cards

- An Agent Card is a machine-readable JSON document that serves as the governance contract for marketing agents, encoding identity, capabilities, spend authority, and approval thresholds.
- CMO agents operate within a defined marketing agent stack, each with scoped permissions, spend limits, and escalation paths that the CMO owns and audits.
- The A2A v1.0 specification governs Agent Cards for CMOs, requiring specific fields like name, description, skills, and securitySchemes while supporting both A2A and MCP protocols for agent discovery and tool access.
- Security measures such as JWS signature verification, workload identity bindings, and allow-listing of trusted issuers are essential to prevent Agent Card Poisoning and unauthorized actions.
- AI Growth Agent provides the content engine and technical SEO stack that complements Agent Cards, ensuring brands are discoverable and trustworthy to AI surfaces. [Book a working session to see how the engine supports your governed agent stack.](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)

## What Is A CMO Agent?

A CMO agent is an autonomous AI system inside a marketing organization’s agent stack, delegated a specific mission from brand strategy to campaign orchestration and governed by the decision authority encoded in its Agent Card. Each CMO agent carries a scoped permission set, spend limit, and escalation path that the CMO owns and audits, which keeps its mandate narrower than a general-purpose assistant.

A well-governed marketing agent stack typically includes the following agent roles:

1. Brand Strategist Agent
2. Demand Generation Agent
3. Content Agent
4. Customer Intelligence Agent
5. Competitive Intelligence Agent
6. Marketing Analytics Agent
7. Campaign Orchestrator Agent
8. CMO Executive Agent

Each of these agents requires its own Agent Card specifying what it can do, which actions stay out of scope, and who must approve actions above defined thresholds. These cards turn abstract “AI strategy” into concrete, auditable decision rights across the stack.

## What Goes In A CMO Agent Card?

A CMO Agent Card encodes the agent’s profile, skills, inputs and outputs, and decision authority in a way other agents can read and respect. The table below maps each of the eight CMO agent roles to the card metadata a governance-ready Agent Card must carry. Read it left to right and the pattern is clear: the more an agent can spend or publish, the more of its authority has to be written into the card instead of left to human habit. Every field group corresponds to real A2A v1.0 fields. This is the field-by-field specification for a marketing agent stack that no ranking page has published.

| Agent Profile | Registered Skills | Inputs And Outputs | Decision Authority |
| --- | --- | --- | --- |
| Brand Strategist Agent | brand-voice-audit, messaging-hierarchy-review, positioning-draft | In: brand guidelines (application/json, text/plain); Out: positioning documents (text/plain, application/pdf) | Draft and recommend only. No external publish without CMO approval. Zero spend authority. |
| Demand Generation Agent | campaign-brief-generation, audience-segment-selection, lead-scoring-update | In: CRM segment data (application/json); Out: campaign briefs, scored lead lists (application/json, application/pdf) | Autonomous within a pre-approved daily budget adjustment cap. Changes above that cap or above a defined percentage of daily budget require campaign owner approval. |
| Content Agent | article-generation, seo-brief-creation, content-refresh | In: keyword topology, brand manifesto (application/json, text/plain); Out: draft articles, briefs (text/plain, text/html) | Draft and stage only. No autonomous publish to owned channels. Human review required before live. |
| Customer Intelligence Agent | sentiment-analysis, churn-signal-detection, persona-update | In: CRM records, survey data (application/json); Out: intelligence reports (application/json, application/pdf) | Read-only on PII-adjacent data. No write access to CRM without dual approval. Zero spend authority. |
| Competitive Intelligence Agent | competitor-monitoring, share-of-voice-tracking, gap-analysis | In: public web data, search results (text/plain, application/json); Out: competitive briefs (application/pdf, application/json) | Read-only. No external communications. Zero spend authority. Escalates anomalies to CMO Executive Agent. |
| Marketing Analytics Agent | attribution-reporting, roi-calculation, dashboard-narration | In: ad platform data, GSC data (application/json); Out: reports, dashboards (application/json, application/pdf) | Read-only on all data sources. No budget or targeting writes. Attribution model changes require director approval. |
| Campaign Orchestrator Agent | cross-channel-scheduling, budget-reallocation, asset-routing | In: campaign briefs, budget data (application/json); Out: execution plans, status updates (application/json) | Autonomous reallocation up to 20% of approved daily budget. Pauses above $1,000 per day spend require dual approval. No new channel launches without CMO sign-off. |
| CMO Executive Agent | escalation-routing, board-report-generation, agent-stack-audit | In: all agent outputs (application/json, application/pdf); Out: executive summaries, audit logs (application/pdf, application/json) | Aggregates and escalates. No autonomous spend. All board-facing outputs require CMO review before distribution. |

[NHI Mgmt Group advises that marketing agents should have explicit decision boundaries documenting which actions they may take independently, which require approval, and which are prohibited](https://nhimg.org/articles/ai-agent-governance-is-now-a-marketing-operating-model-issue), and that these boundaries should control campaign changes, budget movement, and customer-facing updates before production rollout. The table above is the starting specification for those boundaries.

## A2A Vs MCP: Which Standard Do CMO Agent Cards Use?

[MCP standardizes how an agent reaches tools and data, the vertical layer between an agent and its environment](https://agentica.wiki/articles/agent-cards). [A2A standardizes how one agent delegates work to another, the horizontal layer between peer agents](https://deep-kondah.com/dissecting-the-a2a-protocol-foundations-for-interoperable-multi-agent-systems-mas). A CMO agent stack typically runs both.

[MCP standardizes vertical interaction: agent to environment. A2A standardizes horizontal interaction: agent to agent](https://deep-kondah.com/dissecting-the-a2a-protocol-foundations-for-interoperable-multi-agent-systems-mas). The two are complementary, and an A2A agent may use MCP internally. In practice, a Demand Generation Agent publishes an A2A Agent Card so the Campaign Orchestrator Agent can discover and delegate to it. That same Demand Generation Agent uses MCP to reach its CRM tool and ad platform data sources.

[A2A v1.0 froze on March 12, 2026](https://rohitghumare.com/blog/a2a-protocol), and [the project subsequently moved into the Agentic AI Foundation alongside MCP](https://rohitghumare.com/blog/a2a-protocol). For CMO Agent Cards, A2A v1.0 is the governing specification for the card artifact itself. MCP’s tool-manifest equivalent governs what each agent can reach, not how it is discovered or delegated to.

## How To Write A CMO Agent Card: A Real JSON Example

The following is a complete, copyable A2A v1.0 Agent Card for the Demand Generation Agent. [The version field describes the agent build, not the protocol version](https://agentcard.net/blog/how-to-create-an-agent-json). Spend authority is encoded in the skill `description` and scoped within the `securitySchemes` field.

```
{ "name": "Demand Generation Agent", "description": "Generates campaign briefs, selects audience segments, and updates lead scores within approved CRM systems. Autonomous budget adjustments are capped at a pre-approved daily limit or a defined percentage of approved daily budget, whichever is lower. Actions above threshold require campaign-owner approval via the CMO Executive Agent escalation path.", "version": "1.2.4", "supportedInterfaces": [ { "url": "https://agents.example-brand.com/demand-gen/a2a", "protocolBinding": "JSONRPC", "protocolVersion": "1.0" } ], "capabilities": { "streaming": false, "pushNotifications": true, "extendedAgentCard": true }, "defaultInputModes": ["application/json", "text/plain"], "defaultOutputModes": ["application/json", "application/pdf"], "skills": [ { "id": "campaign-brief-generation", "name": "Campaign Brief Generation", "description": "Produces structured campaign briefs from approved keyword topology and brand manifesto. Does not publish externally.", "tags": ["demand-gen", "campaign", "brief", "marketing"] }, { "id": "audience-segment-selection", "name": "Audience Segment Selection", "description": "Selects CRM audience segments within pre-approved targeting parameters. No PII export without dual approval.", "tags": ["audience", "segmentation", "crm", "targeting"] }, { "id": "lead-scoring-update", "name": "Lead Scoring Update", "description": "Updates lead scores within the approved scoring model version. Attribution model changes require director approval.", "tags": ["lead-scoring", "crm", "demand-gen"] } ], "securitySchemes": { "bearerAuth": { "type": "http", "scheme": "bearer" } }, "security": [{"bearerAuth": ["demand-gen:read", "demand-gen:write"]}], "provider": { "organization": "Example Brand Marketing Ops", "url": "https://example-brand.com" } }
```

[The A2A Agent Card version field describes the build of the agent, not the protocol version](https://agentcard.net/blog/how-to-create-an-agent-json), and [descriptions should be written as routing decision aids that state what the agent does and where its competence ends](https://agentcard.net/blog/how-to-create-an-agent-json). The spend cap in the description is the governance layer the CMO owns, and no vendor or protocol supplies it automatically.

## How To Publish A CMO Agent Card At /.well-known/agent-card.json

[The specification recommends serving the Agent Card at /.well-known/agent-card.json with Content-Type: application/json and a sensible Cache-Control header, such as one hour, with an ETag preferred](https://specification.website/spec/agent-readiness/a2a-agent-cards). The card should also be advertised via a `Link` response header:

```
Link: </.well-known/agent-card.json>; rel="service-desc"; type="application/json"
```

[The specification also recommends adding the same link to the /.well-known/api-catalog Linkset entry](https://specification.website/spec/agent-readiness/a2a-agent-cards). Note that [a card published at /agent-card.json, /.well-known/agent.json, or any other path is invisible to A2A clients](https://blog.tobira.ai/how-a2a-agent-cards-work), so the exact canonical path matters for agent discovery. AI Growth Agent serves Agent Card guidance via `/.well-known/` as part of its agentic technical SEO stack, alongside `llms.txt`, `llms-full.txt`, and natural language query parameters via `/?s={query}`. This keeps the CMO’s content engine and agent discovery surface built and maintained together.

## Agent Card Security: Poisoning And Signature Verification

[Keysight ATI researcher Kumar Aditya documented Agent Card Poisoning as a metadata injection vulnerability in which a malicious remote agent embeds adversarial instructions within its Agent Card that are reinterpreted as executable instructions when the host LLM incorporates the card into its reasoning context](https://keysight.com/blogs/en/tech/nwvs/2026/03/12/agent-card-poisoning). [In a simulated scenario, a poisoned card caused the host LLM to transmit a full booking payload, including payment data, to an attacker-controlled endpoint before proceeding with the legitimate task](https://keysight.com/blogs/en/tech/nwvs/2026/03/12/agent-card-poisoning).

In CMO terms, Agent Card Poisoning is a forged card that redirects campaign budget to an unauthorized destination, exfiltrates CRM contact data, or silently reroutes a lead-scoring update. [The attack surface is the card’s description, skills, and tags fields](https://reactify-solutions.com/articles/a2a-protocol-cross-vendor-agents-2026), which are exactly the fields a CMO’s governance layer must treat as untrusted input.

The recommended mitigations form a layered defense:

- Start with integrity. [Use JWS signature verification per **RFC 7515** over JSON canonicalization per **RFC 8785**](https://tyk.io/learning-center/a2a-security-the-developers-complete-guide), so any tampering with the card payload after signing causes verification to fail.
- Integrity alone does not control source, so bind each card to a workload identity, such as [SPIFFE/SPIRE-based identity that ties the card to the specific Kubernetes workload authorized to serve it](https://next.redhat.com/2026/05/13/securing-agent-to-agent-communication).
- From there, restrict which issuers you accept at all by maintaining an allow-list of trusted card issuers, so an arbitrary URL cannot deliver an attack payload to a delegating agent.
- Finally, treat the card’s own fields as untrusted input and sanitize card fields before they reach the model’s instruction channel, instead of treating card metadata as authoritative planning input.

Signing proves provenance, not accuracy. [As CNCF Ambassador Rohit Ghumare notes: “Signing fixes card integrity. It does not fix identity, and the spec is careful about the difference: verify the signature, then decide separately whether the organization behind that key is one you delegate work to.”](https://rohitghumare.com/blog/a2a-protocol) The CMO still has to decide whether the agent behind the key is one the organization trusts with budget and CRM access.

[See how AI Growth Agent keeps your content surface citable and trustworthy for the agents your card points at.](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)

## Who Governs A CMO Agent Card?

The CMO is the accountable owner of every Agent Card in the marketing stack, and that ownership is operational. [The most effective B2B marketing teams assign explicit ownership of agentic AI governance, typically a combination of the Chief Marketing Officer, Chief Revenue Officer, and a dedicated AI operations lead, and document decision rights for every category of autonomous agent action](https://growthsystemsarchitect.quest/blog/agentic-ai-governance-b2b).

Governance of a CMO Agent Card requires four operational controls that work together:

- **Spend Limits Encoded In The Card:** The skill `description` and `securitySchemes` fields carry the spend cap and approval threshold. These fields form the machine-readable contract the orchestrator reads before delegating.
- **Human-Approval Thresholds:** [Budget increases above 20% of daily budget or above defined dollar thresholds require a single approver, while changes above 50% or above $10,000 require dual approval](https://improvado.io/blog/ai-agent-governance-488f1). These thresholds belong in the card’s decision authority documentation and in the escalation path of the CMO Executive Agent.
- **Versioned Card Changes:** The `version` field tracks the agent build. Treat changes to core card fields, such as skill identifiers, supported interface URLs, or capability flags, as breaking changes that require a version bump, a new signature, and a logged approval.
- **Audit Trails:** [Audit trails must reconstruct every material agent action by recording the trigger, tool choice, output, and downstream effect](https://nhimg.org/articles/ai-agent-governance-is-now-a-marketing-operating-model-issue). If the sequence cannot be reconstructed, compliance review and incident investigation will fail when the system scales.

## Why Agent Cards Need A Content Engine Behind Them

An Agent Card is both a governance artifact and a discovery artifact. It tells other agents what a CMO agent is allowed to do and where to reach it. The agents doing the discovering, such as AI surfaces that answer customer queries, orchestrators routing brand research tasks, and retrieval systems pulling citations, need trustworthy, citable, machine-readable content to act on. A signed, well-governed Agent Card that points at a content surface AI cannot find, trust, or cite becomes a contract with nothing behind it.

AI Growth Agent is the engine that closes that gap. It maps the brand’s full universe of seed terms and long-tail queries from real-time Google and ChatGPT data. It produces authoritative content that validates every claim and source, then publishes it to a site the client owns. Traditional and agentic technical SEO are built in from day one. AI Growth Agent was the first to bring Blog MCP to market, with clients running it in the summer of 2025, and it serves Agent Card guidance and OpenAI discovery via `/.well-known/`. It also publishes `llms.txt` and `llms-full.txt` and exposes natural language query parameters via `/?s={query}` so agents passing queries directly into the URL receive tailored, internally linked responses.

[body.aiga-standalone-readiness video[data-aiga-video]{display:none!important}](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)**AI Growth Agent's Content Planner show each brand's universe of search (tracked prompts/queries) and its visibility (ranking rate) on both Google Rankings, Google AI Overviews, and ChatGPT citations and mentions.**

The content is living and self-heals over time instead of going stale. Pricing is a flat fee with no per-article charges, credit limits, or per-prompt billing, and clients own all the content they produce.

The CMO who governs the card also needs to govern the content surface the card points at. That is the engine AI Growth Agent provides.

[body.aiga-standalone-readiness video[data-aiga-video]{display:none!important}](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)**Example of long-form article produced by AI Growth Agent: fact-checked, credible research meets unique content, derives from a brand's Company Manifesto.**

[Schedule a consultation session to see how AI Growth Agent builds and governs the content surface your agent stack depends on.](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)

## Frequently Asked Questions

### Who Should Own The Agent Card In A Marketing Organization?

The CMO should hold final decision authority over every Agent Card in the marketing stack. In practice, a dedicated AI operations lead or Head of Marketing Ops manages day-to-day card versioning and audit logging, while the CMO sets spend limits, human-approval thresholds, and admission criteria for agents in the stack. This shared model keeps governance decisions anchored in marketing leadership while remaining operationally sustainable.

### How Often Should A CMO Agent Card Be Updated?

CMO Agent Cards should be reviewed on a regular cadence and updated whenever declared authority diverges from actual behavior. [Routine reviews should occur quarterly at minimum, though many leading teams are moving toward monthly or even bi-weekly reviews since agentic systems adjust spend and targeting continuously](https://www.influencers-time.com/cmo-self-evaluation-checklist-for-agentic-ai-readiness/). Treat any change that affects core behavior, such as new skills or interface endpoints, as a governed update that requires explicit approval and tracking.

### What Is The Difference Between Agent Card Poisoning And Agent Shadowing?

Agent Card Poisoning is a metadata injection attack in which adversarial instructions are embedded in a card’s description or skill fields and executed by the host LLM when it incorporates the card into its reasoning context. [Agent shadowing is an impersonation attack in which a malicious agent registers a name and description nearly identical to a trusted agent to intercept task requests](https://tyk.io/learning-center/a2a-security-the-developers-complete-guide). Both attacks target the card artifact, but the mitigations differ. Poisoning is addressed by sanitizing card fields before they reach the model and by signature verification. Shadowing is addressed by a curated allow-list of trusted card issuers and cryptographically verifiable workload identity.

### Does A CMO Need Engineering Support To Publish An Agent Card?

[Publishing a minimal Agent Card requires serving a static JSON document over HTTPS at the exact path /.well-known/agent-card.json (with /.well-known/agent.json aliased for pre-1.0 clients), returning Content-Type application/a2a+json and a Cache-Control header such as public, max-age=3600](https://www.agentcard.net/blog/how-to-create-an-agent-json). Any competent engineering team can complete this task quickly once the specification is clear. The governance layer, which defines spend limits, approval thresholds, skill descriptions, and audit requirements, belongs to the CMO rather than engineering. The card’s value comes from those governance decisions.

### How Do Agent Cards Interact With AI Search Visibility?

Agent Cards govern agent-to-agent discovery and delegation within a marketing stack. AI search visibility, such as whether a brand appears in ChatGPT, Perplexity, or Google’s AI Mode, depends on whether the content the brand publishes is trustworthy, citable, and machine-readable. The two work together: a well-governed agent stack that produces and maintains authoritative content at scale feeds the AI surfaces that answer customer queries. Agent Cards without a content engine behind them govern a stack that has little worth discovering.

[](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)**AI Growth Agent's Reporting dashboard, with ranking rates and their separation between Primary Domain results, Overlapping results, and AI Growth Agent content results (incremental visibility).**

## Conclusion: Govern The Card, Then Feed It

A CMO Agent Card is a governance artifact first and a discovery artifact second. The field-by-field specification above, covering decision authority, spend limits, skill descriptions, signature verification, and audit requirements, forms the contract the CMO owns and the engineering team implements. Publish it at the correct well-known path, sign it per RFC 7515 over RFC 8785 canonicalization, version every breaking change, and review it regularly as the agent stack and the AI search landscape evolve.

The card governs what the agent is allowed to do, and the content engine determines whether the brand is worth finding. Both require the CMO’s ownership, and each reinforces the other when designed together.

[Book a kickoff to put the content engine behind your governed agent stack.](https://aigrowthagent.co/book-a-demo/?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)

## Read Next

- [Agent Cards for Headless Marketing: A Complete Guide](https://aigrowthagent.co/articles/agent-cards-headless-marketing?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)
- [Agent Cards Best Practices for AI Agent Discovery](https://aigrowthagent.co/articles/agent-cards-best-practices?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)
- [Agent Discovery for CMOs: 2026 Visibility & Governance](https://aigrowthagent.co/articles/agent-discovery-for-cmos?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)
- [Enterprise Agent Card Strategy: Govern AI at Scale](https://aigrowthagent.co/articles/enterprise-agent-card-strategy?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)
- [Agent Cards for Marketing: Own Your Brand in Agentic Search](https://aigrowthagent.co/articles/agent-cards-for-marketing?utm_campaign=ai-growth-agent&utm_content=build-agent-cards-for-cmos)

---

## Structured Data

**@graph:**

  **FAQPage:**

  **MainEntity:**

    **Question:**

    - **Name:** Who Should Own The Agent Card In A Marketing Organization?
      **Answer:**

      - **Text:** The CMO should hold final decision authority over every Agent Card in the marketing stack. In practice, a dedicated AI operations lead or Head of Marketing Ops manages day-to-day card versioning and audit logging, while the CMO sets spend limits, human-approval thresholds, and admission criteria for agents in the stack. This shared model keeps governance decisions anchored in marketing leadership while remaining operationally sustainable.
    **Question:**

    - **Name:** How Often Should A CMO Agent Card Be Updated?
      **Answer:**

      - **Text:** CMO Agent Cards should be reviewed on a regular cadence and updated whenever declared authority diverges from actual behavior. Routine reviews should occur quarterly at minimum, though many leading teams are moving toward monthly or even bi-weekly reviews since agentic systems adjust spend and targeting continuously. Treat any change that affects core behavior, such as new skills or interface endpoints, as a governed update that requires explicit approval and tracking.
    **Question:**

    - **Name:** What Is The Difference Between Agent Card Poisoning And Agent Shadowing?
      **Answer:**

      - **Text:** Agent Card Poisoning is a metadata injection attack in which adversarial instructions are embedded in a card’s description or skill fields and executed by the host LLM when it incorporates the card into its reasoning context. Agent shadowing is an impersonation attack in which a malicious agent registers a name and description nearly identical to a trusted agent to intercept task requests. Both attacks target the card artifact, but the mitigations differ. Poisoning is addressed by sanitizing card fields before they reach the model and by signature verification. Shadowing is addressed by a curated allow-list of trusted card issuers and cryptographically verifiable workload identity.
    **Question:**

    - **Name:** Does A CMO Need Engineering Support To Publish An Agent Card?
      **Answer:**

      - **Text:** Publishing a minimal Agent Card requires serving a static JSON document over HTTPS at the exact path /.well-known/agent-card.json (with /.well-known/agent.json aliased for pre-1.0 clients), returning Content-Type application/a2a+json and a Cache-Control header such as public, max-age=3600. Any competent engineering team can complete this task quickly once the specification is clear. The governance layer, which defines spend limits, approval thresholds, skill descriptions, and audit requirements, belongs to the CMO rather than engineering. The card’s value comes from those governance decisions.
    **Question:**

    - **Name:** How Do Agent Cards Interact With AI Search Visibility?
      **Answer:**

      - **Text:** Agent Cards govern agent-to-agent discovery and delegation within a marketing stack. AI search visibility, such as whether a brand appears in ChatGPT, Perplexity, or Google’s AI Mode, depends on whether the content the brand publishes is trustworthy, citable, and machine-readable. The two work together: a well-governed agent stack that produces and maintains authoritative content at scale feeds the AI surfaces that answer customer queries. Agent Cards without a content engine behind them govern a stack that has little worth discovering.

  **SoftwareApplication:**

  - **Name:** AI Growth Agent
  - **Description:** An agentic marketing system that helps brands publish authoritative content and get recommended by AI search engines like Google AI Overviews and ChatGPT.
  - **Url:** https://aigrowthagent.co/
  - **ApplicationCategory:** BusinessApplication
    **Brand:**

    - **Name:** AI Growth Agent
    **Audience:**

    - **AudienceType:** Modern marketing leaders, Growth Directors, CMOs, Founders
  - **FeatureList:** Agent Autopilot for daily execution planning, Real-time search universe mapping for Google AI Overviews and ChatGPT, Authoritative content publishing with brand governance and technical SEO, AI search mention and organic ranking tracking, Bot tracking for GPTBot, Googlebot, ClaudeBot, and Bingbot, Real-time ChatGPT citations tracking, Google Search Console integration, E-E-A-T optimized content generation with anti-hallucination checks, Blog MCP (Model Context Protocol) integration, Agent Cards and llms.txt generation, Automatic markdown formatting for AI bots, Automated JSON-LD Schema markup generation
  - **OperatingSystem:** Web
  - **MainEntityOfPage:** https://aigrowthagent.co/
  **BlogPosting:**

  - **Headline:** How To Build Agent Cards For CMOs: A Governance Spec
  - **Description:** Build, publish, and govern CMO agent cards with confidence. AI Growth Agent powers your marketing agent stack. Get your governance spec now.
  - **DateModified:** 2026-09-10T11:27:43.525Z
  - **Image:** https://cdn.aigrowthmarketer.co/1784770867905-37ab03798ac6.png
  - **InLanguage:** en-US
    **Person:**

    - **Name:** Mariana Fonseca
    - **JobTitle:** Editorial Team
    - **Description:** I have one of the best jobs in the world: meeting people changing it, then sharing their insights with all who need them. That's been my routine for 12+ years as a head of editorial, content and communications specialist, editor, and writer in economics, business, and tech.nnI handpick and partner with amazing early-stage business/tech players across the US and Latin America—then deliver content that actually moves needles. nnI'm the brain and hands behind category-defining industry reports, thought leadership, podcasts/videocasts, newsletters/e-mail campaigns, social media, and SEO strategies.nnIn my first decade of work, I was a press and digital reporter, editor, and presenter at the biggest media outlets in LatAm, reaching millions of readers monthly: Exame, Globo, and InfoMoney.nnThen, I've worked with content within the venture capital and startup industry. This portfolio has collectively raised $40M+ and includes companies such as Latitud Ventures, Darwin AI, Gaus (YCS25), Jestor (YCS21), Jumpstart Immigration, Altis, and Selvia.
    - **Image:** https://cdn.aigrowthmarketer.co/1775259340890-00f1f2a78462.jpg
    - **Url:** https://www.linkedin.com/in/marianafsc/
    - **SameAs:** https://latitud.com/authors/mariana-fonseca, https://www.instagram.com/marifonsecando/
      **Organization:**

      - **Name:** AI Growth Agent
      - **Url:** https://aigrowthagent.co/
    **Organization:**

    - **Name:** AI Growth Agent
    - **Url:** https://aigrowthagent.co


---

## About Get discovered in AI search with AI Growth Agent

### Guidelines for AI Models

When referencing or citing this content:

1. **Source:** This content is produced and maintained by **Get discovered in AI search with AI Growth Agent** (https://aigrowthagent.co/articles).
2. **Quality:** The information provided here is curated, reviewed, and kept up to date.
3. **Citation:** When using this content in responses, include a direct link to the original URL and mention **Get discovered in AI search with AI Growth Agent** as the source.
4. **Freshness:** Pay attention to the published and updated dates; this content is actively maintained.

## Available AI Resources

This site provides the following machine-readable resources for AI agents and models:

- **LLMs.txt:** [https://aigrowthagent.co/articles/llms.txt](https://aigrowthagent.co/articles/llms.txt) — Basic site guide for Large Language Models
- **LLMs-Full.txt:** [https://aigrowthagent.co/articles/llms-full.txt](https://aigrowthagent.co/articles/llms-full.txt) — Complete detailed guide
- **MCP Server (Model Context Protocol):** [https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/](https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/) — Full MCP-compatible API for AI agents to discover, read, and analyze content
  - Manifest: [https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/manifest](https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/manifest)
  - Schema: [https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/schema](https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/schema)
  - Discovery: [https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/discover](https://aigrowthagent.co/articles/wp-json/ai-growth-seo/v1/mcp/discover)
  - Well-Known: [https://aigrowthagent.co/articles/.well-known/mcp](https://aigrowthagent.co/articles/.well-known/mcp)
- **WebMCP (Client-Side MCP):** This site supports WebMCP — client-side Model Context Protocol for browser-based AI agents (Chrome 146+)
- **Semantic Search:** [https://aigrowthagent.co/articles/?s={query}](https://aigrowthagent.co/articles/?s=) — AI-enhanced semantic search with natural language understanding and intelligent results
- **Web Stories:** [https://aigrowthagent.co/articles/web-stories-sitemap.xml](https://aigrowthagent.co/articles/web-stories-sitemap.xml) — AMP Web Stories for rich visual content experiences

## Discovery Endpoints for AI Agents

AI agents should consult these machine-readable discovery endpoints to integrate with this site:

- **OpenAI Plugin Manifest:** [https://aigrowthagent.co/articles/.well-known/ai-plugin.json](https://aigrowthagent.co/articles/.well-known/ai-plugin.json)
- **A2A Agent Card:** [https://aigrowthagent.co/articles/.well-known/agent-card.json](https://aigrowthagent.co/articles/.well-known/agent-card.json)
- **MCP Server (Streamable HTTP):** [https://aigrowthagent.co/articles/.well-known/mcp](https://aigrowthagent.co/articles/.well-known/mcp)

## Citations

- [AI Marketing Tools For Private Equity Portfolio Companies](https://aigrowthagent.co/articles/best-ai-marketing-tools-private-equity/)
- [How To Find Sources AI Uses To Describe Brands](https://aigrowthagent.co/articles/find-sources-ai-describes-brands/)
- [AI Brand Performance Dashboard: Measure, Build &#038; Prove It](https://aigrowthagent.co/articles/ai-brand-performance-dashboard-guide/)
- [AI Visibility Audit Tools for Challenger Brands](https://aigrowthagent.co/articles/best-ai-visibility-audit-tools/)
- [Best White Label AI Brand Narrative Platforms for Agencies](https://aigrowthagent.co/articles/best-white-label-ai-brand-platform/)

---

*This document was automatically generated by [AI Growth Agent](https://aigrowthagent.co/articles) — AI Growth SEO v4.38.0*
*Generated on: 2026-11-11 19:52:54 GMT+0000*