Build on Tessen

One API for conversation, memory, agents and deployment. Start in a sandbox that cannot touch your production data.

Start in the sandbox

Your first key should be a sandbox key. A sandbox authenticates as a separate account, so no request it makes can reach real data — which means your first integration test cannot run against your customers.

Clients

TypeScriptpackages/sdk
Pythonpackages/sdk-python
Command linetessen search · brief · approve

Both SDKs return the API's refusals rather than throwing them. “Not enough history” is an answer, not a fault; only transport and authentication failures throw.

All three ship in the repository. None is published to a package registry yet, so there is no install command to copy — deliberately, rather than printing one that would fail.

How it behaves

KeysShown once, then only a hash is kept. A key can never mint another key, and never exercises a person's data rights — those need a signed-in human.
AgentsAgents propose; people approve. A key cannot approve the thing it proposed.
WebhooksDestinations are checked before they are stored, including after DNS resolution. Payloads are signed; reject timestamps older than 300 seconds.
Verification/api/academy/verify needs no key at all.

Reference

The full endpoint reference is API.md in the repository. Your keys, sandbox, webhooks and request usage appear on this page once you are signed in.