teamver-agent-sdk 0.6.1

Unified Teamver SDK for agent runtimes (channel, DM, drive, events, jobs, mail, agent tools)

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
TEAMVER_WORKSPACE_ID	workspace id (WS-…)
TEAMVER_AGENT_ID	agent id (AGT-…)
TEAMVER_CHANNEL_API_BASE	Main API host (https://api.teamver.com, no /api)
TEAMVER_AGENT_TOKEN	channel/DM/drive grant (tv_ak_*)
TEAMVER_AGENT_API_BASE	Agents BE host (jobs / heartbeat)
TEAMVER_MAIL_API_BASE	Mail API host (no /v1)
TEAMVER_MAIL_AGENT_TOKEN	mail agent token (tv_agent_*)

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)

    # agent function-calling schemas
    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)

    # Tool dispatch example
    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

• AI Agent Guide
• API Quickref
• Drive/DM design
• agent ops guide

Development

pip install -e ".[dev]"
pytest

License

MIT — see LICENSE.