Skip to main content

Victor SDK

Protocol and type definitions for building Victor verticals without pulling in the Victor runtime.

Overview

Use victor-sdk when you want to author or publish a vertical package. Use victor-ai when you want to run a vertical inside the Victor host runtime.

The supported external authoring model is contract-first:

  • vertical packages depend on victor-sdk only
  • verticals declare tools, capabilities, prompts, teams, and workflow metadata through the SDK contract
  • victor-ai remains responsible for runtime concerns such as agent creation, capability injection, and tool execution

Installation

SDK-only authoring

pip install victor-sdk

Runtime usage

pip install victor-ai

Stable SDK Surface

The core authoring surface is available from the top-level package:

from victor_sdk import (
    CURRENT_DEFINITION_VERSION,
    CapabilityIds,
    CapabilityRequirement,
    ToolNames,
    ToolRequirement,
    VerticalBase,
    VerticalDefinition,
)

Key pieces:

  • VerticalBase: SDK base class for external verticals
  • ToolNames: canonical SDK-owned tool identifiers
  • CapabilityIds: canonical SDK-owned runtime capability identifiers
  • ToolRequirement / CapabilityRequirement: typed requirement declarations
  • VerticalDefinition: validated serializable manifest returned by get_definition()

Quick Start

from victor_sdk import (
    CapabilityIds,
    CapabilityRequirement,
    ToolNames,
    ToolRequirement,
    VerticalBase,
)


class SecurityVertical(VerticalBase):
    name = "security"
    description = "Security analysis and audit workflows"
    version = "1.0.0"

    @classmethod
    def get_name(cls) -> str:
        return cls.name

    @classmethod
    def get_description(cls) -> str:
        return cls.description

    @classmethod
    def get_tool_requirements(cls) -> list[ToolRequirement]:
        return [
            ToolRequirement(ToolNames.READ, purpose="inspect code and configs"),
            ToolRequirement(ToolNames.GREP, purpose="search for vulnerable patterns"),
            ToolRequirement(ToolNames.SHELL, required=False, purpose="run scanners"),
            ToolRequirement(ToolNames.WEB_SEARCH, required=False, purpose="look up CVEs"),
        ]

    @classmethod
    def get_capability_requirements(cls) -> list[CapabilityRequirement]:
        return [
            CapabilityRequirement(
                capability_id=CapabilityIds.FILE_OPS,
                purpose="read repository contents",
            ),
            CapabilityRequirement(
                capability_id=CapabilityIds.WEB_ACCESS,
                optional=True,
                purpose="fetch external security references",
            ),
        ]

    @classmethod
    def get_system_prompt(cls) -> str:
        return "You are a security-focused assistant."

    @classmethod
    def get_prompt_templates(cls) -> dict[str, str]:
        return {
            "audit": "Audit the target for security issues and explain severity."
        }

    @classmethod
    def get_task_type_hints(cls) -> dict[str, dict[str, object]]:
        return {
            "audit": {
                "hint": "Start with read-first reconnaissance, then validate findings.",
                "tool_budget": 12,
                "priority_tools": [ToolNames.READ, ToolNames.GREP, ToolNames.SHELL],
            }
        }

    @classmethod
    def get_team_declarations(cls) -> dict[str, dict[str, object]]:
        return {
            "security_review_team": {
                "name": "Security Review Team",
                "formation": "pipeline",
                "members": [
                    {
                        "role": "researcher",
                        "goal": "Inspect the target and identify likely risks.",
                    },
                    {
                        "role": "reviewer",
                        "goal": "Validate findings before escalation.",
                    },
                ],
            }
        }


definition = SecurityVertical.get_definition()
assert definition.definition_version == "1.0"
assert definition.tools == [ToolNames.READ, ToolNames.GREP, ToolNames.SHELL, ToolNames.WEB_SEARCH]
assert definition.team_metadata.teams[0].team_id == "security_review_team"

Definition Contract

VerticalBase.get_definition() is the preferred SDK contract. It returns a validated VerticalDefinition manifest that contains:

  • definition_version
  • canonical tool identifiers
  • typed tool and capability requirements
  • system prompt text
  • prompt metadata and task-type hints
  • team metadata such as declarative team layouts and the default team identifier
  • declarative stage definitions
  • workflow metadata such as initial stage, provider hints, and evaluation criteria

Compatibility note:

  • get_config() still exists as a bridge for current victor-ai integrations
  • VerticalDefinition.to_config() / from_config() bridge the legacy config shape
  • VerticalDefinition.from_dict() supports serialized manifest round-tripping

Packaging

Register the vertical via the standard Victor entry point:

[project]
name = "victor-security"
version = "1.0.0"
dependencies = ["victor-sdk>=1.0.0"]

[project.entry-points."victor.verticals"]
security = "victor_security:SecurityVertical"

Discovery

Victor discovers external verticals through Python entry points:

from victor_sdk.discovery import get_global_registry

registry = get_global_registry()
verticals = registry.get_verticals()

Guides And Examples

Testing

pip install -e ".[dev]"
pytest victor-sdk/tests -q

To verify compatibility with the runtime as well:

pip install -e ".[dev]" victor-ai
pytest victor-sdk/tests/unit tests/integration/test_sdk_integration.py -q

Versioning

The package follows semantic versioning, and the manifest contract is versioned separately via VerticalDefinition.definition_version. External verticals should treat the SDK contract as the source of truth for supported identifiers and manifest fields.

Metadata

Release files for victor-sdk 0.6.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 victor-sdk 0.6.0
File Size Uploaded
victor_sdk-0.6.0.tar.gz 46.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for victor-sdk 0.6.0
File Interpreter ABI Platform
victor_sdk-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 103.7 kB

Release files / victor_sdk-0.6.0.tar.gz

Download URL victor_sdk-0.6.0.tar.gz
Size 46.0 kB
Tags Source
SHA-256 checksum
How to use checksums
ae7b228380b1e073993690469d4194548ea28edf8e99ab6219e40997dc7d50e5
BLAKE2b-256 checksum
How to use checksums
9e27de2d1c470e00389ea942cf700b2ac9fd394e29ed1cc06e63cbc4cc5fc616
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Apr 2, 2026.

Transparency log

Release files / victor_sdk-0.6.0-py3-none-any.whl

Download URL victor_sdk-0.6.0-py3-none-any.whl
Size 57.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1043ee560f45edb7f1d3c17e4d8df244099d129b201fbaa87082db6091996466
BLAKE2b-256 checksum
How to use checksums
1f785aecaaf5c0fa01b67a2f02d77655e102e50fad5e312c082fc9d7210d5887
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Apr 2, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.0 This release

2 release files

0.5.7

1 release file

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