{
  "context": "Evaluates whether the solution uses azure-ai-documentintelligence to send custom REST calls through the SDK pipeline instead of ad-hoc HTTP. Focuses on crafting the analyze POST, reusing the returned operation-location, and retrieving markdown or PDF results via the same authenticated pipeline.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Pipeline dispatch",
      "description": "Uses DocumentIntelligenceClient.send_request (or aio equivalent) with azure.core.rest.HttpRequest rather than standalone HTTP clients, ensuring SDK auth/policies are applied.",
      "max_score": 20
    },
    {
      "name": "Analyze POST shape",
      "description": "POST target is documentModels/{modelId}:analyze with api-version query, JSON body sets urlSource and outputContentFormat='markdown', and a matching Content-Type header is provided.",
      "max_score": 25
    },
    {
      "name": "Operation header",
      "description": "Returns the absolute operation-location header from the 202 response without reformatting or dropping it.",
      "max_score": 10
    },
    {
      "name": "Markdown GET",
      "description": "GETs the provided operation URL through send_request with Accept: text/markdown and uses HttpResponse helpers to return markdown text.",
      "max_score": 20
    },
    {
      "name": "PDF GET",
      "description": "GETs the same operation URL (adding a pages query when provided) with Accept: application/pdf via send_request and consumes the HttpResponse content/stream to return bytes.",
      "max_score": 20
    },
    {
      "name": "Pipeline reuse",
      "description": "Relies on the existing DocumentIntelligenceClient instance for authentication and policies (no new credentials or raw requests outside the SDK pipeline).",
      "max_score": 5
    }
  ]
}