Skip to content
Leadee.ai
Not translated yet.This page is not available in Português (Brasil) yet, so you are reading the English version.Open the English page

Fix Engine

Fix tickets generated from a run, plus the re-measurement loop after you ship a fix.

Updated

What it does

The Fix Engine module turns a visibility drop into a concrete ticket — a schema fix, an answer block, a content brief — and re-measures after you ship it, closing the loop between finding a problem and knowing whether the fix worked. This is the differentiator in Leadee's comparison with measurement-only GEO tools; see vs. Otterly.ai.

Planned endpoints

List tickets — GET /v1/fix-engine/tickets

bash
curl "https://api.leadee.ai/v1/fix-engine/tickets?brand_id=brand_01H4JEY&status=open" \
  -H "Authorization: Bearer $LEADEE_API_KEY"

Planned response

json
{
  "data": [
    {
      "id": "ticket_7c21",
      "type": "schema_fix",
      "status": "open",
      "summary": "Add Organization JSON-LD with contactPoint",
      "related_run_id": "run_9f2c"
    }
  ]
}

Mark a ticket resolved and trigger re-measurement — POST /v1/fix-engine/tickets/{ticketId}/resolve

bash
curl -X POST https://api.leadee.ai/v1/fix-engine/tickets/ticket_7c21/resolve \
  -H "Authorization: Bearer $LEADEE_API_KEY"

Resolving a ticket schedules a follow-up Visibility Tracker run so you can see whether the fix moved the confidence interval.

Related