{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-MPP-REQUEST-BODY-DIGEST-RESOURCE-BINDING-01-v1",
  "record_kind": "external_reference",
  "title": "MPP payment proof and request-body binding",
  "system": "Machine Payments Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an MPP payment credential automatically authorise a different request body or resource?",
  "near_questions": [
    "Can an MPP client change a POST body after receiving a challenge?",
    "What does the MPP digest parameter bind?",
    "Does challenge integrity alone identify the authorised API route?",
    "Can one payment receipt authorise an unrelated resource request?"
  ],
  "supported_claims": [
    {
      "claim": "MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A payment receipt as unrestricted access to other resources",
    "The server may omit body binding or route checks; this review does not test its enforcement.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Protocol overview | MPP",
    "source_url": "https://mpp.dev/protocol/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MPP-REQUEST-BODY-DIGEST-RESOURCE-BINDING-01-v1",
    "candidate_record_sha256": "4c82ca0e04f1fc5682ea9b94ca5707d5b33df9720d6357f58c4104d8648a4dcc",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.",
    "required_buyer_context": "Original challenge and expected route context; Original and submitted request-body digests; Verified payment proof and authorised resource scope. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does an MPP payment credential automatically authorise a different request body or resource?",
    "documented_statement": {
      "status": "documented",
      "statement": "MPP supports a digest parameter binding a challenge to the request body. When present, the submitted body must match that digest. The security guidance also requires verification of amount, currency, recipient and route-level context. Challenge integrity therefore needs to be connected to the actual paid request; a receipt or payment proof is not a general-purpose resource authorisation.",
      "source_ids": [
        "mpp-protocol",
        "mpp-security",
        "mpp-challenges"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check the challenge-to-request binding before reusing payment evidence for an amended API call.",
      "source_ids": [
        "mpp-protocol",
        "mpp-security",
        "mpp-challenges"
      ]
    },
    "buyer_evidence_required": [
      "Original challenge and expected route context",
      "Original and submitted request-body digests",
      "Verified payment proof and authorised resource scope"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a different body or resource when the required challenge binding cannot be established."
    },
    "unknowns": "The server may omit body binding or route checks; this review does not test its enforcement.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The server may omit body binding or route checks; this review does not test its enforcement."
    },
    "evidence_sources": [
      {
        "source_id": "mpp-protocol",
        "url": "https://mpp.dev/protocol/",
        "final_url": "https://mpp.dev/protocol/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:55.047Z",
        "sha256": "d2dec7ff4cb5cb7ce170bde0ab0826ffa15fcc1aa44e821900f5a1aca8196be0",
        "bytes": 259178,
        "title": "Protocol overview | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Challenge/credential/receipt flow",
          "Method-specific verification",
          "Authentication and policy status"
        ]
      },
      {
        "source_id": "mpp-security",
        "url": "https://mpp.dev/advanced/security",
        "final_url": "https://mpp.dev/advanced/security",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:47.274Z",
        "sha256": "9b8c683cab824f7aa00fab529d2cfecab9eb37d744d4000780e6b3b20d254db2",
        "bytes": 192685,
        "title": "Security | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Request binding",
          "Atomic shared replay state",
          "Description trust"
        ]
      },
      {
        "source_id": "mpp-challenges",
        "url": "https://mpp.dev/protocol/challenges",
        "final_url": "https://mpp.dev/protocol/challenges",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:46.859Z",
        "sha256": "3e491b0dd642c4311f4cf70f2fb610d9b3fb938039444ec6c85c90e97ec214af",
        "bytes": 206406,
        "title": "Challenges | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Request amount, currency and recipient",
          "expires and digest"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Keep delegated spending attached to the exact operation it was intended to fund.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Keep delegated spending attached to the exact operation it was intended to fund.",
    "refusal_conditions": [
      "Refuse a different body or resource when the required challenge binding cannot be established."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "payments",
    "classification_label": "Agent Payments, Authority & Transaction Evidence",
    "topic_id": "payments",
    "buyer_intent": "Keep delegated spending attached to the exact operation it was intended to fund.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#mpp-request-body-digest-resource-binding",
  "machine_readable_record": "/varexis-index/records/mpp-request-body-digest-resource-binding.json"
}
