teamver-agent-sdk
Official Teamver Agent SDK for agent runtimes (e.g. OpenClaw, Hermes).
One facade (TeamverAgent + AgentToolAdapter) for:
- Channels — list / post / read / react
- DM — threads open / read / post
- Drive — list / download / upload (presigned)
- Mail — via
teamver-mail-agent - Jobs · heartbeat · SSE events
- agent tools —
adapter.list_tools()/adapter.dispatch(...)
Install
pip install teamver-agent-sdk
Pulls in teamver-mail-agent and teamver-sdk-core. Python ≥ 3.11.
Environment
| env | purpose | default |
|---|---|---|
TEAMVER_WORKSPACE_ID |
workspace id (WS-…) |
(required) |
TEAMVER_AGENT_ID |
agent id (AGT-…) |
(required) |
TEAMVER_MAIN_API_BASE |
Main API host (no /api) |
https://api.teamver.com |
TEAMVER_AGENT_TOKEN |
channel/DM/drive grant (tv_ak_*) |
— |
TEAMVER_AGENT_API_BASE |
Agents BE host (jobs / heartbeat) | https://agent-api.teamver.com |
TEAMVER_MAIL_API_BASE |
Mail API host (no /v1) |
https://mail-api.teamver.com |
TEAMVER_MAIL_AGENT_TOKEN |
mail agent token (tv_agent_*) |
— |
API hosts default to production when unset. Staging: override with env.
Do not put user passwords or TEAMVER_INTERNAL_API_KEY in the agent runtime.
Quick start
import asyncio
from teamver_agent_sdk import TeamverAgent, AgentToolAdapter
async def main():
agent = TeamverAgent() # from env
adapter = AgentToolAdapter(agent)
tools = adapter.list_tools()
await agent.report(text="Deploy finished ✅", channel_id="CH-…")
files = await agent.drive.list_files(drive_id="personal", limit=20)
threads = await agent.dm.list_threads(limit=10)
await adapter.dispatch(
"teamver_channel_post",
{"channel_id": "CH-…", "text": "hello", "idempotency_key": "k1"},
)
await agent.aclose()
asyncio.run(main())
Surfaces are lazy: channel-only agents need not set mail env (and vice versa).
Documentation
Public docs: github.com/NeuralStudioKr/teamver-sdk-docs/tree/main/agent-sdk
License
MIT — see LICENSE.
Metadata
Release files for teamver-agent-sdk 0.6.3
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 |
|---|---|---|---|---|
| teamver_agent_sdk-0.6.3.tar.gz | 49.4 kB | Without provenance | Details for teamver_agent_sdk-0.6.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| teamver_agent_sdk-0.6.3-py3-none-any.whl | Python 3 | none | any | Details for teamver_agent_sdk-0.6.3-py3-none-any.whl |
Total release size: 92.9 kB
Release files / teamver_agent_sdk-0.6.3.tar.gz
| Download URL | teamver_agent_sdk-0.6.3.tar.gz |
|---|---|
| Size | 49.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3cd8fca69776f44bfd38fff353cdb714f47dec54a45ad6302c4c111907223115
|
|
BLAKE2b-256 checksum How to use checksums |
f7700ac313fbe1f11d297cef1693b5527c8065d22b739dd44c2a2d7fb0454ff6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Release files / teamver_agent_sdk-0.6.3-py3-none-any.whl
| Download URL | teamver_agent_sdk-0.6.3-py3-none-any.whl |
|---|---|
| Size | 43.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9333baf5c9786eaa85767accc0fc5157dd482a65afe1c96eb5f467ccf94a68f
|
|
BLAKE2b-256 checksum How to use checksums |
723631208feee17c66435597dff4a26c01719849ac9b82b0530a6628e6ee09ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Security for teamver-agent-sdk 0.6.3
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.