Q&A Optimization | Markup AI

API name: answer_authority · Category: AI Visibility

Evaluate whether section headings match their content and lead with the answer. For what this agent does and why it matters, see Q&A Optimization in the Agent Catalog.

What it returns

The run status plus the flagged sections with their suggested heading rewrites.

Run this agent

Agents are run by ID, but you never need to hardcode one: resolve the ID from the agent’s stable name (answer_authority) with GET /agents, then call POST /agents/{agent_id}/run. Pass wait=true to block until the run completes; omit it to get a workflow_id back immediately and track the run with GET /agents/workflows/{workflow_id} (or a webhook_url in the request body).

TOKEN="YOUR_TOKEN"
# Resolve the agent ID by name
AGENT_ID=$(curl -s "https://api.markup.ai/agents?page_size=100" \
  -H "Authorization: Bearer $TOKEN" \
  | jq -r '.agents[] | select(.name == "answer_authority") | .id')
# Run the agent and wait for the result
curl -X POST "https://api.markup.ai/agents/$AGENT_ID/run?wait=true" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text": "Your content to check."}'

Prefer MCP? On the hosted MCP server, run this agent with markupai_run_agents and agents: ["answer_authority"], or let markupai_review select it from your goal — see the MCP overview.