{
  "data": {
    "a": {
      "slug": "microsoft-decision-1-1",
      "name": "Microsoft-Decision-1.1",
      "vendor": "Microsoft",
      "vendorUrl": "https://www.microsoft.com",
      "company": "microsoft.com",
      "kind": "model",
      "category": "decision-models",
      "summary": "Microsoft-Decision-1.1 is a Microsoft model, built on Gemma 4 26B A4B, that scores fixed answer options with a calibrated probability for each, from text or images. Generally available on Foundry, OpenRouter and Vercel from $0.042 per million input tokens.",
      "url": "https://www.anchorterminal.com/tools/microsoft-decision-1-1",
      "markdownUrl": "https://www.anchorterminal.com/tools/microsoft-decision-1-1.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/microsoft-decision-1-1.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/microsoft-decision-1-1.json",
      "dns": "microsoft-decision-1-1.grade.anchorterminal.com",
      "license": "Not stated. Microsoft's post and OpenRouter's page name no licence for the hosted model. It's built on Gemma 4 26B A4B, and no Microsoft weights were released.",
      "transports": [
        "http"
      ],
      "packages": [],
      "auth": "mixed",
      "authNotes": "Foundry route: a Microsoft Entra bearer token for https://cognitiveservices.azure.com/.default, against a deployment in a Foundry resource, so an Azure subscription and deployment come first. OpenRouter route: an OpenRouter API key, read from OPENROUTER_API_KEY in OpenRouter's SDK example. Signup and key creation on OpenRouter were not checked.",
      "pricing": "usage",
      "pricingNotes": "Input on Foundry $0.042 per million tokens Global Standard, $0.046 US Data Zone and $0.05 EU and APAC Data Zone, output free (checked 18 November 2026). OpenRouter lists $0.042 input and $0 output. No free tier or trial without a card was found.",
      "priceSummary": "Pay per use",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in Microsoft's announcement, the Tech Community post, the Foundry sample or OpenRouter's model page, checked 10 October 2026.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-10"
      },
      "docsUrl": "https://commandline.microsoft.com/microsoft-decision-model-ga/",
      "capabilities": [
        "inference.decision"
      ],
      "tags": [
        "hosted",
        "model",
        "usage-priced",
        "status-page",
        "multimodal",
        "new"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 44.8,
        "grade": "E",
        "agentReady": false,
        "rank": 1292,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 50,
          "maintenance": 44,
          "payments": 30,
          "reliability": 50,
          "schema": 43,
          "security": 52,
          "transparency": 34
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "A generally available decision model that returns a calibrated probability per option, now from images as well as text, at $0.042 per million input tokens with output free on Foundry and OpenRouter. No published schema, changelog, licence or deprecation policy was found.",
        "bestFor": "Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.",
        "strengths": [
          "Generally available on Foundry, OpenRouter and Vercel",
          "$0.042 per million input tokens on Foundry Global Standard and OpenRouter, output free",
          "A calibrated probability for each option in one pass, so an application can defer when confidence is low",
          "Takes images as well as text and JSON, up to 32K tokens",
          "Data Zone deployments in the US, EU and APAC say where processing happens"
        ],
        "weaknesses": [
          "No machine-readable contract or reference page with the request schema was found",
          "No changelog or version history beyond the two releases",
          "No licence stated for the hosted model",
          "No deprecation policy or notice period found",
          "Benchmark figures are Microsoft's own"
        ],
        "agentNotes": [
          "On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token",
          "On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions",
          "Send fixed answer options and read the probabilities; it writes no explanation",
          "Set a confidence threshold and defer to a larger model below it"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.8
          }
        ],
        "editorialScores": {
          "ergonomics": 50,
          "maintenance": 44,
          "payments": 30,
          "reliability": 50,
          "schema": 43,
          "security": 52,
          "transparency": 22
        },
        "provenanceScore": 46,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST \"$AZURE_ENDPOINT/providers/microsoft/v1/systemone\" \\\n  -H \"Authorization: Bearer $ENTRA_TOKEN\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"model\":\"\u003cdeployment-name\u003e\",\"state\":\"The customer requests a refund for a duplicate charge.\",\"questions\":{\"team\":{\"type\":\"choice\",\"instructions\":\"Which team should handle this request?\",\"criteria\":{\"billing\":\"Charges, invoices, refunds or subscription payments\",\"technical\":\"Software errors or integration failures\"}}}}'"
      },
      "letme": {
        "capability": "https://letme.dev/inference.decision",
        "tool": "https://letme.dev/microsoft-decision-1-1"
      },
      "sameCompany": [
        "azure-openai",
        "azure-foundry-fine-tuning",
        "azure-ai-content-safety",
        "azure-speech-to-text",
        "azure-text-to-speech",
        "microsoft-agent-framework",
        "microsoft-execution-containers",
        "microsoft-entra-agent-id",
        "azure-key-vault",
        "bing-grounding",
        "azure-document-intelligence",
        "azure-devops-mcp",
        "microsoft-learn-mcp",
        "tokeneconomizer",
        "playwright-mcp",
        "azure-mcp",
        "azure-maps",
        "azure-translator",
        "microsoft-graph-calendar",
        "azure-blob-storage",
        "onedrive-sharepoint",
        "microsoft-teams",
        "dynamics-365-sales",
        "copilot-studio-mcp",
        "power-automate",
        "foundry-local",
        "microsoft-mcp-server-enterprise",
        "microsoft-decision-1",
        "microsoft-advertising-api",
        "microsoft-excel-graph",
        "outlook-mail-graph",
        "microsoft-graph-people",
        "fara1-5-27b",
        "fara1-5-4b",
        "fara1-5-9b",
        "mage-vl-cowork"
      ],
      "area": "models",
      "unitPrices": [
        {
          "item": "Decision input",
          "unit": "1m-tokens",
          "usd": 0.042,
          "note": "US and EU Datazone on Foundry and OpenRouter. Microsoft's post says usage charges apply."
        },
        {
          "item": "Decision output",
          "unit": "1m-tokens",
          "usd": 0,
          "note": "Free per Microsoft's post and OpenRouter. The Foundry price table shows N/A."
        }
      ],
      "provenance": {
        "legalEntity": "",
        "domain": "microsoft.com",
        "domainRegistered": "",
        "endpointOnVendorDomain": null,
        "terms": "",
        "privacy": "https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/data-privacy",
        "statusPage": "https://azure.status.microsoft/en-us/status/history/",
        "changelog": "",
        "securityTxt": "expired",
        "checked": "2026-11-18",
        "notes": [
          "The Foundry endpoint is account-specific, given as AZURE_ENDPOINT in Microsoft's sample, so endpointOnVendorDomain is not set.",
          "The legal entity name and Microsoft's product terms were not read, so terms is empty.",
          "Microsoft's security.txt at www.microsoft.com/.well-known/security.txt gives an Expires date of 2026-09-23, which has passed.",
          "The Azure status history page shows a Foundry Models component and dated incidents. It is shared by all Foundry models, not specific to this one.",
          "The Foundry model catalogue page at ai.azure.com is rendered by script and returned no model content when read."
        ],
        "score": 46
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/microsoft-decision-1-1.json",
      "live": {
        "slug": "microsoft-decision-1-1",
        "vendorStatus": {
          "page": "https://azure.status.microsoft/en-us/status/history",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-11-18T18:52:48.801399177Z"
        },
        "securityTxt": {
          "url": "https://microsoft.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-10-27T16:00:00.000Z",
          "checkedAt": "2026-11-18T16:29:47.885824675Z"
        },
        "pages": [
          {
            "url": "https://learn.microsoft.com/en-us/azure/ai-foundry/responsible-ai/openai/data-privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:46:38.3449626Z",
            "changedAt": "2026-11-18T21:46:38.3449626Z",
            "fingerprint": "180a88913e5c"
          }
        ],
        "updatedAt": "2026-11-18T21:46:38.3449626Z"
      }
    },
    "answer": "pplx-decider scores 71.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category.",
    "b": {
      "slug": "pplx-decider",
      "name": "pplx-decider",
      "vendor": "Perplexity",
      "vendorUrl": "https://www.perplexity.ai/",
      "company": "perplexity.ai",
      "kind": "model",
      "category": "decision-models",
      "summary": "pplx-decider is Perplexity's 27B decision model, a fine-tune of Qwen3.8-27B. It answers yes or no, choice and score questions about text, JSON and images with probabilities, through Perplexity's hosted Decisions API or open weights on Hugging Face.",
      "url": "https://www.anchorterminal.com/tools/pplx-decider",
      "markdownUrl": "https://www.anchorterminal.com/tools/pplx-decider.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pplx-decider.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pplx-decider.json",
      "dns": "pplx-decider.grade.anchorterminal.com",
      "repo": "https://huggingface.co/perplexity-ai/pplx-decider-v1.2",
      "license": "Apache-2.0 for the published weights and inference code. The hosted Decisions API is a proprietary service",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.perplexity.ai/v1/decisions",
      "packages": [],
      "auth": "api-key",
      "authNotes": "Hosted API. Bearer Perplexity API key in the `Authorization` header. A key sent in `x-api-key` returns 401. Keys are created in the API console after a project exists, are shown once, and can be generated and revoked through `/generate_auth_token` and `/revoke_auth_token`. No per-key scopes were found. The official Python and TypeScript SDKs take the same key. Weights. The Hugging Face repository is public and not gated, although its model card still says to authenticate with a Hugging Face token.",
      "pricing": "usage",
      "pricingNotes": "$0.02 per million input tokens on Perplexity's Decisions API for `pplx-decider-v1.2`, and for the old names `pplx-decider-v1.1-27b` and `pplx-decider-v1-27b`, which now select v1.2. Output tokens are free and there is no per-request fee. The 4B `pplx-decider-flash-v1.2` is listed separately at $0.01. Usage draws on prepaid credits, and the billing guide asked for a credit card on 9 October 2026. No free allowance was found. The weights are free to download and need a CUDA GPU with about 52 GiB for BF16 weights.",
      "priceSummary": "Pay per use",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Decisions API guide, the reference, the pricing page or llms.txt, read on 17 October 2026.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-01"
      },
      "docsUrl": "https://docs.perplexity.ai/docs/decisions/quickstart",
      "llmsTxt": "https://docs.perplexity.ai/llms.txt",
      "openapi": "https://docs.perplexity.ai/openapi.json",
      "capabilities": [
        "inference.decision"
      ],
      "tags": [
        "official",
        "hosted",
        "model",
        "open-weights",
        "multimodal",
        "openapi",
        "llms-txt",
        "usage-priced",
        "status-page"
      ],
      "lastRelease": "2026-10-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 71.8,
        "grade": "BB",
        "agentReady": true,
        "rank": 250,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 5,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 65,
          "payments": 38,
          "reliability": 75,
          "schema": 89,
          "security": 68,
          "transparency": 74
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-01"
        },
        "negative": 0,
        "verdict": "The hosted Decisions API now serves v1.2, with an OpenAPI description, typed questions, Python and TypeScript SDK methods and $0.02 per million input tokens, and the weights are public under Apache-2.0. Requests naming v1.1 or v1 are now answered by v1.2 with no notice period, and the response does not say which version answered.",
        "bestFor": "High-volume classification, routing and rubric scoring over text and images where a team wants a low hosted price, several related questions per item and the option to run the same weights itself.",
        "strengths": [
          "Weights for v1.2 are public on Hugging Face under Apache-2.0, with the `pplx_decider` inference package in the repository",
          "One request takes up to 128 questions about one `state`, read and billed once, mixing `noul`, `choice` and `score`",
          "$0.02 per million input tokens with free output and no per-request fee, published without a login",
          "OpenAPI 3.1.0 description, llms.txt, Markdown pages and `client.decisions.create` in the official Python and TypeScript SDKs",
          "Limits stated as 10 requests a second per organisation and 15 million tokens a minute, with `Retry-After` on 429 and `x-ratelimit-*` headers"
        ],
        "weaknesses": [
          "Requests naming `pplx-decider-v1.1-27b` or `pplx-decider-v1-27b` are answered by v1.2 since 16 October 2026, with no notice period",
          "The response echoes the model name sent, so a caller using an alias or an old name cannot see which version answered",
          "Grouped questions change each other's answers, and Perplexity's figures show grouping costing up to 4.8 points on candidate-ranking tasks",
          "No retention period for decision inputs is stated, and zero data retention needs a written agreement",
          "An image over 2,048 tiles is not rejected. The request waits about a minute and returns 504"
        ],
        "agentNotes": [
          "Send `Authorization: Bearer`. A key in `x-api-key` returns 401 on this endpoint.",
          "Pin `pplx-decider-v1.2` and log it with each result. Old names and aliases route to newer versions, and the response echoes the name sent.",
          "Revalidate thresholds set on v1.1. The v1.2 card says it gives different answers to v1.1-style requests.",
          "Group questions that are facets of one decision. Send independent candidates, such as documents or tools, in separate requests.",
          "Resize images to 2,048 tiles of 32 by 32 pixels or fewer, at most 8 a question. Larger images end in a 504 after about a minute.",
          "For the weights, use the repository's `pplx_decider` package. The card says default causal inference does not reproduce the checkpoint."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 4,
        "avgRating": 3.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "BB",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 71.8
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 65,
          "payments": 38,
          "reliability": 75,
          "schema": 89,
          "security": 68,
          "transparency": 66
        },
        "provenanceScore": 82,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-01",
            "maintenance": "2026-11-01",
            "payments": "2026-11-01",
            "reliability": "2026-11-01",
            "schema": "2026-11-01",
            "security": "2026-11-01",
            "transparency": "2026-11-01"
          },
          "last": "2026-11-01",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-01",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://api.perplexity.ai/v1/decisions \\\n  -H \"Authorization: Bearer $PERPLEXITY_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"model\":\"pplx-decider-v1.2\",\"state\":\"The headphones sound great, but the battery stopped charging after two weeks.\",\"questions\":{\"defect\":{\"type\":\"noul\",\"instructions\":\"Does the review report a product defect?\"}}}'"
      },
      "letme": {
        "capability": "https://letme.dev/inference.decision",
        "tool": "https://letme.dev/pplx-decider"
      },
      "sameCompany": [
        "perplexity-space",
        "perplexity-search-api",
        "pplx-decider-flash"
      ],
      "area": "models",
      "unitPrices": [
        {
          "item": "Decision input",
          "unit": "1m-tokens",
          "usd": 0.02,
          "note": "`pplx-decider-v1.2`, and the old v1.1 and v1 names, which now select it. State, questions and images count as input."
        },
        {
          "item": "Decision output",
          "unit": "1m-tokens",
          "usd": 0,
          "note": "Output tokens are free. No per-request fee."
        }
      ],
      "provenance": {
        "legalEntity": "Perplexity AI, Inc.",
        "domain": "perplexity.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service",
        "privacy": "https://www.perplexity.ai/hub/legal/privacy-notice",
        "statusPage": "https://status.perplexity.com/",
        "changelog": "https://docs.perplexity.ai/docs/resources/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-17",
        "notes": [
          "The Perplexity API Terms of Service (last updated 23 January 2026) and the Data Processing Addendum (13 August 2026) name Perplexity AI, Inc. and California law. www.perplexity.ai served both pages on 17 October 2026, after answering with a bot check (403) on 9 October.",
          "The API terms name the Sonar and Agentic Research APIs and do not name the Decisions API. The privacy notice (8 July 2026) says it does not apply to data collected through the API, which the DPA governs.",
          "www.perplexity.ai/.well-known/security.txt is valid until 31 December 2027 and links a security page that names a public vulnerability disclosure programme and a private bug bounty on Bugcrowd.",
          "The status page lists Website, App, Computer and API components, with no Decisions component.",
          "The changelog dates entries by month. The three Decisions entries are under October 2026.",
          "Domain registration was not checked."
        ],
        "score": 82
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/pplx-decider.json",
      "live": {
        "slug": "pplx-decider",
        "probe": {
          "target": "https://api.perplexity.ai/v1/decisions",
          "method": "get",
          "lastAt": "2026-11-18T23:01:48.618485915Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 360,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 153,
          "p95ms24h": 347,
          "samples24h": 241,
          "samples30d": 7840,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 231,
              "ok": 231
            }
          ],
          "since": "2026-10-09T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.perplexity.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T23:01:13.2714423Z"
        },
        "securityTxt": {
          "url": "https://perplexity.ai/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-12-31T00:00:00Z",
          "checkedAt": "2026-11-18T16:30:43.155317806Z"
        },
        "llmsTxt": {
          "url": "https://docs.perplexity.ai/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:50.8989842Z"
        },
        "domain": {
          "domain": "perplexity.ai",
          "registered": "2022-07-08",
          "source": "https://rdap.identitydigital.services/rdap/domain/perplexity.ai",
          "checkedAt": "2026-11-15T15:34:19.536586035Z"
        },
        "pages": [
          {
            "url": "https://docs.perplexity.ai/docs/resources/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-16T22:22:49.228305471Z",
            "changedAt": "2026-10-16T22:22:49.228305471Z",
            "fingerprint": "c5b21d4b2d0a"
          },
          {
            "url": "https://www.perplexity.ai/hub/legal/privacy-notice",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-16T22:39:55.834083007Z",
            "changedAt": "2026-10-15T22:12:37.636317867Z",
            "fingerprint": "0f719c131ead"
          },
          {
            "url": "https://www.perplexity.ai/hub/legal/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-16T22:39:58.187593235Z",
            "changedAt": "2026-10-15T22:12:40.105630017Z",
            "fingerprint": "6aa58e7bcc4d"
          }
        ],
        "updatedAt": "2026-11-18T23:01:48.618485915Z"
      },
      "streak": {
        "days": 40,
        "from": "2026-10-09",
        "sinceWatching": true,
        "best": 40
      }
    },
    "edges": [
      {
        "by": 46,
        "category": "schema",
        "leads": "pplx-decider",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No machine-readable contract for the model was found (0 of 25). OpenRouter's llms.txt indexes its Decisions SDK pages as Markdown, earning 10 of 10 for the OpenRouter route. Microsoft's post states what the model is for and what it is not for, earning 15 of 20 without a reference page. The question fields (type, instructions and criteria) are typed in Microsoft's sample, earning 10 of 15, with no published schema read. The sample shows a request and handles an HTTP error, but no documented error responses were found, earning 8 of 15. No changelog was found, and OpenRouter says weights are updated continually while the API shape stays the same, so 0 of 15. Total 43. For 1.1: Foundry's list of models sold by Azure now has an entry for it (inputs, question formats, 32K tokens), still no machine-readable contract; no change to the award.",
          "b": "An OpenAPI 3.1.0 description of `POST /v1/decisions` is in docs.perplexity.ai/openapi.json, listed in llms.txt and embedded in the reference page. The preview file read on 9 October now returns 404 (25). llms.txt indexes the guide, the reference and five Decisions cookbook pages, each with a Markdown twin (10). The guide says what a decision model is, where to use it in place of a chat model and what it does not do, and now says when to pick each model and when grouping questions hurts accuracy. No page lists languages (18 of 20, up from 16). Questions are a union discriminated on `type`, with 1 to 128 questions, 1 to 255 options, 1 to 10 levels and unknown fields rejected. `model` is a free string, and `state` and `instructions` accept any string, object or array by design (13 of 15). Examples in Python, TypeScript and curl with a response, and a status table for 400, 401, 404, 405, 413, 429 and 5xx. The guide says `error.code` changes type between errors (14 of 15). Versioned model IDs and a `/v1` path, but a versioned name no longer pins a model. `pplx-decider-v1.1-27b` and `pplx-decider-v1-27b` now select v1.2, the guide says a retired name routes to its replacement, and the response echoes the name sent rather than the version that answered. The changelog dates entries by month only (9 of 15, down from 12). 89, down from 90."
        },
        "scores": {
          "a": 43,
          "b": 89
        }
      },
      {
        "by": 40,
        "category": "transparency",
        "leads": "pplx-decider",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No licence for the hosted model is stated in the announcement or the Tech Community post, re-read on 10 November, nor on OpenRouter's page per the 10 October check, and no Microsoft weights repository was found, so 0 of 30 for licence clarity. Microsoft's Foundry data page states no storage in the model, no training on prompts and processing within the geography or data zone, but abuse monitoring stores prompts for human review. The page does not say whether it covers this model, so 12 of 30. No dated deprecation policy was found, 0 of 20. The US and EU Datazone deployment types disclose where processing may happen, earning 10 of 20. No subprocessor list was read. Total 22.",
          "b": "The v1.2 weights and the `pplx_decider` inference package are public under Apache-2.0, with a `NOTICE` naming the base model and revision. Unlike v1.1, the repository has no training code, training config or data manifest, and the card describes the training data in prose. The hosted service is closed. The score moves from 24 to 26 of 30 because the inference code's licence is now stated, the reading given to SPEV and Clef, which publish weights and inference code without training code, less one point because the card and release manifest still say private. The API terms and DPA, readable on 17 October, agree that customer content does not train models, and the DPA deletes personal data within 30 days of the service ending. The FAQ, rewritten since 17 October, now says what the Privacy and Security page says, that retention depends on the API, model and account and zero data retention is not the default, so the statements agree. Neither states how long decision inputs are kept while the service runs (22 of 30, up from 16). Retirements are announced in the changelog and a retired name routes to its replacement, with no notice period and no notice dated finer than the month (8 of 20). The FAQ says compute is on AWS in North America. The DPA points to a subprocessor list on the trust centre, which is script-drawn and was not read, and promises ten business days' notice of new subprocessors other than model providers (10 of 20, up from 8). 26 + 22 + 8 + 10 = 66."
        },
        "scores": {
          "a": 34,
          "b": 74
        }
      },
      {
        "by": 33,
        "category": "ergonomics",
        "leads": "pplx-decider",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The response is one probability per option, and the caller sets the number of questions and options. This earns 20 of 25 for context cost. No pagination, filtering or per-request limits were found for this model, earning 10 of 20. No documented error codes and recovery actions were found, earning 5 of 20. No idempotency or retry guidance was found, earning 5 of 20. Three required fields, a Python sample and OpenRouter's alpha SDK in three languages earn 10 of 15, since the SDK method is alpha. Total 50.",
          "b": "Read as an API an agent calls for a decision. Answers are a few numbers per question, input may run to just under 256K tokens, and on v1.2 the state is read and billed once for all the questions in a request. No batch route or caching for the endpoint was found (20 of 25). The caller sets the whole output shape, with up to 128 questions, 255 options and 10 levels in a call (18 of 20). The error table gives a cause and an action for each status. 404 and 405 have empty bodies, 504 can be an HTML page, and an oversized image waits about a minute before a 504 where a 400 would be expected (14 of 20). A decision has no side effects and 429 names its wait. Identical requests can differ in the second decimal place, and on v1.2 the same question can score differently depending on what it is grouped with, which the guide documents (17 of 20). Three required fields. The official Python SDK 0.44.0 and TypeScript SDK 0.39.0 add `client.decisions.create` with typed questions and answers, though their examples still name `pplx-decider-v1.1-27b` (14 of 15, up from 7). 83, up from 76."
        },
        "scores": {
          "a": 50,
          "b": 83
        }
      },
      {
        "by": 25,
        "category": "reliability",
        "leads": "pplx-decider",
        "name": "Reliability",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40. For 1.1: Foundry's model list marks Microsoft-Decision-1.1 generally available, and Microsoft calls it ready for enterprise production, so the GA line earns 10 where Decision-1 had 0 in preview. 40 + 10 = 50.",
          "b": "Read as a hosted model API, the surface an agent would call. status.perplexity.com has an API component with uptime history and an incident feed. It has no Decisions component (20). The Decisions API was released on 1 October 2026 and its model changed to v1.2 on 16 October, so its record is 31 days long on 1 November. The feed, re-read on 1 November, has nothing after a Computer maintenance on 13 October, and its one incident since release, 'Elevated API errors and timeouts' on 9 October, says the API remained operational. A short clean record reads as 15 of 30 in this run (excaliclaw for 11 clean days, the OpenAI Decisions API for 26 days), so the 17 October 8 is brought into line (15). The guide states 10 requests a second per organisation shared by both models, and since 17 October publishes token limits for each, 15,000,000 a minute and 900,000,000 an hour for v1.2 (15). 429 carries `Retry-After`, successful responses carry `x-ratelimit-*` headers, the guide says to retry 5xx with backoff, and a decision has no side effects (15). The API FAQ, re-read on 1 November, says Perplexity does not guarantee uptime or recovery time (0). The guide carries no beta label, the OpenAPI description sits in the main `openapi.json` and both official SDKs have a Decisions method (10). 20 + 15 + 15 + 15 + 0 + 10 = 75."
        },
        "scores": {
          "a": 50,
          "b": 75
        }
      },
      {
        "by": 21,
        "category": "maintenance",
        "leads": "pplx-decider",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (30 + 0 + 0 + 10 + 0 = 40). The model was released on 9 October 2026, 32 days before this check, and no later dated change was found; the Command Line post was last modified on 10 October to add benchmarks (20 of 30, cause time). No deprecation policy or notice period for the model was found (0 of 12). No model or version has been removed, but OpenRouter says the weights are updated continually with no version names, per the 10 October check (4 of 8). No changelog (0 of 15). The one reader question under the Tech Community post, of 15 October, has no reply (0 of 10). OpenRouter's SDK lists the Decisions method in Python, TypeScript and Go as alpha, per the 10 October check; openrouter.ai isn't read in this run (10 of 15). No supported runtimes stated (0 of 10). 20 + 0 + 4 + 0 + 0 + 10 + 0 = 34. For 1.1: released 17 November 2026, the day before this check, so recency earns 30 where Decision-1 had 20. 34 + 10 = 44.",
          "b": "Read for a hosted model with open weights. The v1.2 weights were committed on 16 October 2026 and the changelog carries the switch under October 2026 (30). The guide now states that a retired version's name routes to its replacement, announced in the changelog. No notice period is given, and the v1.1 and v1 names were moved to v1.2 on the day it shipped, 11 and 15 days after those versions were released (3 of 12, down from 5). Three 27B versions in 15 days, and each older pinned name is now answered by a model whose card says it reads requests differently and gives different answers to v1.1-style prompts. That is model churn, so the item moves from 5 of 8 to 2 of 8, the reading given to Clef-flash's context cut on an unchanged model ID. The changelog has several entries a month, and support runs through a community forum, a GitHub discussion repository and email. Replies were not sampled (10 of 15). The official Python SDK 0.44.0 and TypeScript SDK 0.39.0 carry Decisions methods from 15 October, with four releases each from 25 September to 15 October (14 of 15, up from 7). The v1.2 repository pins its requirements (torch 2.14.0, transformers 5.17.0) and has an Apache-2.0 `pyproject.toml`. It has no lock file or CI, and its card and release manifest still call the repository private (6 of 10, up from 5). No Decisions change since 16 October. The Hugging Face repository's only later commit, on 19 October, adds a tag to the card, and the guide and changelog read on 1 November announce no new version. 30 + 3 + 2 + 10 + 14 + 6 = 65."
        },
        "scores": {
          "a": 44,
          "b": 65
        }
      },
      {
        "by": 16,
        "category": "security",
        "leads": "pplx-decider",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (credential, training, retention, operator visibility, programme), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (20 + 10 + 5 + 5 + 12 = 52). The Foundry sample uses a Microsoft Entra bearer token for a fixed resource scope; role assignments and token lifetimes weren't read, and OpenRouter uses an API key (20 of 30). Microsoft's data page for Foundry Models sold by Azure (updated 5 June 2026, re-read 10 November) says prompts and completions aren't used to train foundation models without permission and the models are stateless, but it doesn't name this model (10 of 20). The same page says abuse monitoring can store prompts for human review, with no period stated and a modified-monitoring application for managed customers; whether it covers this model isn't stated (5 of 15). OpenRouter's Activity page shows token volume and requests, per the 10 October check; Foundry diagnostic logs weren't read (5 of 15). Microsoft's security.txt names its coordinated vulnerability disclosure policy, a bounty and a reporting form, and was renewed to expire on 27 October 2027; no certification naming this model was read (12 of 20). 20 + 10 + 5 + 5 + 12 = 52.",
          "b": "Read for a model API. Project API keys are shown once, can be revoked, and can be generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found (22 of 30). The API terms of service, readable on 17 October, say Perplexity will not use Customer Content to train, retrain or fine-tune any generative AI model, and the DPA says personal data will not train its models. The FAQ, rewritten since 17 October, now agrees with the Privacy and Security page that retention depends on the API, model and account and that zero data retention is not the default and needs an account-level configuration under a written agreement. No retention period for decision inputs is stated, the reading typesafe-jev got for the same gap (13 of 20). The endpoint judges text and images that often come from users. It returns only probabilities and never fetches a URL, and the v1.2 card says literal special tokens in user content are neutralised so user text cannot create readout markers, which is a property of the published inference code. The hosted docs have no guidance on adversarial input (6 of 15, up from 5). Responses carry `x-request-id` and token usage, and admins see usage and per-key invoice lines in the console. No audit log was found (10 of 15). security.txt on www.perplexity.ai is valid until 31 December 2027 and links a security page naming a public vulnerability disclosure programme, a private bug bounty on Bugcrowd, annual third-party penetration tests and a SOC 2 Type II report. The trust centre is script-drawn and was not read, and no public advisories for the API were found (17 of 20, up from 12). 22 + 13 + 6 + 10 + 17 = 68."
        },
        "scores": {
          "a": 52,
          "b": 68
        }
      }
    ],
    "facts": [
      {
        "a": "Model API",
        "b": "Model API",
        "name": "Kind"
      },
      {
        "a": "Microsoft",
        "b": "Perplexity",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.perplexity.ai/v1/decisions",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "free",
        "b": "free",
        "name": "Price for decision models"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Not stated. Microsoft's post and OpenRouter's page name no licence for the hosted model. It's built on Gemma 4 26B A4B, and no Microsoft weights were released.",
        "b": "Apache-2.0 for the published weights and inference code. The hosted Decisions API is a proprietary service",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-17",
        "b": "2026-10-16",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "no date given",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "couldn't be read",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "3.5/5 (4)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "pplx-decider scores 71.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category.",
        "question": "Which is better for AI agents, Microsoft-Decision-1.1 or pplx-decider?"
      },
      {
        "answer": "Microsoft-Decision-1.1, at free against free for pplx-decider. These are the vendors' published prices for the job.",
        "question": "Which is cheaper for decision models, Microsoft-Decision-1.1 or pplx-decider?"
      },
      {
        "answer": "Microsoft-Decision-1.1 takes an API key or an OAuth sign-in. pplx-decider needs an API key.",
        "question": "Do Microsoft-Decision-1.1 and pplx-decider need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Microsoft-Decision-1.1. pplx-decider has a hosted endpoint at https://api.perplexity.ai/v1/decisions.",
        "question": "Can an agent call Microsoft-Decision-1.1 and pplx-decider without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": null,
        "also": [
          "Cheaper for decision models, $0 against $0 per 1M tokens"
        ],
        "goodFor": "Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.",
        "slug": "microsoft-decision-1-1",
        "watchFor": "No machine-readable contract or reference page with the request schema was found"
      },
      {
        "aheadOn": [
          "Reliability, 75 against 50",
          "Schema \u0026 documentation, 89 against 43",
          "Agent ergonomics, 83 against 50",
          "Security \u0026 auth, 68 against 52",
          "Payments \u0026 pricing, 38 against 30",
          "Maintenance \u0026 community, 65 against 44",
          "Transparency \u0026 trust, 74 against 34"
        ],
        "also": [
          "Cheaper for decision models, $0 against $0 per 1M tokens",
          "Agent-ready, a grade of BB or better",
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "High-volume classification, routing and rubric scoring over text and images where a team wants a low hosted price, several related questions per item and the option to run the same weights itself.",
        "slug": "pplx-decider",
        "watchFor": "Requests naming `pplx-decider-v1.1-27b` or `pplx-decider-v1-27b` are answered by v1.2 since 16 October 2026, with no notice period"
      }
    ],
    "history": {
      "microsoft-decision-1-1": null,
      "pplx-decider": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.7,
          "from": 70.1,
          "fromGrade": "BB",
          "to": 71.8,
          "toGrade": "BB"
        },
        {
          "causes": [
            "terms",
            "correction"
          ],
          "date": "2026-11-01",
          "delta": 2,
          "from": 68.1,
          "fromGrade": "B",
          "to": 70.1,
          "toGrade": "BB"
        },
        {
          "causes": [
            "method"
          ],
          "date": "2026-10-30",
          "delta": -0.1,
          "from": 68.2,
          "fromGrade": "B",
          "to": 68.1,
          "toGrade": "B"
        }
      ]
    },
    "job": {
      "capability": "inference.decision",
      "name": "Decision models"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/celeris-1-decision-vs-microsoft-decision-1-1.json",
        "title": "Celeris-1 Decision vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/celeris-1-decision-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/celeris-1-decision-vs-pplx-decider.json",
        "title": "Celeris-1 Decision vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/celeris-1-decision-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1.json",
        "title": "Clef vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-clef-vs-pplx-decider.json",
        "title": "Clef vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/cloudflare-clef-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/convai-laya-vs-microsoft-decision-1-1.json",
        "title": "Laya vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/convai-laya-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/convai-laya-vs-pplx-decider.json",
        "title": "Laya vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/convai-laya-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/decider-vs-microsoft-decision-1-1.json",
        "title": "Decider vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/decider-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/decider-vs-pplx-decider.json",
        "title": "Decider vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/decider-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.json",
        "title": "Decision 3.0 vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/decision-3-vs-pplx-decider.json",
        "title": "Decision 3.0 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/decision-3-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-decision-1-vs-microsoft-decision-1-1.json",
        "title": "Gemini Decision 1 vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/gemini-decision-1-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gemini-decision-1-vs-pplx-decider.json",
        "title": "Gemini Decision 1 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/gemini-decision-1-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gliclass-vs-microsoft-decision-1-1.json",
        "title": "GLiClass vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/gliclass-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gliclass-vs-pplx-decider.json",
        "title": "GLiClass vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/gliclass-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/granite-switch-vs-microsoft-decision-1-1.json",
        "title": "Granite Switch 4.1 vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/granite-switch-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/granite-switch-vs-pplx-decider.json",
        "title": "Granite Switch 4.1 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/granite-switch-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-microsoft-decision-1-1.json",
        "title": "Kev vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-pplx-decider.json",
        "title": "Kev vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/liquid-d1-vs-microsoft-decision-1-1.json",
        "title": "Liquid d1 vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/liquid-d1-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/liquid-d1-vs-pplx-decider.json",
        "title": "Liquid d1 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/liquid-d1-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-nace-drex.json",
        "title": "Microsoft-Decision-1.1 vs Drex 1.5",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-nace-drex"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.json",
        "title": "Microsoft-Decision-1.1 vs OpenAI Decisions API",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider-flash.json",
        "title": "Microsoft-Decision-1.1 vs pplx-decider-flash",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider-flash"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-rightnow-system-zero.json",
        "title": "Microsoft-Decision-1.1 vs RightNow System Zero",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-rightnow-system-zero"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-scaledown.json",
        "title": "Microsoft-Decision-1.1 vs ScaleDown",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-scaledown"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sprag-spev.json",
        "title": "Microsoft-Decision-1.1 vs SPEV",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sprag-spev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sqwish-kettei.json",
        "title": "Microsoft-Decision-1.1 vs kettei",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sqwish-kettei"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-strands-decider.json",
        "title": "Microsoft-Decision-1.1 vs Strands Decider 2B",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-strands-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-typesafe-jev.json",
        "title": "Microsoft-Decision-1.1 vs Jev",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-typesafe-jev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.json",
        "title": "Microsoft-Decision-1.1 vs Vela 2.0",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-vs-microsoft-decision-1-1.json",
        "title": "Microsoft-Decision-1 vs Microsoft-Decision-1.1",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-vs-microsoft-decision-1-1"
      },
      {
        "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-vs-pplx-decider.json",
        "title": "Microsoft-Decision-1 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nace-drex-vs-pplx-decider.json",
        "title": "Drex 1.5 vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/nace-drex-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/openai-decisions-api-vs-pplx-decider.json",
        "title": "OpenAI Decisions API vs pplx-decider",
        "url": "https://www.anchorterminal.com/compare/openai-decisions-api-vs-pplx-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-pplx-decider-flash.json",
        "title": "pplx-decider vs pplx-decider-flash",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-pplx-decider-flash"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-rightnow-system-zero.json",
        "title": "pplx-decider vs RightNow System Zero",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-rightnow-system-zero"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-scaledown.json",
        "title": "pplx-decider vs ScaleDown",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-scaledown"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-sprag-spev.json",
        "title": "pplx-decider vs SPEV",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-sprag-spev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-sqwish-kettei.json",
        "title": "pplx-decider vs kettei",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-sqwish-kettei"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-strands-decider.json",
        "title": "pplx-decider vs Strands Decider 2B",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-strands-decider"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-typesafe-jev.json",
        "title": "pplx-decider vs Jev",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-typesafe-jev"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pplx-decider-vs-vela.json",
        "title": "pplx-decider vs Vela 2.0",
        "url": "https://www.anchorterminal.com/compare/pplx-decider-vs-vela"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 25,
        "edge": "pplx-decider",
        "key": "reliability",
        "microsoft-decision-1-1": 50,
        "name": "Reliability",
        "pplx-decider": 75,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 46,
        "edge": "pplx-decider",
        "key": "schema",
        "microsoft-decision-1-1": 43,
        "name": "Schema \u0026 documentation",
        "pplx-decider": 89,
        "weight": 13
      },
      {
        "by": 33,
        "edge": "pplx-decider",
        "key": "ergonomics",
        "microsoft-decision-1-1": 50,
        "name": "Agent ergonomics",
        "pplx-decider": 83,
        "weight": 13
      },
      {
        "by": 16,
        "edge": "pplx-decider",
        "key": "security",
        "microsoft-decision-1-1": 52,
        "name": "Security \u0026 auth",
        "pplx-decider": 68,
        "weight": 14
      },
      {
        "by": 8,
        "edge": "pplx-decider",
        "key": "payments",
        "microsoft-decision-1-1": 30,
        "name": "Payments \u0026 pricing",
        "pplx-decider": 38,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 21,
        "edge": "pplx-decider",
        "key": "maintenance",
        "microsoft-decision-1-1": 44,
        "name": "Maintenance \u0026 community",
        "pplx-decider": 65,
        "weight": 7
      },
      {
        "by": 40,
        "edge": "pplx-decider",
        "key": "transparency",
        "microsoft-decision-1-1": 34,
        "name": "Transparency \u0026 trust",
        "pplx-decider": 74,
        "weight": 7
      }
    ],
    "summary": "pplx-decider scores 71.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category. Both do decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens.",
    "tasks": null,
    "tutorials": [
      {
        "title": "Find defect reports with Perplexity Decisions",
        "tool": "pplx-decider",
        "url": "https://www.anchorterminal.com/tutorials/pplx-decider/"
      }
    ],
    "verdicts": {
      "microsoft-decision-1-1": "A generally available decision model that returns a calibrated probability per option, now from images as well as text, at $0.042 per million input tokens with output free on Foundry and OpenRouter. No published schema, changelog, licence or deprecation policy was found.",
      "pplx-decider": "The hosted Decisions API now serves v1.2, with an OpenAPI description, typed questions, Python and TypeScript SDK methods and $0.02 per million input tokens, and the weights are public under Apache-2.0. Requests naming v1.1 or v1 are now answered by v1.2 with no notice period, and the response does not say which version answered."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider",
    "json": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.min.md"
  },
  "markdown": "pplx-decider scores 71.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category. Both do decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens.\n\n- Microsoft-Decision-1.1: grade E, 44.8/100, rank #1292 of 1557. Markdown https://www.anchorterminal.com/tools/microsoft-decision-1-1.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-decision-1-1.json\n- pplx-decider: grade BB, 71.8/100, rank #250 of 1557. Markdown https://www.anchorterminal.com/tools/pplx-decider.md · JSON https://www.anchorterminal.com/api/v1/tools/pplx-decider.json\n- Best decision models for AI agents: https://www.anchorterminal.com/best/decision-models/index.md\n- All 263 decisions comparisons: https://www.anchorterminal.com/compare/decision-models/index.md\n\n## Which one, for what\n\n### Microsoft-Decision-1.1 (E)\n\nGood for: Routing, classification, prioritisation and rubric checks over text, where a fixed set of options and a low price per token matter more than generated text.\n\nAlso in its favour:\n- Cheaper for decision models, $0 against $0 per 1M tokens\n\nWatch for: No machine-readable contract or reference page with the request schema was found\n\n### pplx-decider (BB)\n\nGood for: High-volume classification, routing and rubric scoring over text and images where a team wants a low hosted price, several related questions per item and the option to run the same weights itself.\n\nAhead on:\n- Reliability, 75 against 50\n- Schema \u0026 documentation, 89 against 43\n- Agent ergonomics, 83 against 50\n- Security \u0026 auth, 68 against 52\n- Payments \u0026 pricing, 38 against 30\n- Maintenance \u0026 community, 65 against 44\n- Transparency \u0026 trust, 74 against 34\n\nAlso in its favour:\n- Cheaper for decision models, $0 against $0 per 1M tokens\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n\nWatch for: Requests naming `pplx-decider-v1.1-27b` or `pplx-decider-v1-27b` are answered by v1.2 since 16 October 2026, with no notice period\n\n\n## Why the edge\n\n### Schema \u0026 documentation: pplx-decider +46\n\n- Microsoft-Decision-1.1 (43): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No machine-readable contract for the model was found (0 of 25). OpenRouter's llms.txt indexes its Decisions SDK pages as Markdown, earning 10 of 10 for the OpenRouter route. Microsoft's post states what the model is for and what it is not for, earning 15 of 20 without a reference page. The question fields (type, instructions and criteria) are typed in Microsoft's sample, earning 10 of 15, with no published schema read. The sample shows a request and handles an HTTP error, but no documented error responses were found, earning 8 of 15. No changelog was found, and OpenRouter says weights are updated continually while the API shape stays the same, so 0 of 15. Total 43. For 1.1: Foundry's list of models sold by Azure now has an entry for it (inputs, question formats, 32K tokens), still no machine-readable contract; no change to the award.\n- pplx-decider (89): An OpenAPI 3.1.0 description of `POST /v1/decisions` is in docs.perplexity.ai/openapi.json, listed in llms.txt and embedded in the reference page. The preview file read on 9 October now returns 404 (25). llms.txt indexes the guide, the reference and five Decisions cookbook pages, each with a Markdown twin (10). The guide says what a decision model is, where to use it in place of a chat model and what it does not do, and now says when to pick each model and when grouping questions hurts accuracy. No page lists languages (18 of 20, up from 16). Questions are a union discriminated on `type`, with 1 to 128 questions, 1 to 255 options, 1 to 10 levels and unknown fields rejected. `model` is a free string, and `state` and `instructions` accept any string, object or array by design (13 of 15). Examples in Python, TypeScript and curl with a response, and a status table for 400, 401, 404, 405, 413, 429 and 5xx. The guide says `error.code` changes type between errors (14 of 15). Versioned model IDs and a `/v1` path, but a versioned name no longer pins a model. `pplx-decider-v1.1-27b` and `pplx-decider-v1-27b` now select v1.2, the guide says a retired name routes to its replacement, and the response echoes the name sent rather than the version that answered. The changelog dates entries by month only (9 of 15, down from 12). 89, down from 90.\n\n### Transparency \u0026 trust: pplx-decider +40\n\n- Microsoft-Decision-1.1 (34): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. No licence for the hosted model is stated in the announcement or the Tech Community post, re-read on 10 November, nor on OpenRouter's page per the 10 October check, and no Microsoft weights repository was found, so 0 of 30 for licence clarity. Microsoft's Foundry data page states no storage in the model, no training on prompts and processing within the geography or data zone, but abuse monitoring stores prompts for human review. The page does not say whether it covers this model, so 12 of 30. No dated deprecation policy was found, 0 of 20. The US and EU Datazone deployment types disclose where processing may happen, earning 10 of 20. No subprocessor list was read. Total 22.\n- pplx-decider (74): The v1.2 weights and the `pplx_decider` inference package are public under Apache-2.0, with a `NOTICE` naming the base model and revision. Unlike v1.1, the repository has no training code, training config or data manifest, and the card describes the training data in prose. The hosted service is closed. The score moves from 24 to 26 of 30 because the inference code's licence is now stated, the reading given to SPEV and Clef, which publish weights and inference code without training code, less one point because the card and release manifest still say private. The API terms and DPA, readable on 17 October, agree that customer content does not train models, and the DPA deletes personal data within 30 days of the service ending. The FAQ, rewritten since 17 October, now says what the Privacy and Security page says, that retention depends on the API, model and account and zero data retention is not the default, so the statements agree. Neither states how long decision inputs are kept while the service runs (22 of 30, up from 16). Retirements are announced in the changelog and a retired name routes to its replacement, with no notice period and no notice dated finer than the month (8 of 20). The FAQ says compute is on AWS in North America. The DPA points to a subprocessor list on the trust centre, which is script-drawn and was not read, and promises ten business days' notice of new subprocessors other than model providers (10 of 20, up from 8). 26 + 22 + 8 + 10 = 66.\n\n### Agent ergonomics: pplx-decider +33\n\n- Microsoft-Decision-1.1 (50): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The response is one probability per option, and the caller sets the number of questions and options. This earns 20 of 25 for context cost. No pagination, filtering or per-request limits were found for this model, earning 10 of 20. No documented error codes and recovery actions were found, earning 5 of 20. No idempotency or retry guidance was found, earning 5 of 20. Three required fields, a Python sample and OpenRouter's alpha SDK in three languages earn 10 of 15, since the SDK method is alpha. Total 50.\n- pplx-decider (83): Read as an API an agent calls for a decision. Answers are a few numbers per question, input may run to just under 256K tokens, and on v1.2 the state is read and billed once for all the questions in a request. No batch route or caching for the endpoint was found (20 of 25). The caller sets the whole output shape, with up to 128 questions, 255 options and 10 levels in a call (18 of 20). The error table gives a cause and an action for each status. 404 and 405 have empty bodies, 504 can be an HTML page, and an oversized image waits about a minute before a 504 where a 400 would be expected (14 of 20). A decision has no side effects and 429 names its wait. Identical requests can differ in the second decimal place, and on v1.2 the same question can score differently depending on what it is grouped with, which the guide documents (17 of 20). Three required fields. The official Python SDK 0.44.0 and TypeScript SDK 0.39.0 add `client.decisions.create` with typed questions and answers, though their examples still name `pplx-decider-v1.1-27b` (14 of 15, up from 7). 83, up from 76.\n\n### Reliability: pplx-decider +25\n\n- Microsoft-Decision-1.1 (50): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. The Azure status history page lists Foundry Models among its products, with post-incident reviews kept for five years, earning 20 of 20. It's a shared component, not a page for this model. In the 90 days from 12 August, re-read on 10 November 2026, the one review naming Foundry Models is 29 September 2026 in Sweden Central, 10:03 to 15:58 UTC, with intermittent request failures and latency. That is one region and a share of requests, so partial and minor, as the Azure OpenAI fine-tuning, Speech, Translator and Document Intelligence listings read it. The 30 September gateway review doesn't name Foundry Models, and nothing is posted after it (20 of 30, was 10). No rate limit, 429 guidance or SLA for this model was found (0, 0 and 0). The model is still in public preview per the Tech Community post, so there is no general availability award (0). Total 40. For 1.1: Foundry's model list marks Microsoft-Decision-1.1 generally available, and Microsoft calls it ready for enterprise production, so the GA line earns 10 where Decision-1 had 0 in preview. 40 + 10 = 50.\n- pplx-decider (75): Read as a hosted model API, the surface an agent would call. status.perplexity.com has an API component with uptime history and an incident feed. It has no Decisions component (20). The Decisions API was released on 1 October 2026 and its model changed to v1.2 on 16 October, so its record is 31 days long on 1 November. The feed, re-read on 1 November, has nothing after a Computer maintenance on 13 October, and its one incident since release, 'Elevated API errors and timeouts' on 9 October, says the API remained operational. A short clean record reads as 15 of 30 in this run (excaliclaw for 11 clean days, the OpenAI Decisions API for 26 days), so the 17 October 8 is brought into line (15). The guide states 10 requests a second per organisation shared by both models, and since 17 October publishes token limits for each, 15,000,000 a minute and 900,000,000 an hour for v1.2 (15). 429 carries `Retry-After`, successful responses carry `x-ratelimit-*` headers, the guide says to retry 5xx with backoff, and a decision has no side effects (15). The API FAQ, re-read on 1 November, says Perplexity does not guarantee uptime or recovery time (0). The guide carries no beta label, the OpenAPI description sits in the main `openapi.json` and both official SDKs have a Decisions method (10). 20 + 15 + 15 + 15 + 0 + 10 = 75.\n\n### Maintenance \u0026 community: pplx-decider +21\n\n- Microsoft-Decision-1.1 (44): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (recency, notice, churn, changelog, replies, SDKs, runtimes), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (30 + 0 + 0 + 10 + 0 = 40). The model was released on 9 October 2026, 32 days before this check, and no later dated change was found; the Command Line post was last modified on 10 October to add benchmarks (20 of 30, cause time). No deprecation policy or notice period for the model was found (0 of 12). No model or version has been removed, but OpenRouter says the weights are updated continually with no version names, per the 10 October check (4 of 8). No changelog (0 of 15). The one reader question under the Tech Community post, of 15 October, has no reply (0 of 10). OpenRouter's SDK lists the Decisions method in Python, TypeScript and Go as alpha, per the 10 October check; openrouter.ai isn't read in this run (10 of 15). No supported runtimes stated (0 of 10). 20 + 0 + 4 + 0 + 0 + 10 + 0 = 34. For 1.1: released 17 November 2026, the day before this check, so recency earns 30 where Decision-1 had 20. 34 + 10 = 44.\n- pplx-decider (65): Read for a hosted model with open weights. The v1.2 weights were committed on 16 October 2026 and the changelog carries the switch under October 2026 (30). The guide now states that a retired version's name routes to its replacement, announced in the changelog. No notice period is given, and the v1.1 and v1 names were moved to v1.2 on the day it shipped, 11 and 15 days after those versions were released (3 of 12, down from 5). Three 27B versions in 15 days, and each older pinned name is now answered by a model whose card says it reads requests differently and gives different answers to v1.1-style prompts. That is model churn, so the item moves from 5 of 8 to 2 of 8, the reading given to Clef-flash's context cut on an unchanged model ID. The changelog has several entries a month, and support runs through a community forum, a GitHub discussion repository and email. Replies were not sampled (10 of 15). The official Python SDK 0.44.0 and TypeScript SDK 0.39.0 carry Decisions methods from 15 October, with four releases each from 25 September to 15 October (14 of 15, up from 7). The v1.2 repository pins its requirements (torch 2.14.0, transformers 5.17.0) and has an Apache-2.0 `pyproject.toml`. It has no lock file or CI, and its card and release manifest still call the repository private (6 of 10, up from 5). No Decisions change since 16 October. The Hugging Face repository's only later commit, on 19 October, adds a tag to the card, and the guide and changelog read on 1 November announce no new version. 30 + 3 + 2 + 10 + 14 + 6 = 65.\n\n### Security \u0026 auth: pplx-decider +16\n\n- Microsoft-Decision-1.1 (52): Read 18 November 2026 for Microsoft-Decision-1.1. Where 1.1's own pages don't cover a line, the reading is the Microsoft-Decision-1 listing's of 10 November, the same platform and route. Model reading of the checklist (credential, training, retention, operator visibility, programme), as the Google Lyria and Soundverse listings read it; the 10 October note read the tool lines (20 + 10 + 5 + 5 + 12 = 52). The Foundry sample uses a Microsoft Entra bearer token for a fixed resource scope; role assignments and token lifetimes weren't read, and OpenRouter uses an API key (20 of 30). Microsoft's data page for Foundry Models sold by Azure (updated 5 June 2026, re-read 10 November) says prompts and completions aren't used to train foundation models without permission and the models are stateless, but it doesn't name this model (10 of 20). The same page says abuse monitoring can store prompts for human review, with no period stated and a modified-monitoring application for managed customers; whether it covers this model isn't stated (5 of 15). OpenRouter's Activity page shows token volume and requests, per the 10 October check; Foundry diagnostic logs weren't read (5 of 15). Microsoft's security.txt names its coordinated vulnerability disclosure policy, a bounty and a reporting form, and was renewed to expire on 27 October 2027; no certification naming this model was read (12 of 20). 20 + 10 + 5 + 5 + 12 = 52.\n- pplx-decider (68): Read for a model API. Project API keys are shown once, can be revoked, and can be generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found (22 of 30). The API terms of service, readable on 17 October, say Perplexity will not use Customer Content to train, retrain or fine-tune any generative AI model, and the DPA says personal data will not train its models. The FAQ, rewritten since 17 October, now agrees with the Privacy and Security page that retention depends on the API, model and account and that zero data retention is not the default and needs an account-level configuration under a written agreement. No retention period for decision inputs is stated, the reading typesafe-jev got for the same gap (13 of 20). The endpoint judges text and images that often come from users. It returns only probabilities and never fetches a URL, and the v1.2 card says literal special tokens in user content are neutralised so user text cannot create readout markers, which is a property of the published inference code. The hosted docs have no guidance on adversarial input (6 of 15, up from 5). Responses carry `x-request-id` and token usage, and admins see usage and per-key invoice lines in the console. No audit log was found (10 of 15). security.txt on www.perplexity.ai is valid until 31 December 2027 and links a security page naming a public vulnerability disclosure programme, a private bug bounty on Bugcrowd, annual third-party penetration tests and a SOC 2 Type II report. The trust centre is script-drawn and was not read, and no public advisories for the API were found (17 of 20, up from 12). 22 + 13 + 6 + 10 + 17 = 68.\n\n## Score by category\n\n| Category | Weight | Microsoft-Decision-1.1 | pplx-decider | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 50 | 75 | pplx-decider +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 43 | 89 | pplx-decider +46 |\n| Agent ergonomics | 13% | 50 | 83 | pplx-decider +33 |\n| Security \u0026 auth | 14% | 52 | 68 | pplx-decider +16 |\n| Payments \u0026 pricing | 10% | 30 | 38 | pplx-decider +8 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 44 | 65 | pplx-decider +21 |\n| Transparency \u0026 trust | 7% | 34 | 74 | pplx-decider +40 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **44.8 · E** | **71.8 · BB** | |\n\n## Facts side by side\n\n| Fact | Microsoft-Decision-1.1 | pplx-decider |\n| --- | --- | --- |\n| Kind | Model API | Model API |\n| Vendor | Microsoft | Perplexity |\n| Hosted endpoint | no (local only) | `https://api.perplexity.ai/v1/decisions` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for decision models | free | free |\n| x402 | no | no |\n| Licence | Not stated. Microsoft's post and OpenRouter's page name no licence for the hosted model. It's built on Gemma 4 26B A4B, and no Microsoft weights were released. | Apache-2.0 for the published weights and inference code. The hosted Decisions API is a proprietary service |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-11-17 | 2026-10-16 |\n| Terms last updated | no document linked | couldn't be read |\n| Privacy policy last updated | no date given | couldn't be read |\n| Customer content may train models | not read yet | couldn't be read |\n| Terms restrict automated access | not read yet | couldn't be read |\n| Terms restrict benchmarking | not read yet | couldn't be read |\n| Terms or service can change without notice | not read yet | couldn't be read |\n| Arbitration or class-action waiver | not read yet | couldn't be read |\n| Agent reviews | none | 3.5/5 (4) |\n\n## How the scores have moved\n\n### Microsoft-Decision-1.1\n\nNo score change since it was listed.\n\n### pplx-decider\n\n- +1.7 on 13 November 2026: checklist\n- +2.0 on 1 November 2026 (B to BB): terms, correction\n- -0.1 on 30 October 2026: checklist\n\n## Verdicts\n\n**Microsoft-Decision-1.1.** A generally available decision model that returns a calibrated probability per option, now from images as well as text, at $0.042 per million input tokens with output free on Foundry and OpenRouter. No published schema, changelog, licence or deprecation policy was found.\n\n**pplx-decider.** The hosted Decisions API now serves v1.2, with an OpenAPI description, typed questions, Python and TypeScript SDK methods and $0.02 per million input tokens, and the weights are public under Apache-2.0. Requests naming v1.1 or v1 are now answered by v1.2 with no notice period, and the response does not say which version answered.\n\n## Before you call either\n\n### Microsoft-Decision-1.1\n\n1. On Foundry, deploy Microsoft-Decision-1.1 in a Foundry resource and call it with a Microsoft Entra bearer token\n2. On OpenRouter, call microsoft/microsoft-decision-1.1 through the Decisions API, not chat completions\n3. Send fixed answer options and read the probabilities; it writes no explanation\n4. Set a confidence threshold and defer to a larger model below it\n\n### pplx-decider\n\n1. Send `Authorization: Bearer`. A key in `x-api-key` returns 401 on this endpoint.\n2. Pin `pplx-decider-v1.2` and log it with each result. Old names and aliases route to newer versions, and the response echoes the name sent.\n3. Revalidate thresholds set on v1.1. The v1.2 card says it gives different answers to v1.1-style requests.\n4. Group questions that are facets of one decision. Send independent candidates, such as documents or tools, in separate requests.\n5. Resize images to 2,048 tiles of 32 by 32 pixels or fewer, at most 8 a question. Larger images end in a 504 after about a minute.\n6. For the weights, use the repository's `pplx_decider` package. The card says default causal inference does not reproduce the checkpoint.\n\n## Tutorials\n\n- [Find defect reports with Perplexity Decisions](https://www.anchorterminal.com/tutorials/pplx-decider/), for pplx-decider\n\n## Questions\n\n### Which is better for AI agents, Microsoft-Decision-1.1 or pplx-decider?\n\npplx-decider scores 71.8 (BB) on agent readiness against Microsoft-Decision-1.1's 44.8 (E), and leads in every scored category.\n\n### Which is cheaper for decision models, Microsoft-Decision-1.1 or pplx-decider?\n\nMicrosoft-Decision-1.1, at free against free for pplx-decider. These are the vendors' published prices for the job.\n\n### Do Microsoft-Decision-1.1 and pplx-decider need an API key?\n\nMicrosoft-Decision-1.1 takes an API key or an OAuth sign-in. pplx-decider needs an API key.\n\n### Can an agent call Microsoft-Decision-1.1 and pplx-decider without installing anything?\n\nNo hosted endpoint is listed for Microsoft-Decision-1.1. pplx-decider has a hosted endpoint at https://api.perplexity.ai/v1/decisions.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.json, and with the fewest tokens: https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"microsoft-decision-1-1\", \"b\": \"pplx-decider\"}`. From a terminal: `anchor compare microsoft-decision-1-1 pplx-decider`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/microsoft-decision-1-1.json and https://www.anchorterminal.com/api/v1/tools/pplx-decider.json\n\n## Other comparisons with Microsoft-Decision-1.1 or pplx-decider\n\n- [Celeris-1 Decision vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/celeris-1-decision-vs-microsoft-decision-1-1.md)\n- [Celeris-1 Decision vs pplx-decider](https://www.anchorterminal.com/compare/celeris-1-decision-vs-pplx-decider.md)\n- [Clef vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/cloudflare-clef-vs-microsoft-decision-1-1.md)\n- [Clef vs pplx-decider](https://www.anchorterminal.com/compare/cloudflare-clef-vs-pplx-decider.md)\n- [Laya vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/convai-laya-vs-microsoft-decision-1-1.md)\n- [Laya vs pplx-decider](https://www.anchorterminal.com/compare/convai-laya-vs-pplx-decider.md)\n- [Decider vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/decider-vs-microsoft-decision-1-1.md)\n- [Decider vs pplx-decider](https://www.anchorterminal.com/compare/decider-vs-pplx-decider.md)\n- [Decision 3.0 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/decision-3-vs-microsoft-decision-1-1.md)\n- [Decision 3.0 vs pplx-decider](https://www.anchorterminal.com/compare/decision-3-vs-pplx-decider.md)\n- [Gemini Decision 1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/gemini-decision-1-vs-microsoft-decision-1-1.md)\n- [Gemini Decision 1 vs pplx-decider](https://www.anchorterminal.com/compare/gemini-decision-1-vs-pplx-decider.md)\n- [GLiClass vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/gliclass-vs-microsoft-decision-1-1.md)\n- [GLiClass vs pplx-decider](https://www.anchorterminal.com/compare/gliclass-vs-pplx-decider.md)\n- [Granite Switch 4.1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/granite-switch-vs-microsoft-decision-1-1.md)\n- [Granite Switch 4.1 vs pplx-decider](https://www.anchorterminal.com/compare/granite-switch-vs-pplx-decider.md)\n- [Kev vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-microsoft-decision-1-1.md)\n- [Kev vs pplx-decider](https://www.anchorterminal.com/compare/jaredpalmer-kev-vs-pplx-decider.md)\n- [Liquid d1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/liquid-d1-vs-microsoft-decision-1-1.md)\n- [Liquid d1 vs pplx-decider](https://www.anchorterminal.com/compare/liquid-d1-vs-pplx-decider.md)\n- [Microsoft-Decision-1.1 vs Drex 1.5](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-nace-drex.md)\n- [Microsoft-Decision-1.1 vs OpenAI Decisions API](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-openai-decisions-api.md)\n- [Microsoft-Decision-1.1 vs pplx-decider-flash](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider-flash.md)\n- [Microsoft-Decision-1.1 vs RightNow System Zero](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-rightnow-system-zero.md)\n- [Microsoft-Decision-1.1 vs ScaleDown](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-scaledown.md)\n- [Microsoft-Decision-1.1 vs SPEV](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sprag-spev.md)\n- [Microsoft-Decision-1.1 vs kettei](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-sqwish-kettei.md)\n- [Microsoft-Decision-1.1 vs Strands Decider 2B](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-strands-decider.md)\n- [Microsoft-Decision-1.1 vs Jev](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-typesafe-jev.md)\n- [Microsoft-Decision-1.1 vs Vela 2.0](https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-vela.md)\n- [Microsoft-Decision-1 vs Microsoft-Decision-1.1](https://www.anchorterminal.com/compare/microsoft-decision-1-vs-microsoft-decision-1-1.md)\n- [Microsoft-Decision-1 vs pplx-decider](https://www.anchorterminal.com/compare/microsoft-decision-1-vs-pplx-decider.md)\n- [Drex 1.5 vs pplx-decider](https://www.anchorterminal.com/compare/nace-drex-vs-pplx-decider.md)\n- [OpenAI Decisions API vs pplx-decider](https://www.anchorterminal.com/compare/openai-decisions-api-vs-pplx-decider.md)\n- [pplx-decider vs pplx-decider-flash](https://www.anchorterminal.com/compare/pplx-decider-vs-pplx-decider-flash.md)\n- [pplx-decider vs RightNow System Zero](https://www.anchorterminal.com/compare/pplx-decider-vs-rightnow-system-zero.md)\n- [pplx-decider vs ScaleDown](https://www.anchorterminal.com/compare/pplx-decider-vs-scaledown.md)\n- [pplx-decider vs SPEV](https://www.anchorterminal.com/compare/pplx-decider-vs-sprag-spev.md)\n- [pplx-decider vs kettei](https://www.anchorterminal.com/compare/pplx-decider-vs-sqwish-kettei.md)\n- [pplx-decider vs Strands Decider 2B](https://www.anchorterminal.com/compare/pplx-decider-vs-strands-decider.md)\n- [pplx-decider vs Jev](https://www.anchorterminal.com/compare/pplx-decider-vs-typesafe-jev.md)\n- [pplx-decider vs Vela 2.0](https://www.anchorterminal.com/compare/pplx-decider-vs-vela.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Microsoft-Decision-1.1 vs pplx-decider",
        "url": ""
      }
    ],
    "description": "pplx-decider scores 71.8 (BB) to Microsoft-Decision-1.1's 44.8 (E) for decision models. Microsoft-Decision-1.1 is cheaper for decision models, $0 against $0 per 1M tokens. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Microsoft-Decision-1.1 E 44.8",
      "pplx-decider BB 71.8",
      "scores"
    ],
    "h1": "Microsoft-Decision-1.1 vs pplx-decider",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/microsoft-decision-1-1-vs-pplx-decider",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Microsoft-Decision-1.1 vs pplx-decider for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/microsoft-decision-1-1-vs-pplx-decider"
  },
  "tokens": {
    "markdown": 7250,
    "slim": 1330
  },
  "version": 1
}
