Keys and connections
Give each agent or device its own Baltor key.
Your keys
Keys stay active until they expire or you revoke them.
Revoke the key for {{ confirm.name }}? Revocation takes effect on its next request.
Revoked the key for {{ revokedMsg.name }}. Files you already downloaded stay on your computer.
| Device or purpose | Allowed operations | Created | Expires | Last used | Actions |
|---|---|---|---|---|---|
| Claude Code, laptop | SearchDownload | Aug 28, 2026 | Nov 26, 2026 | Today, 9:41 AM | |
| Codex, CI | SearchDownload | Sep 1, 2026 | Nov 30, 2026 | Today, 9:12 AM | |
| Baltor Harness, worker | SearchDownload | Sep 8, 2026 | Oct 23, 2026 | Today, 2:17 AM |
| Device or purpose | Allowed operations | Created | Expires | Last used | Actions |
|---|---|---|---|---|---|
| {{ newKey.name }} | {{ newKey.opsText }} | Today | {{ newKey.expires }} | Waiting for its first request | |
| Claude Code, laptop | SearchDownload | Aug 28, 2026 | Nov 26, 2026 | Today, 9:41 AM | |
| Codex, CI | SearchDownload | Sep 1, 2026 | Nov 30, 2026 | Today, 9:12 AM | |
| Baltor Harness, worker | SearchDownload | Sep 8, 2026 | Oct 23, 2026 | Today, 2:17 AM |
Service endpoint
One address for every agent you connect.
How requests connect
- Protocol
- Model Context Protocol over streamable HTTP
- Each request
- A Baltor key, as a bearer header
- Configuration
- Names the key
BALTOR_SERVICE_TOKEN - OAuth
- Where your app offers it
Connection check
Lists the tools your connection can use.
- Key
- Claude Code, laptop
Ask the service first
Versions, transport, search modes and limits.
Connected. Checked just now with the key for Claude Code, laptop.
Tools your connection can use
intelligence_searchSearch the libraryprovisioning_manifestList an item’s filesprovisioning_readDownload an item’s exact filespublic_good_filesFree Public Good files
Create a key
One key for each tool or device. It can search and download what your plan allows.
Name it after the tool or device, so you know which key to revoke later.
{{ expiresHelp }}
Key created for {{ newKey.name }}. We show each key once, so copy it now.
Paste it where your tool reads BALTOR_SERVICE_TOKEN, then clear it from this page.
Cleared from this page. The key for {{ newKey.name }} is listed under Your keys.
Connect a harness
Pick yours, keep the key in your environment and merge one entry into its configuration.
- Claude Code reads skills from
.claude/skills/ - Instruction file:
CLAUDE.md
- Codex reads skills from
.agents/skills/ - Instruction file:
AGENTS.md
- OpenCode reads skills from
.opencode/skills/ - Instruction file:
AGENTS.md
- Pi reads skills from
.pi/skills/
- The Baltor Harness reads the task file it is given, so each step lists the files it needs.
17 more connect over MCP: Cursor, Gemini CLI, GitHub Copilot, Windsurf, Cline, Roo Code, Kilo Code, Aider, Goose, Amp, Kiro, Zed, Qwen Code, Crush, Factory Droid, Hermes Agent and OpenClaw.
Keep the key in your environment
The prompt hides the key while you paste it, and your shell history keeps only the command.
Merge the configuration
The configuration holds the variable name; your key stays in your environment. The setup guide names the exact file.
Remove a connection
- Revoke its key under Your keys.
- After closing the tool, clear the variable:
unset BALTOR_SERVICE_TOKEN - Remove the
baltorentry from its configuration.
Your harness decides what runs, with the permissions you choose. Serving and connections