This release is a pre-release and may not be stable for production use.
agent-topology-spec
Validate, canonicalize, and hash agent-topology JSON documents in Python 3.11–3.14. This package has no framework dependency and does not install a CLI.
python -m pip install "agent-topology-spec==0.1.0b2"
import json
from pathlib import Path
from agent_topology.spec import compute_structure_hash, validate_document
document = json.loads(Path("topology.json").read_text(encoding="utf-8"))
errors = validate_document(document)
if errors:
raise ValueError("\n".join(errors))
print(compute_structure_hash(document))
print(document["completeness"])
print(document["producerLimitations"])
Validation checks schema, references, and completeness; it does not verify the
recorded hash. canonical_json serializes canonical JSON; finalize_document
recomputes the hash and returns a canonical copy. These utilities do not mutate
their input or validate it automatically.
To derive documents from compiled Python LangGraph graphs, install
agent-topology-langgraph instead. Its specification dependency is installed
automatically.
The 0.1 format is provisional. Package versions, document format versions, and hash algorithm versions are independent.
Documentation · Consumer guide · Source and issues
Licensed under the MIT License; see the included LICENSE file.
Join connections (unreleased)
Current source exports derived_join_edges(structure); published beta.2 does not.
from agent_topology.spec import derived_join_edges
# After validate_document(document) succeeds:
links = derived_join_edges(document["graphs"][0]["structure"])
The helper returns one fresh {joinId, source, target} record per join source,
sorted first by joinId, then by source, using lexicographic Unicode code point
order (shorter prefixes first, without normalization or locale collation). Empty
joins produce an empty list. Input objects and arrays are not mutated.
Consumers must read both structure.edges and structure.joins. Derived links
retain their join identity even when endpoints coincide with another join or a
direct edge. They describe the original join's AND convergence: all its sources
are required. They do not imply independent edge execution. Keep them separate
from ordinary edges; no ordinary edge id or kind is assigned. Validate the
containing document at the input boundary; the helper does not validate again.
Metadata
Release files for agent-topology-spec 0.1.0b3
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 | |
|---|---|---|---|---|
| agent_topology_spec-0.1.0b3.tar.gz | 13.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agent_topology_spec-0.1.0b3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.9 kB
Release files / agent_topology_spec-0.1.0b3.tar.gz
| Download URL | agent_topology_spec-0.1.0b3.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6da5f5640eae25477771845ea171fef80195856163e69a5f9d4dc047862a71d
|
|
BLAKE2b-256 checksum How to use checksums |
69e369ed2ef9589f85467a1138c79ab9fb77e4a62498512fd18cced56dbb52fe
|
| 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 12, 2026.
Transparency logRelease files / agent_topology_spec-0.1.0b3-py3-none-any.whl
| Download URL | agent_topology_spec-0.1.0b3-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
45732c5080126484af8ba4bea7a1767f72fca27721825c0f678321fa7093e276
|
|
BLAKE2b-256 checksum How to use checksums |
71acb727fa2ce0a8ac2dedb9877462a7277cae36d972af2b3c4211dc592f7ae5
|
| 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 12, 2026.
Transparency logSecurity for agent-topology-spec 0.1.0b3
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 agent_topology_spec-0.1.0b3.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 12, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.