Reference conventions
Each API page distinguishes:
- Recommended import path;
- Exact public signature or dataclass fields;
- Defaults and immutability behavior;
- Return values and exceptions;
- Validation and lifecycle constraints;
- A minimal example where the API benefits from one.
Signatures show semantic defaults such as {} for a dataclass mapping created with default_factory; they do not imply that instances share a mutable default. Types use Python 3.12 syntax because the package requires Python 3.12 or later.
API groups
| Area | Reference |
|---|---|
| Provider lifecycle and optional Provider protocols | Provider API |
| Execution requests, contexts, cancellation, results, and progress | Execution API |
| Standard errors and health reports | Errors and Health API |
| Configuration, secrets, and robot identity | Configuration and Identity API |
| Artifacts, clocks, logging, resource leases, and tracing | Services API |
| Restart-time Provider recovery contract | Recovery API |
| Action self-descriptions | Action Contracts API |
| Capability manifest models, package validation, and version helpers | Manifest and Validation API |
| Test doubles and Provider conformance harness | Testing API |
| `vega-capability` command line interface | CLI Reference |
Versioning and compatibility
vega_capability_sdk.__version__ is the installed SDK version. Capability packages declare a compatible SDK range in capability.yaml; validate it with the manifest APIs rather than comparing version strings manually.
from vega_capability_sdk import __version__print(__version__) # str
__version__ describes the installed SDK distribution. It is not the Capability package version or an Action version. Use vega_capability_sdk.manifests.is_sdk_compatible() or package validation for range checks.
Public import boundaries
vega_capability_sdkis the preferred import surface for Provider-facing contracts and services.vega_capability_sdk.manifestsis the public manifest and package-validation surface.vega_capability_sdk.testingis the public testing surface.- Compatibility modules such as
execution,errors,health,identity,context,recovery, andaction_contractre-export their named contracts. - Modules and symbols beginning with
_, including_immutability, remain private compatibility or implementation surfaces even when importable.
The SDK exposes no Runtime client, Task or Session abstraction, network transport, event bus, or robot-driver API.
