Skip to main content

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 (W-…; legacy WS-… still accepted) (required)
TEAMVER_AGENT_ID agent id (AG2-…; legacy AGT-… still accepted) (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_AGENTS_API_BASE alias of the above (OpenClaw openclaw.env) used if TEAMVER_AGENT_API_BASE is unset
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.

OpenClaw also receives TEAMVER_CONTROL_PLANE_TOKEN (tv_cp_*). This SDK does not read it. Channel / DM / Drive / Mail use tv_ak_* and tv_agent_* only.

ACL in Agents Console is policy. Without tv_ak_* in the runtime env, channel/Drive/DM calls fail even if Access looks OK.

Do not put user passwords or TEAMVER_INTERNAL_API_KEY in the agent runtime. Do not SSH-export tokens as the product fix — they come from Desired → VM Manager → openclaw.env.

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.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for teamver-agent-sdk 0.6.5
File Size Uploaded Provenance Actions
teamver_agent_sdk-0.6.5.tar.gz 46.7 kB Without provenance Details for teamver_agent_sdk-0.6.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for teamver-agent-sdk 0.6.5
File Interpreter ABI Platform Actions
teamver_agent_sdk-0.6.5-py3-none-any.whl Python 3 none any Details for teamver_agent_sdk-0.6.5-py3-none-any.whl

Total release size: 85.8 kB

Release files / teamver_agent_sdk-0.6.5.tar.gz

Download URL teamver_agent_sdk-0.6.5.tar.gz
Size 46.7 kB
Tags Source
SHA-256 checksum
How to use checksums
e40f494cf911c5319e6055edcdda32d2e4d63bda495638413183d59be7899b7b
BLAKE2b-256 checksum
How to use checksums
0b961aa783e593e502e4cd77144e50b9cade90859382019b8f1eeb515f86e872
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.5-py3-none-any.whl

Download URL teamver_agent_sdk-0.6.5-py3-none-any.whl
Size 39.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b1ef499199a256d979ed118117f110cf2199634d343cc951616ff18f7b05028a
BLAKE2b-256 checksum
How to use checksums
280a7fb494b2f296bd382a9352a6ded7393f0fb045ce9c40aa772f3cf85754df
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.5

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page