// examples

AI visibility workflow examples.

Practical patterns for using Kiodo AI visibility checks inside agents, dashboards, scheduled jobs, customer-facing features, and marketing reports.

// patterns

workflows.json

Cron job

Run category checks daily or weekly, store the JSON output, and notify a team when share of answer or citation gaps move.

HTTP agent

Call the REST API during research or product work to inspect brand visibility before changing dashboards, reports, or internal tools.

MCP client

Use MCP for Search, Contents, Answer, and Usage. AI Visibility is REST-only beta for now.

Dashboard backend

Use aiVisibility.check() as the data source behind brand, competitor, source, and opportunity panels.

Marketing report

Generate recurring reports with visibility score, share of answer, cited sources, and recommended actions.

// inputs

request_shape.md

Brand

The brand you want to measure.

Category

The market, product, or buying category to check.

Competitors

A short list of companies to compare against.

Market

The target market for the visibility check.

faq.md

Can I run AI visibility checks on a schedule?

Yes. Kiodo is API-first, so checks can run from cron, queues, jobs, or backend workflows.

Can agents use these workflows?

Yes. Agents can call AI Visibility directly through HTTP. MCP currently covers Search, Contents, Answer, and Usage, not AI Visibility.