Skip to navigation

Running Agents

Markup AI’s content agents are exposed through the Agents endpoints of the API. Each agent runs against the settings configured for your organization in the Markup AI console — no per-call style guide IDs. For what each agent does and why it matters, see the Agent Catalog.

The run flow

  1. Discover the agents available to your organization with GET /agents. Each entry includes the agent’s stable name (e.g. brand_voice), its id, description, and category. Resolve the id from the name at runtime — every agent page below has copy-paste examples that do exactly that.
  2. Run an agent with POST /agents/{agent_id}/run, passing your content as text. Pass wait=true to block until the run completes; otherwise the response returns immediately with a workflow_id.
  3. Track longer runs with GET /agents/workflows/{workflow_id}, stream progress from GET /agents/workflows/{workflow_id}/stream (server-sent events), or supply a webhook_url in the run request to receive the result when the agent finishes.

The agents returned by GET /agents depend on your organization’s plan and feature access.

Agent reference

AgentAPI nameCategory
AI Voiceai_voice_detectorContent Integrity
Brand TermsterminologyBrand
Brand Voicebrand_voiceBrand
Claimsgeneric_claimsAccuracy
Date & Time Accuracydate_time_accuracyAccuracy
Flufffocus_agentContent Integrity
FreshnessfreshnessAI Visibility
Key Takeawayskey_takeawaysAI Visibility
Link Integritylink_integrityAccuracy
PersonapersonaBrand
Q&A Optimizationanswer_authorityAI Visibility
Sentence Claritysentence_clarityContent Integrity
Snippet Readinesssnippet_readinessAI Visibility
Source Authoritysource_authorityAI Visibility
Stylestyle_agentBrand

Via MCP

The same agents run on the hosted MCP server at https://api.markup.ai/mcp/, addressed by the same name used here. Ask for a review and markupai_review picks the agents for you, or name them explicitly with markupai_run_agents — see the MCP overview to connect Claude, Cursor, or any other MCP client.