Have an AI agent? Let it explore Baltor for you. Any assistant works, personal or coding.

Connect your agent
What your agent reads

The request it copies

Explore baltor.ai for me and report back. Start with https://baltor.ai/llms.txt, then read https://baltor.ai/.well-known/agent-card.json and https://baltor.ai/.well-known/mcp.json. Tell me which plan (Feeds at $4.99/mo, Pro at $29/mo, or Max at $49/mo) fits my work, what you would connect, and the setup steps at https://baltor.ai/connect. Stay read-only: read public pages and agent files, and check with me before any sign-in, purchase or change. If a step needs a key, name it (BALTOR_SERVICE_TOKEN) and I will add it myself.

Discovery files on baltor.ai

Read-only discovery is open. Keep BALTOR_SERVICE_TOKEN in your own environment.

Baltor
AccountMax Sign out

Keys and connections

Give each agent or device its own Baltor key.

Your keys

Keys stay active until they expire or you revoke them.

{{ activeCount }} active

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 purposeAllowed operationsCreatedExpiresLast usedActions
Claude Code, laptopSearchDownloadAug 28, 2026Nov 26, 2026Today, 9:41 AMRevoked
Codex, CISearchDownloadSep 1, 2026Nov 30, 2026Today, 9:12 AMRevoked
Baltor Harness, workerSearchDownloadSep 8, 2026Oct 23, 2026Today, 2:17 AMRevoked
Device or purposeAllowed operationsCreatedExpiresLast usedActions
{{ newKey.name }}{{ newKey.opsText }}Today{{ newKey.expires }}Waiting for its first requestRevoked
Claude Code, laptopSearchDownloadAug 28, 2026Nov 26, 2026Today, 9:41 AMRevoked
Codex, CISearchDownloadSep 1, 2026Nov 30, 2026Today, 9:12 AMRevoked
Baltor Harness, workerSearchDownloadSep 8, 2026Oct 23, 2026Today, 2:17 AMRevoked

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.

$ curl https://baltor.ai/api/v1/capabilities
Ready to test

Connected. Checked just now with the key for Claude Code, laptop.

Tools your connection can use

  • intelligence_searchSearch the library
  • provisioning_manifestList an item’s files
  • provisioning_readDownload an item’s exact files
  • public_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.

Allowed operations

{{ 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
Open the Claude Code setup guide
  • Codex reads skills from .agents/skills/
  • Instruction file: AGENTS.md
Open the Codex setup guide
  • OpenCode reads skills from .opencode/skills/
  • Instruction file: AGENTS.md
Open the OpenCode setup guide
  • Pi reads skills from .pi/skills/
Open the Pi setup guide
  • The Baltor Harness reads the task file it is given, so each step lists the files it needs.
Open the Baltor Harness setup guide

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.

Bash
# Prompts for the key and keeps it hidden
read -rsp "Baltor service token: " BALTOR_SERVICE_TOKEN
export BALTOR_SERVICE_TOKEN
# When you are done
unset BALTOR_SERVICE_TOKEN

Merge the configuration

The configuration holds the variable name; your key stays in your environment. The setup guide names the exact file.

Entry JSON
{
"mcpServers": {
"baltor": {
"type": "http",
"url": "https://baltor.ai/mcp",
"headers": {
"Authorization": "Bearer ${BALTOR_SERVICE_TOKEN}"
}
}
}
}

Remove a connection

  1. Revoke its key under Your keys.
  2. After closing the tool, clear the variable: unset BALTOR_SERVICE_TOKEN
  3. Remove the baltor entry from its configuration.

Your harness decides what runs, with the permissions you choose. Serving and connections