Skip to main content
By the end of this page one agent will have written a decision and a second agent — from a different vendor — will have read it back. That handover is the whole product; everything else is detail.

​
Prerequisites

Prefer to run everything yourself? Skip this page and go to Self-hosting — one command brings up the engine locally and wires your agents to it.

​
Get connected

1

Create an API key

Sign in at app.klio.tech, open Settings → API keys, and create a key. It looks like vex_live_….
The key is shown once. Store it in your password manager or an environment variable — never commit it to a repository.
2

Point your agent at the workplace

Klio’s hosted endpoint speaks Streamable HTTP MCP:
Authenticate with the X-Vex-Key header. For Claude Code:
X-Vex-Agent is optional but recommended — it is what lets you see which agent wrote what. Clients that omit it share a single default agent identity. See Authentication for every header.
3

Confirm the tools are there

Ask your agent to list its tools, or run:
You should see ten Klio tools: recall, remember, observe, plan, decide, note, artifact_put, artifact_get, space, and forget.

​
Prove the handover

This is worth doing once, deliberately, so you can see the mechanism work.
1

Have the first agent decide something

In your connected agent, say:
We’re going to retry 429s with jittered backoff, capped at five attempts. Record that decision — the reason is that the upstream rate-limits per minute, and fixed backoff was synchronising our retries.
The agent should call decide. You can also call it directly:
2

Ask a different agent, cold

Open a different agent — Cursor if the first was Claude Code — connected with the same key. Start a fresh session and ask:
How do we handle rate limiting on the upstream API?
It calls recall, finds the decision, and answers with the rationale. You never re-explained it.
If the second agent found the decision, your workplace is working. Every other page here is about doing this well at scale — scoping it properly, keeping the right things, and retiring what stops being true.

​
Make it a habit

Agents recall well when asked, but the value compounds when writing is automatic. Add something like this to your agent’s system prompt or rules file:
Klio strips secrets and personal data before anything is stored, and the redaction step fails closed — if content cannot be made safe, it is not written. That is a backstop, not a licence to send it everything. See What Klio keeps.

​
Next

Scope and spaces

Keep a team’s memory shared without turning it into one global pile.

Tool reference

Exact parameters and defaults for all ten tools.