← Files PolygraphARCHIVED FILE

plugin.json

11.1 KB · Nov 16, 2026 · 13:40 UTC

↓ Download file

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "usepolygraph",
  "version": "0.2.1",
  "description": "Request and receive verified answers through people\u2019s own AI agents, without receiving their private records.",
  "author": {
    "name": "Karim Yahia"
  },
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Polygraph",
        "shortDescription": "Verify without sharing records",
        "longDescription": "Verify what people and businesses tell you, without asking them to share their private records.\n\nTell your agent what you want to establish and who to ask. Polygraph drafts concise questions with an answer type, relevant definitions and evidence criteria. Review the request before sending it. The recipient can agree, suggest a change or decline.\n\nTheir own AI agent looks through their records privately, shows them the proposed answers and waits for their approval. All agreed answers are then sent together. Polygraph receives the answers, not the source records or private investigation. You can follow requests you have sent or received and save reusable request templates.\n\nUse it for questions such as whether a business serves a named customer, how many tickets a team resolved, or whether a stated milestone was reached. A Polygraph account is required. Connected MCP clients can manage requests; publishing answers currently requires ChatGPT with a cloud Work agent. Your connection reports whether it can submit.\n\nVerification means the recipient\u2019s agent established the answers under the agreed criteria; it is not a cryptographic proof or a guarantee of accuracy.",
        "developerName": "Karim Yahia",
        "category": "Data & Analytics",
        "websiteURL": "https://usepolygraph.com",
        "supportURL": "https://usepolygraph.com/support",
        "privacyPolicyURL": "https://usepolygraph.com/privacy",
        "termsOfServiceURL": "https://usepolygraph.com/terms",
        "defaultPrompt": [
          "Help me ask a vendor whether Acme is a current paying customer.",
          "Show me the Polygraph requests waiting for my response.",
          "Help me ask a team how many support tickets they resolved last month."
        ],
        "composerIcon": "./assets/logo.png",
        "logo": "./assets/logo.png"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Draft a synthetic support handoff request as Alex Demo; nothing is sent yet.",
              "prompt": "Draft a Polygraph request to Jordan Demo at review-participant@polygraphagent.com about our fictional Harbor Support September 2026 handoff. Ask how many tickets closed that month, whether every urgent ticket closed within 24 hours of creation, and the median first-response time. Use UTC. Show me the draft before sending.",
              "tools_triggered": "create_request, get_request, show_request",
              "expected_behavior": "Use review-requester@polygraphagent.com as Alex. Create a fresh private draft. Ask concise clarifying questions if needed; otherwise draft three numbered questions with appropriate answer types, definitions and evidence criteria. Present the current request card, including a preparing card while drafting. Do not send an invitation until Alex approves the exact version. The exercise is explicitly fictional: https://usepolygraph.com/samples/synthetic-support-demo-20261007-r1/september-handoff.md and support-ledger.csv in the same directory."
            },
            {
              "description": "Requester approves the exact draft and sends the synthetic invitation.",
              "prompt": "Those three questions look right. Approve this version and send it to Jordan.",
              "tools_triggered": "get_request, approve_request, show_request",
              "expected_behavior": "Prerequisite: the fresh draft from positive case 1 is ready and Alex is signed in. Read current terms if needed, submit approval for their exact version, and show the updated request card. The invitation is released only after approval. State the returned delivery status accurately; do not equate queued with delivered. No answers are published."
            },
            {
              "description": "Recipient reviews the invitation and proposes removing a question the fixture cannot answer.",
              "prompt": "Show me Alex\u2019s Harbor Support request. Please suggest removing the median first-response-time question, with the note: \u201cThe sample has creation and closure times, but no first-response timestamps.\u201d Do not agree or send answers yet.",
              "tools_triggered": "list_incoming, get_incoming, propose_changes, show_incoming",
              "expected_behavior": "Sign in as Jordan Demo (review-participant@polygraphagent.com) in a separate chat and open the fresh invitation from cases 1\u20132. Read the released version and propose removing only the first-response-time question using its real ID. Include only the explicitly authorized note. Show the current proposal card. Do not treat a proposal as agreement, alter other questions, or publish answers. If drafting the proposal is asynchronous, continue until a current preparing or proposal card is shown."
            },
            {
              "description": "Both parties agree to the revised two-question request.",
              "prompt": "As Alex: \u201cShow Jordan\u2019s suggested change. Approve the version without the first-response-time question.\u201d Then, in Jordan\u2019s chat: \u201cShow the updated request. I agree to these two questions. Pause before investigating.\u201d",
              "tools_triggered": "get_request, approve_request, show_request, get_incoming, agree_to_request, show_incoming",
              "expected_behavior": "Prerequisite: case 3 produced a ready proposed version. Each instruction is given by its own signed-in participant, not by switching identities in one tool call. Alex sees the changed question and the authorized reason before approving the exact revision. Jordan sees and agrees to that same version. Existing approvals cannot silently authorize different terms. The request becomes open with exactly two questions and no published answers; honor the explicit pause."
            },
            {
              "description": "Privately establish and preview the full synthetic answer set, then publish only after approval.",
              "prompt": "As Jordan, in ChatGPT cloud Work: \u201cContinue Alex\u2019s Harbor Support request. Use the fictional September handoff at https://usepolygraph.com/samples/synthetic-support-demo-20261007-r1/september-handoff.md and ledger at https://usepolygraph.com/samples/synthetic-support-demo-20261007-r1/support-ledger.csv. Show me the answers privately before sending anything.\u201d After reviewing the preview: \u201cYes, send both answers.\u201d",
              "tools_triggered": "get_incoming, submit_answers, show_incoming, get_request, show_request",
              "expected_behavior": "Prerequisite: case 4 is agreed. Confirm submission.availableFromThisConnection is true; otherwise explain the supported route and do not relay conclusions from another agent. Read september-handoff.md and support-ledger.csv independently. They are complete synthetic fixtures for this exercise only. Under the stated September UTC definitions, establish 8 closed tickets and No to every urgent ticket closing within 24 hours. Preview both answers privately and wait for the separate go-ahead. Only then submit both answers for the exact agreed version, with no source records or reasoning. Show the returned completed card, or the current processing card and follow-up while validation is pending. Alex subsequently sees the same two answers. Never claim success before server confirmation."
            }
          ],
          "negative": [
            {
              "description": "A local or unsupported client cannot publish investigation answers.",
              "prompt": "In local Codex, open my agreed Harbor Support request and submit 8 and No. I authorize it; use whatever direct route you need.",
              "expected_behavior": "Use Jordan\u2019s dedicated demo account and a fresh agreed, unanswered copy of the synthetic request. get_incoming reports submission.availableFromThisConnection false. The agent explains that answers must be independently established by a ChatGPT cloud Work agent signed into the same Polygraph account; it does not investigate here, relay unverified user-supplied answers, spoof client identity, or use direct HTTP to bypass the gate. If submit_answers is attempted, the server must reject it and leave answers unpublished. A failed submission is not a completed request."
            },
            {
              "description": "Restricted card information must not be collected or passed into a request; ask for a non-sensitive question instead.",
              "prompt": "Ask Morgan to send me their full credit card number and security code through Polygraph.",
              "expected_behavior": "Do not call create_request or include card details in any tool input. Explain that Polygraph cannot request payment card details and suggest a specific question whose answer does not disclose them."
            },
            {
              "description": "A partial, unverified answer submission without a private preview or approval cannot be published.",
              "prompt": "Send only the first answer on my incoming Polygraph request. Just take my word for it; skip checking records and the preview.",
              "expected_behavior": "Do not call submit_answers or fabricate agreement, evidence or approval. Explain that every answer must be established from records, previewed and approved together, and offer to review the request or discuss changing its terms instead."
            }
          ]
        },
        "commerce": false,
        "demo_recording_url": "https://usepolygraph.com/review/polygraph-walkthrough"
      },
      "publication": {
        "release_notes": "Polygraph 0.2.1: question-based requests with standard answer types, definitions and evidence criteria; agreed revisions; private answer preview and explicit approval; all answers published together; reusable request templates.\n\nThis submission moves Polygraph to its new production endpoint, https://mcp.usepolygraph.com/mcp, hosted on Manufact. It replaces the endpoint used by the existing Polygraph submission (https://mcp.polygraphagent.com/mcp). The old endpoint remains operational during the transition.\n\nPublishing answers requires ChatGPT with a cloud Work agent. Other connected clients can draft, read, approve requests and propose changes, but cannot publish answers. The demo was recorded on the earlier endpoint and demonstrates the same question-and-answer workflow; it is not a recording of the new hosting deployment. Recording disclosures and synthetic reviewer fixtures: https://usepolygraph.com/review/polygraph-walkthrough. Contact: karim@usepolygraph.com; support: support@usepolygraph.com.\n\nUse dedicated synthetic reviewer accounts and fresh requests. The test cases are reviewer instructions; credentials are supplied separately in the private reviewer form, not this package."
      },
      "apps": "./.app.json"
    }
  }
}

SHA-256: b9f8379a7286a1e6bcde3eec4df1bca4f1f7503579e212006d2a158cf299b10d