maivn-contracts
maivn-contracts contains the typed wire models, JSON Schemas, loaders, and
validators shared by mAIvn services and the Python SDK.
Install
pip install maivn-contracts
Import from a focused public namespace rather than from its implementation modules:
from maivn_contracts.events import Event, validate_event
from maivn_contracts.messages import Message, validate_message
from maivn_contracts.tools import ToolCall, validate_tool_call
The package exposes contract families for agents, artifacts, events, messages,
resources, runtime state, scenarios, swarms, tools, toolsets, and workers. Each
family's load_*_schema functions return the checked-in schema, validate_*
functions validate untrusted wire data, and Pydantic models provide typed
construction and parsing.
Treat schemas and their canonical encodings as protocol boundaries. Do not copy private fields into logs or relax a validator only in one consumer. Update the shared contract and all affected producers and consumers together.
1 maintainer
Metadata
1 maintainer
Release files for maivn-contracts 0.1.0
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 | |
|---|---|---|---|---|
| maivn_contracts-0.1.0.tar.gz | 405.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| maivn_contracts-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 587.0 kB
Release files / maivn_contracts-0.1.0.tar.gz
| Download URL | maivn_contracts-0.1.0.tar.gz |
|---|---|
| Size | 405.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43948c2ab67ddc8e60c4d14e96b5141093b373c9d207fd317ff82c81fa0369cd
|
|
BLAKE2b-256 checksum How to use checksums |
df12350b010630738a1e9efd1436b4d700621dca9a01c8ce0c707678358ed47d
|
| 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 Sep 28, 2026.
Transparency logRelease files / maivn_contracts-0.1.0-py3-none-any.whl
| Download URL | maivn_contracts-0.1.0-py3-none-any.whl |
|---|---|
| Size | 181.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
343aff0c297bc6ce4a26ed3548708cb7abc6b0381c2bb1859cbbbaaf77c06880
|
|
BLAKE2b-256 checksum How to use checksums |
83f21c59cf9f3a0c5f8c9a5abf738be19f31a7fb0ea4c1be97be016120492666
|
| 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 Sep 28, 2026.
Transparency logSecurity for maivn-contracts 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for maivn_contracts-0.1.0.tar.gz
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 Sep 28, 2026.
Transparency logA 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.
