Agntshare (agnt.sr)
HTTPS for AI Agent State.
Today, AI agents hand off tasks by stuffing 100k+ tokens of raw memory into prompt windows. It’s slow, expensive, and degrades context.
Agntshare replaces raw context with a cryptographically verified "coat-check ticket" (Pathway Token). Mint a token on Agent A, pass a tiny 28-byte string, and let Agent B resolve the exact state it needs.
🚀 Quickstart
Install the zero-dependency SDK:
pip install agentshare
Zero-Friction Local Handoff (No API Keys Required):
from agentshare import AgentShareClient
# Initialize in local sandbox mode
client = AgentShareClient(mode="local")
# Agent A (Research) - Mints token for a massive state payload
state_payload = {"summary": "Deep-dive analysis...", "data": [1, 2, 3, 4, 5]}
token = client.mint_pathway_token(payload=state_payload, framework="python")
print(f"Token: agnt.sr/{token}")
# Agent B (Writer) - Resolves only the keys it needs
resolved = client.resolve_pathway_token(token, keys=["summary"])
print(resolved['state'])
🛠️ Framework Integrations
LangChain Integration
from agentshare.integrations import AgentShareCallbackHandler
# 1-Line RunnableConfig integration
handler = AgentShareCallbackHandler(ttl_seconds=3600)
chain.invoke(input_data, config={"callbacks": [handler]})
Universal MCP Server (Claude Desktop & Cursor)
# Run stdio FastMCP server
python -m agentshare.integrations.mcp_server
🔒 Security & Inviolable Laws
- Law 1: The Server is Blind (Zero-Trust Transport): The backend server NEVER parses or inspects payload bytes. Uploads and downloads use direct S3/R2 presigned URLs.
- Law 2: The Token is the Truth: Pathway Tokens carry mandatory SHA-256 integrity checksums, TTL expiration window, scope rules, and cryptographic signatures.
- Law 3: Zero-Friction Adoption: Integrations defensively swallow callback exceptions to ensure 0% impact on production agent executions.
License
MIT © Deepak V & Agntshare Contributors
Metadata
Release files for agntshare 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 | Actions |
|---|---|---|---|---|
| agntshare-0.1.0.tar.gz | 11.6 kB | Without provenance | Details for agntshare-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agntshare-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agntshare-0.1.0-py3-none-any.whl |
Total release size: 21.7 kB
Security for agntshare 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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.