SDKs
Tensile ships matching SDKs for Python and TypeScript, each with a Conversations surface for app-level agents and an MCP wrapper for MCP servers. Learn which to use.
Tensile offers the same surface in Python and TypeScript, so the concepts you learn in one transfer directly to the other. Each SDK gives you two ways in:
- Conversations — instrument agent turns from your application code.
- MCP — wrap an MCP server so every call it handles is captured for you.
You can use both in the same organization. They write to the same ingestion pipeline and show up together in the dashboard.
Which one do I use
Reach for this when your agent is application code that produces a reply per turn. You control when a turn begins and ends, and you attach the user, the input, and the output.
Reach for this when your agent uses tools through a supported MCP server. The wrapper captures registered tool invocations; it does not currently capture resource reads or prompt calls.
Rules of thumb:
- If you already talk to the model directly and shape the conversation, use Conversations.
- If the model reaches your tools through MCP, use the MCP wrapper to capture registered tool invocations.
- If both are true (an app-level agent that also exposes MCP tools), use both. Turns and tool calls link together into one event tree.
Install
pip install honeainpm install @asymmetric-ai/honeThe shared shape
Both SDKs expose the same core calls. The naming follows each language's conventions (snake_case in Python, camelCase in TypeScript), but the behavior is identical.
| Call | What it does |
|---|---|
init | Configures the SDK with your API key and optional endpoint. |
begin / end | Opens an interaction for a turn and closes it with the output and success flag. |
track | Records a completed turn in one fire-and-forget call. |
identify | Attaches traits to a user id. |
set_property / set_properties | Adds custom properties to the current interaction (for example model, tokens, cost). |
| MCP wrapper | Captures registered tool invocations on supported MCP servers. |
Full references
Authentication
Tensile ingestion is authenticated with a single header: x-api-key. Learn where to get a key, how to send it, and how to keep it safe.
Python SDK
Complete reference for the Tensile Python SDK: init, begin, end, track, identify, set_property, and conversation grouping, with runnable examples.