{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-UCP-AUTHENTICATION-PROFILE-PRINCIPAL-BINDING-01-v1",
  "record_kind": "external_reference",
  "title": "UCP authentication and profile identity",
  "system": "Universal Commerce Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does UCP require one universal authentication scheme for every merchant endpoint?",
  "near_questions": [
    "Which authentication methods does UCP support?",
    "Must an authenticated UCP principal match its advertised profile?",
    "Are UCP business-to-platform webhooks required to be signed?",
    "Does discovering a UCP profile authenticate the caller?"
  ],
  "supported_claims": [
    {
      "claim": "UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Profile discovery as permissionless access to private merchant operations",
    "The merchant configuration and successful verification of a real request are not established here.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Overview - Universal Commerce Protocol (UCP)",
    "source_url": "https://ucp.dev/2026-08-25/specification/overview/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-UCP-AUTHENTICATION-PROFILE-PRINCIPAL-BINDING-01-v1",
    "candidate_record_sha256": "7a831797dfeef2048821c392efba7991699aff9b1ec2b2084b59c4da17429eca",
    "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": "UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.",
    "required_buyer_context": "Endpoint authentication mechanism and validated principal; UCP-Agent profile and authorised representation binding; Required message signatures and verification evidence. 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 UCP require one universal authentication scheme for every merchant endpoint?",
    "documented_statement": {
      "status": "documented",
      "statement": "UCP v2026-08-25 supports API keys, OAuth, mutual TLS and HTTP Message Signatures. Regardless of mechanism, the authenticated identity must be consistent with the advertised UCP-Agent profile; business-to-platform webhooks must be signed. A discoverable profile therefore does not remove identity-binding requirements or prove a particular deployment uses the expected authentication method.",
      "source_ids": [
        "ucp-overview"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check the mechanism and principal-to-profile binding for the actual endpoint before relying on its capability declaration.",
      "source_ids": [
        "ucp-overview"
      ]
    },
    "buyer_evidence_required": [
      "Endpoint authentication mechanism and validated principal",
      "UCP-Agent profile and authorised representation binding",
      "Required message signatures and verification evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not accept a profile advertisement as authenticated identity without the applicable binding checks."
    },
    "unknowns": "The merchant configuration and successful verification of a real request are not established here.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The merchant configuration and successful verification of a real request are not established here."
    },
    "evidence_sources": [
      {
        "source_id": "ucp-overview",
        "url": "https://ucp.dev/2026-08-25/specification/overview/",
        "final_url": "https://ucp.dev/2026-08-25/specification/overview/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:54.710Z",
        "sha256": "0898f8e754a4c123766153326f5d0fd5e73937f0e28346829acbde93671d8626",
        "bytes": 565554,
        "title": "Overview - Universal Commerce Protocol (UCP)",
        "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": "UCP specification v2026-08-25, explicitly versioned documentation; deployment applicability must be checked.",
        "reviewed_sections": [
          "Capability negotiation",
          "Authentication and principal binding",
          "Profile caching and versioning"
        ]
      }
    ],
    "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": "Avoid trusting capability metadata from a mismatched or impersonated principal.",
      "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": "Avoid trusting capability metadata from a mismatched or impersonated principal.",
    "refusal_conditions": [
      "Do not accept a profile advertisement as authenticated identity without the applicable binding checks."
    ]
  },
  "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": "Avoid trusting capability metadata from a mismatched or impersonated principal.",
    "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#ucp-authentication-profile-principal-binding",
  "machine_readable_record": "/varexis-index/records/ucp-authentication-profile-principal-binding.json"
}
