The protocol, the client and the setup
Baltor is one authenticated endpoint that serves material to the tools you already run.
The facts
- Endpoint
https://baltor.ai/mcp- Transport
- Model Context Protocol over streamable HTTP
- Protocol versions
2025-11-25for the handshake and2026-07-28per request, named in the capabilities record- Authentication
- OAuth where your app supports it, or a Baltor key sent as a bearer header and named
BALTOR_SERVICE_TOKENin your settings - Session
- Stateless: each request carries its own key
- Tools
- intelligence_searchprovisioning_manifestprovisioning_readpublic_good_files
The entry holds the variable name; your key stays in your environment.
References first, bodies second
- 1Search returns referencesSmall references and their facts, from
intelligence_search. Bodies arrive with a download. - 2List an item's files
provisioning_manifestnames the files an item holds before anything is read. - 3Download names the SHA-256
provisioning_readdelivers the exact bytes through a separate authorized download that names their SHA-256.
Small items can be read inline, up to 16,384 bytes. A download carries up to 1,048,576 bytes.
Versions, on purpose
A request for another protocol version gets a reply that lists the versions the service serves, so the client picks one. Every change stays the client's choice.
2025-11-25Served for the handshake2026-07-28Served per request
Read October 25, 2026, from the capabilities record.
Ask the service first
Before any setup, the capabilities record lists the versions, transport, search modes and download limits. It is public, so your client can read it before it asks for a key.
Connect your client.
Pro is $29 a month, with a key for each client you connect.
Pro
$29a month
Includes Agent Feeds + Skills and agent files
- The whole library, 1,560,856 files
- One downloaded item is the measured unit
- A Baltor key for each tool you connect
Model usage stays with your provider. Cancel any time from your account page.