Back to Kazakhstan Corridor Risk Agent

Card snapshot

kazakhstan-corridor-risk-a2a.vassiliy-lakhonin.workers.dev · 2026-05-24 17:08:10 UTC · 47bf187605de13c26f77f898eed93e2e321ed4e3a243af53578dd43da0f56035

This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.

{
  "protocolVersion": "1.0",
  "name": "Kazakhstan Corridor Risk Agent",
  "description": "Live no-payment A2A/JSON-RPC agent for Kazakhstan and Central Asia corridor-risk triage: sanctions exposure, Middle Corridor and Trans-Caspian logistics disruption, policy signals, source gaps, watch-next indicators, and routing into the installable Agenda Intelligence MD MCP server.",
  "url": "https://kazakhstan-corridor-risk-a2a.vassiliy-lakhonin.workers.dev",
  "provider": {
    "organization": "Vassiliy Lakhonin",
    "url": "https://vassiliylakhonin.github.io/",
    "legalEntity": {
      "type": "individual",
      "name": "Vassiliy Lakhonin",
      "url": "https://vassiliylakhonin.github.io/verification.json",
      "sameAs": [
        "https://github.com/vassiliylakhonin",
        "https://pypi.org/project/agenda-intelligence-md/",
        "https://glama.ai/mcp/servers/vassiliylakhonin/agenda-intelligence-md",
        "https://agenstry.com/agents/kazakhstan-corridor-risk-a2a.vassiliy-lakhonin.workers.dev"
      ]
    }
  },
  "version": "1.0.1",
  "documentationUrl": "https://github.com/vassiliylakhonin/agenda-intelligence-md/blob/main/MCP.md",
  "supportedInterfaces": [
    {
      "url": "https://kazakhstan-corridor-risk-a2a.vassiliy-lakhonin.workers.dev/message/send",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    }
  ],
  "protocolVersions": [
    "1.0"
  ],
  "securitySchemes": {
    "optionalClientId": {
      "apiKeySecurityScheme": {
        "location": "header",
        "name": "X-Client-Id",
        "description": "Optional caller identifier for observability and abuse triage. The public lightweight triage endpoint does not require an access key."
      }
    }
  },
  "securityRequirements": [],
  "security": [],
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "stateTransitionHistory": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "application/json",
    "text/plain",
    "text/markdown"
  ],
  "defaultOutputModes": [
    "application/json",
    "text/markdown"
  ],
  "skills": [
    {
      "id": "kazakhstan-sanctions-exposure-screen",
      "name": "Kazakhstan sanctions exposure screen",
      "description": "Returns first-pass triage for Kazakhstan-linked sanctions exposure: affected counterparties, corridor touchpoints, source categories required, evidence gaps, and watch-next indicators.",
      "tags": [
        "kazakhstan",
        "sanctions",
        "secondary-sanctions",
        "trade-compliance",
        "central-asia",
        "source-coverage",
        "free"
      ],
      "examples": [
        "Screen sanctions exposure for a Kazakhstan logistics route with Russia-linked counterparties.",
        "Find evidence gaps before writing a sanctions-risk note on Kazakhstan transit."
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/markdown"
      ]
    },
    {
      "id": "middle-corridor-risk-triage",
      "name": "Middle Corridor risk triage",
      "description": "Routes Middle Corridor and Trans-Caspian questions into structured risk triage covering bottlenecks, sanctions spillover, policy signals, logistics disruption, and required evidence categories.",
      "tags": [
        "middle-corridor",
        "trans-caspian",
        "logistics-risk",
        "corridor-risk",
        "kazakhstan",
        "caspian"
      ],
      "examples": [
        "Analyze how Caspian port disruption changes risk for a Kazakhstan-Europe logistics corridor.",
        "Prepare a corridor-risk screen for Aktau, Kuryk, Baku, and Georgia transit dependencies."
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/markdown"
      ]
    },
    {
      "id": "central-asia-policy-watch",
      "name": "Central Asia policy signal watch",
      "description": "Identifies watch-next indicators for Central Asia policy, customs, export-control, energy, and transport developments without claiming live source retrieval.",
      "tags": [
        "central-asia",
        "policy-risk",
        "customs",
        "export-controls",
        "energy",
        "watch-next"
      ],
      "examples": [
        "List watch-next indicators for Kazakhstan export-control enforcement over the next quarter.",
        "Frame a policy-risk monitoring plan for Central Asia corridor operations."
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/markdown"
      ]
    },
    {
      "id": "corridor-source-coverage",
      "name": "Corridor source coverage checklist",
      "description": "Returns source-planning guidance for Kazakhstan and Central Asia risk memos: primary official sources, sanctions lists, customs/logistics data, independent context, and dated retrieval notes.",
      "tags": [
        "source-planning",
        "evidence-coverage",
        "official-sources",
        "logistics",
        "sanctions",
        "kazakhstan"
      ],
      "examples": [
        "Check whether this Kazakhstan sanctions evidence pack has enough primary-source coverage.",
        "What source categories are missing for a Middle Corridor policy-risk memo?"
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/markdown"
      ]
    },
    {
      "id": "kazakhstan-memo-quality-gate",
      "name": "Kazakhstan risk memo quality gate",
      "description": "Routes callers to Agenda Intelligence MCP quality gates for structured memo validation, evidence audit, unsupported-claim detection, and source-coverage diagnostics.",
      "tags": [
        "memo-validation",
        "evidence-audit",
        "quality-gate",
        "provenance",
        "kazakhstan",
        "strategic-risk"
      ],
      "examples": [
        "Audit this Kazakhstan corridor-risk memo for unsupported claims and missing source categories.",
        "Validate this sanctions-risk memo before analyst handoff."
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/markdown"
      ]
    }
  ],
  "x_agenda_intelligence": {
    "hosted_wrapper": true,
    "wrapper_scope": "A2A/JSON-RPC discovery, Kazakhstan and Central Asia corridor-risk triage, and routing response only",
    "jsonrpc_endpoint": "https://kazakhstan-corridor-risk-a2a.vassiliy-lakhonin.workers.dev/message/send",
    "repository": "https://github.com/vassiliylakhonin/agenda-intelligence-md",
    "package": "https://pypi.org/project/agenda-intelligence-md/",
    "mcp": {
      "transport": "stdio",
      "server_command": "agenda-intelligence-mcp",
      "install": "pip install agenda-intelligence-md"
    },
    "boundaries": [
      "No payments or wallet rails.",
      "No autonomous live source retrieval.",
      "No factual-truth verification.",
      "No legal, financial, compliance, investment, or trading advice."
    ],
    "product_profile": "kazakhstan_corridor_risk",
    "focus": [
      "Kazakhstan sanctions exposure",
      "Middle Corridor and Trans-Caspian logistics risk",
      "Central Asia policy and customs signals",
      "source coverage and evidence gaps",
      "risk memo quality gates"
    ]
  }
}