Skip to main content

aisoc-sdk

License: MIT PyPI release

Async Python client SDK for AiSOC.

Status — monorepo today, not yet on PyPI. pip install aisoc-sdk does not resolve; install from the monorepo source path below. The import path (aisoc_sdk) and API surface stay identical once it ships.

Installation

# Today (from this monorepo):
git clone https://github.com/beenuar/AiSOC.git
cd AiSOC && pip install -e packages/sdk-py

# Not yet on PyPI — the upload is blocked on registry credentials,
# which is an account action rather than a code change. Until then, install
# from source with the command above.
#   pip install aisoc-sdk

Quick start

import asyncio
from aisoc_sdk import AiSOCClient


async def main():
    async with AiSOCClient(
        base_url="https://your-aisoc.example.com",
        token="aisoc_...",
    ) as client:
        # List critical open alerts
        alerts = await client.alerts.list(severity="critical", status="open")
        print(f"Found {alerts.total} critical alerts")

        # Create a case
        case = await client.cases.create(
            title="Suspicious lateral movement",
            priority="high",
        )

        # Trigger a playbook
        run = await client.playbooks.run(
            "isolate-host",
            trigger_data={"host_id": "srv-prod-42", "case_id": case.id},
        )
        print("Playbook run:", run.run_id)


asyncio.run(main())

GraphQL

async with AiSOCClient(base_url="...", token="...") as client:
    result = await client.graphql("""
        query {
            alerts(pageSize: 10, status: "open") {
                items { id title severity }
            }
        }
    """)

API reference

All resource methods are async and return typed Pydantic models.

Attribute Methods
client.alerts list(filters?), get(id), update(id, **data)
client.cases list(filters?), get(id), create(**data), update(id, **data), delete(id)
client.detections list(page, page_size), get(id)
client.connectors list(page, page_size), get(id)
client.playbooks list(page, page_size), get(id), create(**data), update(id, **data), delete(id), run(id, trigger_data?), get_run(run_id)
client.api_keys list(), create(req), revoke(id)

Development

pip install -e ".[dev]"
pytest

Metadata

Release files for aisoc-sdk 4.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aisoc-sdk 4.0.0
File Size Uploaded
aisoc_sdk-4.0.0.tar.gz 9.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aisoc-sdk 4.0.0
File Interpreter ABI Platform
aisoc_sdk-4.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 15.9 kB

Release files / aisoc_sdk-4.0.0.tar.gz

Download URL aisoc_sdk-4.0.0.tar.gz
Size 9.2 kB
Tags Source
SHA-256 checksum
How to use checksums
41bd61591e6f8116c5e7e47ea0d2eda8877b4108771fc744b00fd4067404b79f
BLAKE2b-256 checksum
How to use checksums
f100c7d43f6734d436e8244e3cd3007bdb3d0004f6c8a1b08cafbff02f0892d4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Release files / aisoc_sdk-4.0.0-py3-none-any.whl

Download URL aisoc_sdk-4.0.0-py3-none-any.whl
Size 6.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8e3b518c1ec81e23afbcdf87b94e5170e5a4349b52b78f5b917221659bf090f5
BLAKE2b-256 checksum
How to use checksums
3b2b0a39ae65f23d47f34cdccdb1c32678e34de80206a29abcd9bb9dc312b489
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

4.0.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page