Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rkat.ai/llms.txt

Use this file to discover all available pages before exploring further.

Meerkat is easiest to understand as a composable agent runtime with a practical product layer on top. You can approach it from any surface:
  • Rust embedding
  • Python or TypeScript SDKs
  • CLI
  • REST / JSON-RPC / MCP
  • multi-agent orchestration
The core concepts fit together like this:

Read order

If you are new to Meerkat, a good concepts path is:
  1. Composability
  2. Realms
  3. Sessions
  4. Configuration
  5. Providers
  6. Tools
Then branch into the systems you need:

What each concept owns

ConceptMain question
ComposabilityWhat kind of product is Meerkat, and why do the surfaces behave like peers?
RealmsWhat defines shared vs isolated state?
SessionsHow does one conversation live, continue, and end?
ConfigurationHow are runtime settings stored and updated?
ProvidersHow are models resolved, selected, and capability-gated?
ToolsHow does the agent act on the world?
Auth & bindingsUnder what identity/credentials does the runtime talk to a provider?
Memory & compactionHow does Meerkat handle context beyond one model window?
CommsHow do long-lived agents exchange messages?
MobsHow does Meerkat coordinate multiple agents as one system?
SchedulingHow does durable automation fire over time?
Live ChannelsHow does low-latency interactive transport fit into the session model?

Where To Go Next

After the core concepts, choose the path that matches the system you are building:
PathStart with
Embedding Meerkat in RustRust SDK overview
Driving Meerkat from an appPython SDK or TypeScript SDK
Running Meerkat as a serviceJSON-RPC or REST
Building multi-agent systemsMobs
Running private modelsSelf-hosting models
Understanding ownershipArchitecture

See also