ASCEND AI SDK
Official Python SDK for Ascend AI Governance Platform — enterprise AI governance and enforcement for regulated industries.
Govern what your AI agents do — in real time. ASCEND intercepts every agent action, scores risk using CVSS v3.1/NIST 800-30/MITRE ATT&CK, enforces your policies, and maintains an immutable audit trail for compliance.
Built for financial services, healthcare, and government contractors.
Install
pip install ascend-ai-sdk
Quick Start
from ascend import AscendClient, FailMode
client = AscendClient(
api_key="your_api_key",
api_url="https://pilot.owkai.app",
agent_id="my-agent",
agent_name="My Agent",
fail_mode=FailMode.CLOSED
)
# Govern an action before it executes
result = client.evaluate_action(
action_type="database_write",
resource="customer_db",
wait_for_decision=False
)
print(result.decision) # APPROVED / PENDING / DENIED
print(result.risk_score) # 0-100
print(result.cvss_score) # CVSS v3.1 base score
print(result.mitre_tactic) # MITRE ATT&CK tactic
Enforcement Decision Attribution
Inspect why the platform reached its verdict. These fields ship in
AuthorizationDecision as of SDK 2.7.0:
# Authoritative governance verdict
print(result.enforcement_decision)
# 'auto_approved' | 'pending_approval' | 'denied' | 'escalated'
# Which signal drove the verdict
print(result.enforcement_decision_source)
# 'threshold' | 'policy' | 'smart_rule' |
# 'code_analysis' | 'prompt_security'
# Which signal contributed the highest risk score
print(result.risk_score_source)
# 'cvss' | 'policy' | 'code_analysis' |
# 'prompt_security' | 'pipeline'
# Shadow scoring — what the system WOULD have decided under
# the org's shadow threshold config. None when no shadow
# config exists (opt-in feature, observational only).
print(result.shadow_enforcement_decision)
print(result.shadow_enforcement_decision_source)
Model Governance (SR-11-7 / EU AI Act Art. 9)
Enforce your model registry at action submit time. Non-compliant or unregistered models are denied.
result = client.evaluate_action(
action_type="model_inference",
resource="ml_pipeline",
model_id="gpt-4-production", # checked against registry
wait_for_decision=False
)
print(result.model_governance["registry_checked"])
print(result.model_governance["compliance_status"])
MCP Layer 13 Governance
Govern actions from MCP servers. Unregistered or deactivated servers are denied.
result = client.evaluate_action(
action_type="tool_call",
resource="crm_system",
mcp_server_name="salesforce-mcp",
wait_for_decision=False
)
print(result.mcp_governance["server_registered"])
Kill-Switch
Block all agent actions within one poll cycle (default 5 seconds). Kill-switch server handler p99=17.03ms (measured June 2, 2026).
# Agent side — poll for kill-switch signals
client.start_kill_switch_polling(
interval_seconds=5
)
# Fail-secure: agents fail-closed after 3 consecutive unreachable
# polls (~15 seconds worst-case). Recovers automatically when the
# endpoint becomes healthy.
if client.is_blocked():
# Kill-switch active OR polling has failed 3+ times —
# do not proceed with the agent action.
pass
Capabilities
| Capability | Description |
|---|---|
| Risk Scoring | CVSS v3.1, NIST 800-30, MITRE ATT&CK composite |
| MCP Governance | Layer 13 enforcement — unregistered servers denied |
| Model Governance | Registry-backed compliance check — SR-11-7, EU AI Act |
| Kill-Switch | Poll-based agent blocking, default 5s interval. Server handler p99=17.03ms measured |
| Prompt Injection | 22 detection patterns including encoding detection |
| Code Analysis | SQL injection, command injection, credential detection |
| Supply Chain | CVE detection via NVD/OSV, risk scoring |
| Audit Trail | Immutable hash-chain, cryptographic verification |
| Human Approval | Multi-stage workflows with SLA enforcement |
Compliance
SOC 2 Type II · PCI-DSS · HIPAA · FedRAMP Compatible NIST AI RMF · SR 11-7 · EU AI Act Art. 9/28
Links
- Platform: https://pilot.owkai.app
- Documentation: https://docs.ascendowkai.com
- Status: https://ascend-status.instatus.com
- Support: info@ow-kai.com
Requirements
Python 3.8+
ASCEND is a product of OW-KAI Technologies, Inc. 9+ years spanning AI/ML governance and cybersecurity.
Metadata
Release files for ascend-ai-sdk 2.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ascend_ai_sdk-2.7.1.tar.gz | 93.3 kB | Without provenance | Details for ascend_ai_sdk-2.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ascend_ai_sdk-2.7.1-py3-none-any.whl | Python 3 | none | any | Details for ascend_ai_sdk-2.7.1-py3-none-any.whl |
Total release size: 161.9 kB
Release files / ascend_ai_sdk-2.7.1.tar.gz
| Download URL | ascend_ai_sdk-2.7.1.tar.gz |
|---|---|
| Size | 93.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b328a9d089dd563e67006c176761faa9745b30d59974181d73ce86b9ad90b7a2
|
|
BLAKE2b-256 checksum How to use checksums |
c186d43462ba58fd4e143215ca0381e2858b1ca7423af31dd650e3c1f8b900b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Release files / ascend_ai_sdk-2.7.1-py3-none-any.whl
| Download URL | ascend_ai_sdk-2.7.1-py3-none-any.whl |
|---|---|
| Size | 68.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c70f8c4839e36fd24b8fcf41653c759dd7adbcb4e83cfd628f8e3aed269c1e7
|
|
BLAKE2b-256 checksum How to use checksums |
14d9bd59854d78e789ffa66a359ab282f25e0b802532c5796099cf9572b99158
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.1
|
Security for ascend-ai-sdk 2.7.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.