SynAgent
SynAgent is a proof-of-concept agent that orchestrates multiple Syn™ ecosystem packages: SynKit, SynRBL, SynTemp, SynCat, SynRFP, and SynRXN. It wraps each package into a standard tool interface and provides a simple agent core that sequences these tools for end-to-end reaction informatics workflows.
Features
- SynRBL: Rule- and MCS-based reaction rebalancing.
- SynKit: Reaction canonicalization and mechanistic transition graphs.
- SynTemp: High-accuracy reaction template extraction with consensus atom mapping.
- SynCat: Graph-based reaction classification via cross-attention models.
- SynRFP: Mapping-free, permutation-invariant reaction fingerprints.
- SynRXN: Reproducible reaction datasets and splits.
Structure
synagent/: Core package providing the agent (agent.py), registry (registry.py) and tool wrappers.tools/: Implementations of each tool wrapper and a base protocol.
README.md: This document describing the package.
Usage
- Register tools: Instantiate a :class:
~synagent.registry.ToolRegistryand register imported tool instances from :mod:synagent.tools. - Create an agent: Instantiate :class:
~synagent.agent.AgentCorewith the registry. - Build a plan: Create a list of
:class:
~synagent.agent.PlanStepobjects specifying tool names and their parameters. - Run the plan: Call
agent.run(plan)to execute tool calls sequentially.
Example
```python
from synagent import ToolRegistry, AgentCore, PlanStep
from synagent.tools import synrbl_balance, synkit_canonicalize
# 1. Register tools
registry = ToolRegistry()
registry.register(synrbl_balance)
registry.register(synkit_canonicalize)
# 2. Initialize agent
agent = AgentCore(registry)
# 3. Build plan
plan = [
PlanStep("synrbl.balance", {"reaction": "CC=O>>CC(=O)O"}),
PlanStep("synkit.canonicalize", {"reaction": "CC=O>>CC(=O)O", "with_mt_graph": False}),
]
# 4. Run
result = agent.run(plan)
print(result)
```
Notes
-----
- The actual Syn™ packages must be installed in your environment for the
wrappers to work.
- Each tool uses lazy imports to avoid unnecessary dependencies until
invoked.
- Error handling is basic; real-world agents should implement more
robust failure recovery and logging.
License
-------
This repository is released under the Apache 2.0 License, consistent
with the licensing of the underlying Syn packages.
Metadata
Release files for synagent 0.0.1
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 | Actions |
|---|---|---|---|---|
| synagent-0.0.1.tar.gz | 17.4 kB | With provenance | Details for synagent-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| synagent-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for synagent-0.0.1-py3-none-any.whl |
Total release size: 35.4 kB
Release files / synagent-0.0.1.tar.gz
| Download URL | synagent-0.0.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3219580b964cacc4e9ea1082e8ec84b7f3f4575cc0f8b0eed2ba5beb5dd0e35b
|
|
BLAKE2b-256 checksum How to use checksums |
f305d667d3c1c3a001bea0dbe04ca4d1392e0a5194a963fec16386f2bd09703a
|
| 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 Dec 10, 2025.
Transparency logRelease files / synagent-0.0.1-py3-none-any.whl
| Download URL | synagent-0.0.1-py3-none-any.whl |
|---|---|
| Size | 18.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6d92f5ce1cef1c6368f535c66800d67c52dd3ad956c66cafe111515f00851da
|
|
BLAKE2b-256 checksum How to use checksums |
1eb1abb40e59ef173cc8ed616a75991fb35ff69350103bdc7a41c6a10163edc6
|
| 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 Dec 10, 2025.
Transparency logSecurity for synagent 0.0.1
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 synagent-0.0.1.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 Dec 10, 2025.
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.