Shinox Agent SDK
A Python library for building agents in the Shinox decentralized mesh network.
Installation
# Using pip
pip install shinox-agent-sdk
# Using uv
uv add shinox-agent-sdk
# With LangChain support
pip install shinox-agent-sdk[langchain]
For local development:
cd shinox-agent-sdk
pip install -e .
Quick Start
Worker Agent (Simple)
For agents that execute tasks and return results:
from shinox_agent import ShinoxWorkerAgent
from brain import brain # Your LangGraph/LangChain brain
from agent import agent_card # Your A2A AgentCard
agent = ShinoxWorkerAgent(
agent_card=agent_card,
brain=brain,
triggers=["calculate", "process"], # Optional custom wake-up words
)
app = agent.app
# Run with: faststream run main:app
The worker automatically:
- Registers with the agent registry
- Joins sessions when invited by Director
- Wakes up when @mentioned or targeted
- Invokes your brain and publishes results
Custom Agent (Advanced)
For agents with complex logic (like Squad Lead):
from shinox_agent import ShinoxAgent, AgentMessage
async def my_handler(msg: AgentMessage, agent: ShinoxAgent):
headers = msg.headers
# Custom wake-up logic
if headers.interaction_type == "SESSION_BRIEFING":
# Handle briefing
pass
if headers.target_agent_id == agent.agent_id:
# Process and respond
await agent.publish_message(
content="Task completed",
conversation_id=headers.conversation_id,
interaction_type="TASK_RESULT",
)
agent = ShinoxAgent(
agent_card=agent_card,
session_handler=my_handler,
triggers=["coordinate", "plan"],
)
app = agent.app
API Reference
ShinoxAgent
Base class for all agents.
ShinoxAgent(
agent_card: AgentCard, # A2A agent card
session_handler: Callable, # async def handler(msg, agent)
triggers: list[str] = None, # Wake-up keywords
agent_url: str = None, # URL for registry (default: env AGENT_URL)
)
Attributes:
agent_id: str- Generated from agent_card.nameactive_sessions: set[str]- Currently joined sessionsbroker: KafkaBroker- FastStream Kafka brokerapp: FastStream- FastStream application
Methods:
publish_message(content, conversation_id, interaction_type, target_agent_id=None)publish_update(content, conversation_id, interaction_type)- Alias for publish_messageresolve_agent_inbox(agent_id) -> str- Get inbox topic for an agentfetch_available_agents(exclude_self=True) -> list[str]- Get active agents from registry
ShinoxWorkerAgent
Worker agent with default wake-up logic.
ShinoxWorkerAgent(
agent_card: AgentCard,
brain: Any, # LangGraph brain with ainvoke()
agent_url: str = None,
triggers: list[str] = None, # Additional wake-up keywords
)
Additional Methods:
publish_task_result(content, conversation_id, target_agent_id=None)
Default Wake-up Triggers:
target_agent_idmatches this agent@{agent_id}mentioned in content- Any custom trigger word found (case-insensitive)
Message Schemas
from shinox_agent import AgentMessage, A2AHeaders
# Create a message
msg = AgentMessage(
content="Hello",
headers=A2AHeaders(
source_agent_id="my-agent",
interaction_type="INFO_UPDATE",
conversation_id="session.123",
)
)
Environment Variables
| Variable | Default | Description |
|---|---|---|
KAFKA_BOOTSTRAP_SERVERS |
localhost:19092 |
Kafka/Redpanda broker URL |
AGENT_REGISTRY_URL |
http://localhost:9000 |
Agent registry URL |
AGENT_URL |
http://localhost:8001 |
This agent's URL for registry |
Architecture
┌─────────────────────────────────────────────────────────────┐
│ ShinoxAgent (Base) │
├─────────────────────────────────────────────────────────────┤
│ • Broker setup (Kafka/Redpanda) │
│ • Registry registration │
│ • Inbox subscription (mesh.agent.{id}.inbox) │
│ • Dynamic session subscription │
│ • Message parsing │
│ • publish_message(), resolve_agent_inbox() │
└─────────────────────────────────────────────────────────────┘
│
│ extends
▼
┌─────────────────────────────────────────────────────────────┐
│ ShinoxWorkerAgent │
├─────────────────────────────────────────────────────────────┤
│ • Default wake-up logic │
│ • Brain invocation │
│ • publish_task_result() │
└─────────────────────────────────────────────────────────────┘
Message Flow
- Director sends
JOIN_SESSIONto agent inbox - Agent joins session, subscribes to session topic, sends acknowledgment
- Director sends
SESSION_BRIEFINGto session topic - Agent wakes up (if triggered), invokes brain, publishes result
License
MIT
Release files for shinox-agent-sdk 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| shinox_agent_sdk-0.1.6.tar.gz | 150.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shinox_agent_sdk-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 183.8 kB
Release files / shinox_agent_sdk-0.1.6.tar.gz
| Download URL | shinox_agent_sdk-0.1.6.tar.gz |
|---|---|
| Size | 150.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42120acbbf6377baac4e8200aae56a45c1b7be96990ce86bdee8ab39d868314b
|
|
BLAKE2b-256 checksum How to use checksums |
cb9ca62921983034e3a874da0a217d38ff350ea8289829829debc7428fe6f334
|
| 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 Mar 10, 2026.
Transparency logRelease files / shinox_agent_sdk-0.1.6-py3-none-any.whl
| Download URL | shinox_agent_sdk-0.1.6-py3-none-any.whl |
|---|---|
| Size | 33.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1fcff19b8bbb05bb628ff8837a8ecdbc6aa1cb6f476f9c3364e752267cf259f
|
|
BLAKE2b-256 checksum How to use checksums |
04f796ddf766f0f9099044a1d26798dc2f01d75691b26554c6e2526c9a67fc8d
|
| 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 Mar 10, 2026.
Transparency log