agenticdome-python-sdk 1.2.16__tar.gz → 1.2.18__tar.gz

{agenticdome_python_sdk-1.2.16 → agenticdome_python_sdk-1.2.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agenticdome-python-sdk
-Version: 1.2.16
+Version: 1.2.18
 Summary: Official Python SDK for AgenticDome security guardrails, DLP, tool authorization, and multi-agent delegation enforcement.
 Author: AgenticDome
 License-Expression: Apache-2.0
@@ -32,20 +32,20 @@ License-File: NOTICE
 Requires-Dist: requests>=2.31.0
 Requires-Dist: urllib3>=2.0.0
 Provides-Extra: crewai
-Requires-Dist: crewai<=1.15.15,>=1.15.5; extra == "crewai"
+Requires-Dist: crewai<=1.15.16,>=1.15.5; extra == "crewai"
 Provides-Extra: redis
 Requires-Dist: redis>=4.5.0; extra == "redis"
 Provides-Extra: pop
 Requires-Dist: cryptography>=42.0.0; extra == "pop"
 Provides-Extra: pydanticai
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "pydanticai"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "pydanticai"
 Requires-Dist: anyio>=4.0.0; extra == "pydanticai"
 Provides-Extra: pydantic
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "pydantic"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "pydantic"
 Requires-Dist: anyio>=4.0.0; extra == "pydantic"
 Provides-Extra: langgraph
 Requires-Dist: langgraph<=1.2.11,>=1.2.9; extra == "langgraph"
-Requires-Dist: langchain-core<=1.5.4,>=1.5.0; extra == "langgraph"
+Requires-Dist: langchain-core<=1.5.5,>=1.5.0; extra == "langgraph"
 Requires-Dist: langchain-openai==1.3.5; extra == "langgraph"
 Requires-Dist: anyio>=4.0.0; extra == "langgraph"
 Provides-Extra: microsoft
@@ -57,48 +57,48 @@ Provides-Extra: foundry
 Requires-Dist: azure-ai-projects<=2.4.0,>=2.3.0; extra == "foundry"
 Requires-Dist: azure-identity==1.25.3; extra == "foundry"
 Provides-Extra: agno
-Requires-Dist: agno<=2.8.7,>=2.8.0; extra == "agno"
+Requires-Dist: agno<=2.9.0,>=2.8.0; extra == "agno"
 Provides-Extra: openai-agents
-Requires-Dist: openai-agents<=0.20.0,>=0.18.3; extra == "openai-agents"
+Requires-Dist: openai-agents<=0.21.0,>=0.18.3; extra == "openai-agents"
 Provides-Extra: mcp
 Requires-Dist: mcp<=1.28.1,>=1.26.0; extra == "mcp"
 Provides-Extra: bedrock
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "bedrock"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "bedrock"
 Provides-Extra: aws-bedrock
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "aws-bedrock"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "aws-bedrock"
 Provides-Extra: llamaindex
 Requires-Dist: llama-index==0.14.23; extra == "llamaindex"
 Provides-Extra: llama-index
 Requires-Dist: llama-index==0.14.23; extra == "llama-index"
 Provides-Extra: google-adk
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "google-adk"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "google-adk"
 Provides-Extra: adk
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "adk"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "adk"
 Provides-Extra: claude
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "claude"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "claude"
 Provides-Extra: claude-agent-sdk
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "claude-agent-sdk"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "claude-agent-sdk"
 Provides-Extra: smolagents
 Requires-Dist: smolagents==1.26.0; extra == "smolagents"
 Provides-Extra: all
-Requires-Dist: crewai<=1.15.15,>=1.15.5; extra == "all"
+Requires-Dist: crewai<=1.15.16,>=1.15.5; extra == "all"
 Requires-Dist: redis>=4.5.0; extra == "all"
 Requires-Dist: cryptography>=42.0.0; extra == "all"
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "all"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "all"
 Requires-Dist: anyio>=4.0.0; extra == "all"
 Requires-Dist: langgraph<=1.2.11,>=1.2.9; extra == "all"
-Requires-Dist: langchain-core<=1.5.4,>=1.5.0; extra == "all"
+Requires-Dist: langchain-core<=1.5.5,>=1.5.0; extra == "all"
 Requires-Dist: langchain-openai==1.3.5; extra == "all"
 Requires-Dist: autogen-agentchat==0.7.5; extra == "all"
-Requires-Dist: agno<=2.8.7,>=2.8.0; extra == "all"
+Requires-Dist: agno<=2.9.0,>=2.8.0; extra == "all"
 Requires-Dist: azure-ai-projects<=2.4.0,>=2.3.0; extra == "all"
 Requires-Dist: azure-identity==1.25.3; extra == "all"
-Requires-Dist: openai-agents<=0.20.0,>=0.18.3; extra == "all"
+Requires-Dist: openai-agents<=0.21.0,>=0.18.3; extra == "all"
 Requires-Dist: mcp<=1.28.1,>=1.26.0; extra == "all"
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "all"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "all"
 Requires-Dist: llama-index==0.14.23; extra == "all"
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "all"
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "all"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "all"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "all"
 Requires-Dist: smolagents==1.26.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0.0; extra == "dev"
@@ -117,7 +117,7 @@ Dynamic: license-file
 [![CI](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml)
 [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
 
-[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
+[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Customer onboarding guide](docs/customer-onboarding.md) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
 
 > **Production-grade security guardrails, DLP, tool authorization, and cryptographically verified multi-agent delegation for Python autonomous AI runtimes.**
 
@@ -147,7 +147,14 @@ No account, API key, tenant, network connection, or third-party framework packag
 agenticdome-demo --framework langgraph --scenario both
 ```
 
-Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`. These are simulations: the example does not execute either tool.
+Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`.
+
+> **Offline demonstration—not runtime evidence.** This command evaluates two
+> fixed onboarding scenarios with a deterministic, bundled public baseline. It
+> does not contact AgenticDome, load tenant policy, execute either tool, or
+> instantiate a LangGraph graph. `--framework langgraph` labels the example
+> payload and points you to the matching integration; it is not a LangGraph
+> integration test.
 
 ### 4. Select your framework
 
@@ -158,6 +165,35 @@ agenticdome-demo --framework all --scenario both
 
 You can also open the [framework example gallery](examples/README.md) and run the individual example matching your stack. Before editing production code, choose the dedicated [framework integration guide](docs/frameworks/README.md), then use the [production integration playbook](examples/PRODUCTION_INTEGRATION.md) for the cross-framework attachment and proof checklist. MCP host and gateway developers can follow the dedicated [MCP Action Firewall guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md).
 
+If this is an application you intend to connect, start the local Integration
+Assistant from its repository root. It discovers likely protection points and
+keeps source code on your machine:
+
+```bash
+agenticdome init
+agenticdome verify --run-tests --output .agenticdome/verification.json
+```
+
+`init` writes the secret-free inspection and local configuration. `verify` is
+required before production because it rechecks the discovered boundaries,
+runs harmless allowed/blocked cases and, with `--run-tests`, runs detected
+application tests. If you want a suggested patch, run `agenticdome scaffold`;
+that step is optional and writes an unapplied patch for review.
+
+When `.agenticdome/inspection.json` is imported into Developer Integration,
+the Control Panel adds its detected frameworks to the workload. Frameworks,
+languages and candidate boundaries can be discovered locally; business
+purpose, sensitive actions and managed-versus-sovereign deployment remain
+explicit customer decisions and are not guessed from source code.
+
+Use **Customer Control Panel → Activate Action Firewall → Core Config** to
+choose the Developer Integration path and import the two evidence files. This
+path is for SDK, MCP, framework or custom-code integrations; Microsoft
+Discovery Scan and Copilot Studio external protection are separate optional
+paths selected from Core Config. See the
+[customer onboarding guide](docs/customer-onboarding.md) for the complete
+required-versus-optional workflow.
+
 ### 5. Connect the same integration to AgenticDome
 
 When you are ready to test real tenant policy, remove `AGENTICDOME_MODE=local_sim`, obtain the assigned runtime sidecar URL, Runtime/SDK API key and tenant ID from AgenticDome, and configure:
@@ -170,7 +206,13 @@ export AGENTICDOME_TENANT_ID="your_tenant_id"
 agenticdome-demo --framework langgraph --scenario both --live
 ```
 
-Offline simulation demonstrates the SDK decision flow using a bundled public baseline. Only live mode applies the customer's policy, topology, telemetry, signed decisions and runtime enforcement.
+With `--live`, the same fixed scenarios are sent to the actual assigned
+AgenticDome runtime sidecar, so their verdicts come from the customer's tenant
+policy and engine. The live demo still does not instantiate LangGraph or prove
+that an application has attached the framework adapter at every execution
+boundary. Use the framework guide to attach the adapter, test the real
+application path, and use AgenticDome Runtime Assurance for production
+evidence.
 
 ```python
 # The 30-second version: block a prompt-injected refund before it executes.
@@ -205,6 +247,21 @@ result = crew.kickoff()          # hostile prompts, unsafe tools, and rogue
 
 An agent can be hijacked while holding valid tokens, approved tools, and fully authorized paths. Legacy security sees a compliant request; the business sees a breach. AgenticDome adds an intent-aware enforcement layer at the exact boundaries where agents act:
 
+### Identity is necessary, but it is not the action decision
+
+Give every agent and workload a distinct principal and keep your identity
+provider authoritative for authentication, scopes, conditional access,
+credential lifecycle, and downstream entitlements. Then pass the identity the
+application has actually authenticated into AgenticDome alongside the agent,
+purpose, tool, final arguments, session, and delegation context. A valid token
+proves access authority; it does not prove that a prompt-influenced action is
+appropriate. AgenticDome complements IAM by evaluating that action at the
+application-controlled execution boundary. It does not issue enterprise
+identities or make a stolen credential safe.
+
+For the architectural rationale, see
+[An agent principal proves who—not why](https://www.agenticdome.io/research/agent-principal-identity).
+
 | Control | What it stops | Where it runs |
 | :--- | :--- | :--- |
 | **Prompt ingress guardrails** | Prompt injection, jailbreaks, system-prompt extraction, instruction override, policy bypass | Before agent/LLM execution |
@@ -300,15 +357,23 @@ Start with a network-free simulation, then connect the same SDK to your assigned
 
 ```bash
 pip install agenticdome-python-sdk
-# Show one ALLOWED and one BLOCKED action for LangGraph.
+# Label the fixed demonstration as LangGraph and show one ALLOWED and one BLOCKED path.
 agenticdome-demo --framework langgraph --scenario both
 
-# Or prove the same offline contract across all 15 integrations.
+# Or repeat the fixed demonstration under every supported framework label.
 agenticdome-demo --framework all --scenario both
 agenticdome-demo --list-frameworks
 ```
 
-This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It evaluates a small bundled demonstration policy through the real public client contract, but it does not load tenant policy, issue signed decision tokens or execution receipts, write cloud evidence, or provide runtime assurance. To exercise any wrapper inside your own process without credentials, set `AGENTICDOME_MODE=local_sim`. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
+This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It
+evaluates two fixed inputs with a small deterministic bundled baseline through
+the public core-client response shape. The `--framework` option changes the
+payload label and integration guidance; it does not import, instantiate, or run
+the selected framework. The simulation does not load tenant policy, issue
+signed decision tokens or execution receipts, write cloud evidence, or provide
+runtime assurance. To exercise a real adapter inside your own process without
+credentials, set `AGENTICDOME_MODE=local_sim` in that application or framework
+example. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
 
 Browse the public [`examples/`](examples/README.md) gallery for a runnable allowed/blocked example for CrewAI, PydanticAI, LangGraph, Microsoft Agent Framework, AutoGen, AI Foundry, OpenAI Agents, Claude, smolagents, Agno, Google ADK, LlamaIndex, Bedrock, MCP, and custom Python. Local blocked/redacted results emit safe terminal logs containing verdict metadata only—not raw prompts, arguments, keys, or secrets.
 

{agenticdome_python_sdk-1.2.16 → agenticdome_python_sdk-1.2.18}/README.md

@@ -5,7 +5,7 @@
 [![CI](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml)
 [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
 
-[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
+[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Customer onboarding guide](docs/customer-onboarding.md) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
 
 > **Production-grade security guardrails, DLP, tool authorization, and cryptographically verified multi-agent delegation for Python autonomous AI runtimes.**
 
@@ -35,7 +35,14 @@ No account, API key, tenant, network connection, or third-party framework packag
 agenticdome-demo --framework langgraph --scenario both
 ```
 
-Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`. These are simulations: the example does not execute either tool.
+Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`.
+
+> **Offline demonstration—not runtime evidence.** This command evaluates two
+> fixed onboarding scenarios with a deterministic, bundled public baseline. It
+> does not contact AgenticDome, load tenant policy, execute either tool, or
+> instantiate a LangGraph graph. `--framework langgraph` labels the example
+> payload and points you to the matching integration; it is not a LangGraph
+> integration test.
 
 ### 4. Select your framework
 
@@ -46,6 +53,35 @@ agenticdome-demo --framework all --scenario both
 
 You can also open the [framework example gallery](examples/README.md) and run the individual example matching your stack. Before editing production code, choose the dedicated [framework integration guide](docs/frameworks/README.md), then use the [production integration playbook](examples/PRODUCTION_INTEGRATION.md) for the cross-framework attachment and proof checklist. MCP host and gateway developers can follow the dedicated [MCP Action Firewall guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md).
 
+If this is an application you intend to connect, start the local Integration
+Assistant from its repository root. It discovers likely protection points and
+keeps source code on your machine:
+
+```bash
+agenticdome init
+agenticdome verify --run-tests --output .agenticdome/verification.json
+```
+
+`init` writes the secret-free inspection and local configuration. `verify` is
+required before production because it rechecks the discovered boundaries,
+runs harmless allowed/blocked cases and, with `--run-tests`, runs detected
+application tests. If you want a suggested patch, run `agenticdome scaffold`;
+that step is optional and writes an unapplied patch for review.
+
+When `.agenticdome/inspection.json` is imported into Developer Integration,
+the Control Panel adds its detected frameworks to the workload. Frameworks,
+languages and candidate boundaries can be discovered locally; business
+purpose, sensitive actions and managed-versus-sovereign deployment remain
+explicit customer decisions and are not guessed from source code.
+
+Use **Customer Control Panel → Activate Action Firewall → Core Config** to
+choose the Developer Integration path and import the two evidence files. This
+path is for SDK, MCP, framework or custom-code integrations; Microsoft
+Discovery Scan and Copilot Studio external protection are separate optional
+paths selected from Core Config. See the
+[customer onboarding guide](docs/customer-onboarding.md) for the complete
+required-versus-optional workflow.
+
 ### 5. Connect the same integration to AgenticDome
 
 When you are ready to test real tenant policy, remove `AGENTICDOME_MODE=local_sim`, obtain the assigned runtime sidecar URL, Runtime/SDK API key and tenant ID from AgenticDome, and configure:
@@ -58,7 +94,13 @@ export AGENTICDOME_TENANT_ID="your_tenant_id"
 agenticdome-demo --framework langgraph --scenario both --live
 ```
 
-Offline simulation demonstrates the SDK decision flow using a bundled public baseline. Only live mode applies the customer's policy, topology, telemetry, signed decisions and runtime enforcement.
+With `--live`, the same fixed scenarios are sent to the actual assigned
+AgenticDome runtime sidecar, so their verdicts come from the customer's tenant
+policy and engine. The live demo still does not instantiate LangGraph or prove
+that an application has attached the framework adapter at every execution
+boundary. Use the framework guide to attach the adapter, test the real
+application path, and use AgenticDome Runtime Assurance for production
+evidence.
 
 ```python
 # The 30-second version: block a prompt-injected refund before it executes.
@@ -93,6 +135,21 @@ result = crew.kickoff()          # hostile prompts, unsafe tools, and rogue
 
 An agent can be hijacked while holding valid tokens, approved tools, and fully authorized paths. Legacy security sees a compliant request; the business sees a breach. AgenticDome adds an intent-aware enforcement layer at the exact boundaries where agents act:
 
+### Identity is necessary, but it is not the action decision
+
+Give every agent and workload a distinct principal and keep your identity
+provider authoritative for authentication, scopes, conditional access,
+credential lifecycle, and downstream entitlements. Then pass the identity the
+application has actually authenticated into AgenticDome alongside the agent,
+purpose, tool, final arguments, session, and delegation context. A valid token
+proves access authority; it does not prove that a prompt-influenced action is
+appropriate. AgenticDome complements IAM by evaluating that action at the
+application-controlled execution boundary. It does not issue enterprise
+identities or make a stolen credential safe.
+
+For the architectural rationale, see
+[An agent principal proves who—not why](https://www.agenticdome.io/research/agent-principal-identity).
+
 | Control | What it stops | Where it runs |
 | :--- | :--- | :--- |
 | **Prompt ingress guardrails** | Prompt injection, jailbreaks, system-prompt extraction, instruction override, policy bypass | Before agent/LLM execution |
@@ -188,15 +245,23 @@ Start with a network-free simulation, then connect the same SDK to your assigned
 
 ```bash
 pip install agenticdome-python-sdk
-# Show one ALLOWED and one BLOCKED action for LangGraph.
+# Label the fixed demonstration as LangGraph and show one ALLOWED and one BLOCKED path.
 agenticdome-demo --framework langgraph --scenario both
 
-# Or prove the same offline contract across all 15 integrations.
+# Or repeat the fixed demonstration under every supported framework label.
 agenticdome-demo --framework all --scenario both
 agenticdome-demo --list-frameworks
 ```
 
-This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It evaluates a small bundled demonstration policy through the real public client contract, but it does not load tenant policy, issue signed decision tokens or execution receipts, write cloud evidence, or provide runtime assurance. To exercise any wrapper inside your own process without credentials, set `AGENTICDOME_MODE=local_sim`. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
+This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It
+evaluates two fixed inputs with a small deterministic bundled baseline through
+the public core-client response shape. The `--framework` option changes the
+payload label and integration guidance; it does not import, instantiate, or run
+the selected framework. The simulation does not load tenant policy, issue
+signed decision tokens or execution receipts, write cloud evidence, or provide
+runtime assurance. To exercise a real adapter inside your own process without
+credentials, set `AGENTICDOME_MODE=local_sim` in that application or framework
+example. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
 
 Browse the public [`examples/`](examples/README.md) gallery for a runnable allowed/blocked example for CrewAI, PydanticAI, LangGraph, Microsoft Agent Framework, AutoGen, AI Foundry, OpenAI Agents, Claude, smolagents, Agno, Google ADK, LlamaIndex, Bedrock, MCP, and custom Python. Local blocked/redacted results emit safe terminal logs containing verdict metadata only—not raw prompts, arguments, keys, or secrets.
 

{agenticdome_python_sdk-1.2.16 → agenticdome_python_sdk-1.2.18}/agenticdome_python_sdk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agenticdome-python-sdk
-Version: 1.2.16
+Version: 1.2.18
 Summary: Official Python SDK for AgenticDome security guardrails, DLP, tool authorization, and multi-agent delegation enforcement.
 Author: AgenticDome
 License-Expression: Apache-2.0
@@ -32,20 +32,20 @@ License-File: NOTICE
 Requires-Dist: requests>=2.31.0
 Requires-Dist: urllib3>=2.0.0
 Provides-Extra: crewai
-Requires-Dist: crewai<=1.15.15,>=1.15.5; extra == "crewai"
+Requires-Dist: crewai<=1.15.16,>=1.15.5; extra == "crewai"
 Provides-Extra: redis
 Requires-Dist: redis>=4.5.0; extra == "redis"
 Provides-Extra: pop
 Requires-Dist: cryptography>=42.0.0; extra == "pop"
 Provides-Extra: pydanticai
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "pydanticai"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "pydanticai"
 Requires-Dist: anyio>=4.0.0; extra == "pydanticai"
 Provides-Extra: pydantic
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "pydantic"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "pydantic"
 Requires-Dist: anyio>=4.0.0; extra == "pydantic"
 Provides-Extra: langgraph
 Requires-Dist: langgraph<=1.2.11,>=1.2.9; extra == "langgraph"
-Requires-Dist: langchain-core<=1.5.4,>=1.5.0; extra == "langgraph"
+Requires-Dist: langchain-core<=1.5.5,>=1.5.0; extra == "langgraph"
 Requires-Dist: langchain-openai==1.3.5; extra == "langgraph"
 Requires-Dist: anyio>=4.0.0; extra == "langgraph"
 Provides-Extra: microsoft
@@ -57,48 +57,48 @@ Provides-Extra: foundry
 Requires-Dist: azure-ai-projects<=2.4.0,>=2.3.0; extra == "foundry"
 Requires-Dist: azure-identity==1.25.3; extra == "foundry"
 Provides-Extra: agno
-Requires-Dist: agno<=2.8.7,>=2.8.0; extra == "agno"
+Requires-Dist: agno<=2.9.0,>=2.8.0; extra == "agno"
 Provides-Extra: openai-agents
-Requires-Dist: openai-agents<=0.20.0,>=0.18.3; extra == "openai-agents"
+Requires-Dist: openai-agents<=0.21.0,>=0.18.3; extra == "openai-agents"
 Provides-Extra: mcp
 Requires-Dist: mcp<=1.28.1,>=1.26.0; extra == "mcp"
 Provides-Extra: bedrock
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "bedrock"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "bedrock"
 Provides-Extra: aws-bedrock
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "aws-bedrock"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "aws-bedrock"
 Provides-Extra: llamaindex
 Requires-Dist: llama-index==0.14.23; extra == "llamaindex"
 Provides-Extra: llama-index
 Requires-Dist: llama-index==0.14.23; extra == "llama-index"
 Provides-Extra: google-adk
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "google-adk"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "google-adk"
 Provides-Extra: adk
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "adk"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "adk"
 Provides-Extra: claude
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "claude"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "claude"
 Provides-Extra: claude-agent-sdk
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "claude-agent-sdk"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "claude-agent-sdk"
 Provides-Extra: smolagents
 Requires-Dist: smolagents==1.26.0; extra == "smolagents"
 Provides-Extra: all
-Requires-Dist: crewai<=1.15.15,>=1.15.5; extra == "all"
+Requires-Dist: crewai<=1.15.16,>=1.15.5; extra == "all"
 Requires-Dist: redis>=4.5.0; extra == "all"
 Requires-Dist: cryptography>=42.0.0; extra == "all"
-Requires-Dist: pydantic-ai<=2.28.0,>=2.16.0; extra == "all"
+Requires-Dist: pydantic-ai<=2.31.0,>=2.16.0; extra == "all"
 Requires-Dist: anyio>=4.0.0; extra == "all"
 Requires-Dist: langgraph<=1.2.11,>=1.2.9; extra == "all"
-Requires-Dist: langchain-core<=1.5.4,>=1.5.0; extra == "all"
+Requires-Dist: langchain-core<=1.5.5,>=1.5.0; extra == "all"
 Requires-Dist: langchain-openai==1.3.5; extra == "all"
 Requires-Dist: autogen-agentchat==0.7.5; extra == "all"
-Requires-Dist: agno<=2.8.7,>=2.8.0; extra == "all"
+Requires-Dist: agno<=2.9.0,>=2.8.0; extra == "all"
 Requires-Dist: azure-ai-projects<=2.4.0,>=2.3.0; extra == "all"
 Requires-Dist: azure-identity==1.25.3; extra == "all"
-Requires-Dist: openai-agents<=0.20.0,>=0.18.3; extra == "all"
+Requires-Dist: openai-agents<=0.21.0,>=0.18.3; extra == "all"
 Requires-Dist: mcp<=1.28.1,>=1.26.0; extra == "all"
-Requires-Dist: boto3<=1.43.69,>=1.43.54; extra == "all"
+Requires-Dist: boto3<=1.43.72,>=1.43.54; extra == "all"
 Requires-Dist: llama-index==0.14.23; extra == "all"
-Requires-Dist: google-adk<=2.6.3,>=2.5.0; extra == "all"
-Requires-Dist: claude-agent-sdk<=0.2.136,>=0.2.126; extra == "all"
+Requires-Dist: google-adk<=2.7.0,>=2.5.0; extra == "all"
+Requires-Dist: claude-agent-sdk<=0.2.139,>=0.2.126; extra == "all"
 Requires-Dist: smolagents==1.26.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0.0; extra == "dev"
@@ -117,7 +117,7 @@ Dynamic: license-file
 [![CI](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/agenticdome/agenticdome-python-sdk/actions/workflows/ci.yml)
 [![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
 
-[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
+[Source and examples](https://github.com/agenticdome/agenticdome-python-sdk) · [Customer onboarding guide](docs/customer-onboarding.md) · [Framework integration guides](https://github.com/agenticdome/agenticdome-python-sdk/tree/main/docs/frameworks) · [MCP integration guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md) · [Issue tracker](https://github.com/agenticdome/agenticdome-python-sdk/issues) · [Security policy](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/SECURITY.md) · [PyPI package](https://pypi.org/project/agenticdome-python-sdk/)
 
 > **Production-grade security guardrails, DLP, tool authorization, and cryptographically verified multi-agent delegation for Python autonomous AI runtimes.**
 
@@ -147,7 +147,14 @@ No account, API key, tenant, network connection, or third-party framework packag
 agenticdome-demo --framework langgraph --scenario both
 ```
 
-Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`. These are simulations: the example does not execute either tool.
+Look for `ALLOWED — TOOL WOULD EXECUTE` followed by `BLOCKED — TOOL WOULD NOT EXECUTE`.
+
+> **Offline demonstration—not runtime evidence.** This command evaluates two
+> fixed onboarding scenarios with a deterministic, bundled public baseline. It
+> does not contact AgenticDome, load tenant policy, execute either tool, or
+> instantiate a LangGraph graph. `--framework langgraph` labels the example
+> payload and points you to the matching integration; it is not a LangGraph
+> integration test.
 
 ### 4. Select your framework
 
@@ -158,6 +165,35 @@ agenticdome-demo --framework all --scenario both
 
 You can also open the [framework example gallery](examples/README.md) and run the individual example matching your stack. Before editing production code, choose the dedicated [framework integration guide](docs/frameworks/README.md), then use the [production integration playbook](examples/PRODUCTION_INTEGRATION.md) for the cross-framework attachment and proof checklist. MCP host and gateway developers can follow the dedicated [MCP Action Firewall guide](https://github.com/agenticdome/agenticdome-python-sdk/blob/main/docs/mcp-integration.md).
 
+If this is an application you intend to connect, start the local Integration
+Assistant from its repository root. It discovers likely protection points and
+keeps source code on your machine:
+
+```bash
+agenticdome init
+agenticdome verify --run-tests --output .agenticdome/verification.json
+```
+
+`init` writes the secret-free inspection and local configuration. `verify` is
+required before production because it rechecks the discovered boundaries,
+runs harmless allowed/blocked cases and, with `--run-tests`, runs detected
+application tests. If you want a suggested patch, run `agenticdome scaffold`;
+that step is optional and writes an unapplied patch for review.
+
+When `.agenticdome/inspection.json` is imported into Developer Integration,
+the Control Panel adds its detected frameworks to the workload. Frameworks,
+languages and candidate boundaries can be discovered locally; business
+purpose, sensitive actions and managed-versus-sovereign deployment remain
+explicit customer decisions and are not guessed from source code.
+
+Use **Customer Control Panel → Activate Action Firewall → Core Config** to
+choose the Developer Integration path and import the two evidence files. This
+path is for SDK, MCP, framework or custom-code integrations; Microsoft
+Discovery Scan and Copilot Studio external protection are separate optional
+paths selected from Core Config. See the
+[customer onboarding guide](docs/customer-onboarding.md) for the complete
+required-versus-optional workflow.
+
 ### 5. Connect the same integration to AgenticDome
 
 When you are ready to test real tenant policy, remove `AGENTICDOME_MODE=local_sim`, obtain the assigned runtime sidecar URL, Runtime/SDK API key and tenant ID from AgenticDome, and configure:
@@ -170,7 +206,13 @@ export AGENTICDOME_TENANT_ID="your_tenant_id"
 agenticdome-demo --framework langgraph --scenario both --live
 ```
 
-Offline simulation demonstrates the SDK decision flow using a bundled public baseline. Only live mode applies the customer's policy, topology, telemetry, signed decisions and runtime enforcement.
+With `--live`, the same fixed scenarios are sent to the actual assigned
+AgenticDome runtime sidecar, so their verdicts come from the customer's tenant
+policy and engine. The live demo still does not instantiate LangGraph or prove
+that an application has attached the framework adapter at every execution
+boundary. Use the framework guide to attach the adapter, test the real
+application path, and use AgenticDome Runtime Assurance for production
+evidence.
 
 ```python
 # The 30-second version: block a prompt-injected refund before it executes.
@@ -205,6 +247,21 @@ result = crew.kickoff()          # hostile prompts, unsafe tools, and rogue
 
 An agent can be hijacked while holding valid tokens, approved tools, and fully authorized paths. Legacy security sees a compliant request; the business sees a breach. AgenticDome adds an intent-aware enforcement layer at the exact boundaries where agents act:
 
+### Identity is necessary, but it is not the action decision
+
+Give every agent and workload a distinct principal and keep your identity
+provider authoritative for authentication, scopes, conditional access,
+credential lifecycle, and downstream entitlements. Then pass the identity the
+application has actually authenticated into AgenticDome alongside the agent,
+purpose, tool, final arguments, session, and delegation context. A valid token
+proves access authority; it does not prove that a prompt-influenced action is
+appropriate. AgenticDome complements IAM by evaluating that action at the
+application-controlled execution boundary. It does not issue enterprise
+identities or make a stolen credential safe.
+
+For the architectural rationale, see
+[An agent principal proves who—not why](https://www.agenticdome.io/research/agent-principal-identity).
+
 | Control | What it stops | Where it runs |
 | :--- | :--- | :--- |
 | **Prompt ingress guardrails** | Prompt injection, jailbreaks, system-prompt extraction, instruction override, policy bypass | Before agent/LLM execution |
@@ -300,15 +357,23 @@ Start with a network-free simulation, then connect the same SDK to your assigned
 
 ```bash
 pip install agenticdome-python-sdk
-# Show one ALLOWED and one BLOCKED action for LangGraph.
+# Label the fixed demonstration as LangGraph and show one ALLOWED and one BLOCKED path.
 agenticdome-demo --framework langgraph --scenario both
 
-# Or prove the same offline contract across all 15 integrations.
+# Or repeat the fixed demonstration under every supported framework label.
 agenticdome-demo --framework all --scenario both
 agenticdome-demo --list-frameworks
 ```
 
-This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It evaluates a small bundled demonstration policy through the real public client contract, but it does not load tenant policy, issue signed decision tokens or execution receipts, write cloud evidence, or provide runtime assurance. To exercise any wrapper inside your own process without credentials, set `AGENTICDOME_MODE=local_sim`. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
+This is visibly labelled **LOCAL SIMULATION — NOT CLOUD ENFORCEMENT**. It
+evaluates two fixed inputs with a small deterministic bundled baseline through
+the public core-client response shape. The `--framework` option changes the
+payload label and integration guidance; it does not import, instantiate, or run
+the selected framework. The simulation does not load tenant policy, issue
+signed decision tokens or execution receipts, write cloud evidence, or provide
+runtime assurance. To exercise a real adapter inside your own process without
+credentials, set `AGENTICDOME_MODE=local_sim` in that application or framework
+example. The SDK refuses that mode when `AGENTICDOME_PRODUCTION_MODE=true`.
 
 Browse the public [`examples/`](examples/README.md) gallery for a runnable allowed/blocked example for CrewAI, PydanticAI, LangGraph, Microsoft Agent Framework, AutoGen, AI Foundry, OpenAI Agents, Claude, smolagents, Agno, Google ADK, LlamaIndex, Bedrock, MCP, and custom Python. Local blocked/redacted results emit safe terminal logs containing verdict metadata only—not raw prompts, arguments, keys, or secrets.
 

{agenticdome_python_sdk-1.2.16 → agenticdome_python_sdk-1.2.18}/agenticdome_python_sdk.egg-info/SOURCES.txt

@@ -29,11 +29,13 @@ agenticdome_sdk/llamaindex.py
 agenticdome_sdk/mcp_host.py
 agenticdome_sdk/microsoft_agent_framework.py
 agenticdome_sdk/microsoft_ai_foundry.py
+agenticdome_sdk/onboarding_cli.py
 agenticdome_sdk/openai_agents.py
 agenticdome_sdk/proof.py
 agenticdome_sdk/pydantic.py
 agenticdome_sdk/simulation.py
 agenticdome_sdk/smolagents.py
+docs/customer-onboarding.md
 docs/mcp-integration.md
 docs/performance-evidence.md
 docs/runtime-deployment.md
@@ -94,6 +96,7 @@ tests/test_mcp_host_integration.py
 tests/test_mcp_launch_example.py
 tests/test_microsoft_agent_framework_integration.py
 tests/test_microsoft_ai_foundry_integration.py
+tests/test_onboarding_cli.py
 tests/test_openai_agents_integration.py
 tests/test_pydanticai_integration.py
 tests/test_smolagents_integration.py

{agenticdome_python_sdk-1.2.16 → agenticdome_python_sdk-1.2.18}/agenticdome_python_sdk.egg-info/entry_points.txt

@@ -1,2 +1,3 @@
 [console_scripts]
+agenticdome = agenticdome_sdk.onboarding_cli:main
 agenticdome-demo = agenticdome_sdk.demo:main