Choose the setup path for your environment
Each setup path provides a complete runtime. The full configuration reference and schema documentation ship directly inside the package.
Run locally without keys
Install Ollama and pull an open-weight model to run a syndicate on your own machine. The tutor executes as one agent, while the council coordinates three. Neither setup sends data beyond your computer.
Swap tutor for council in the command to run the three-agent version.
Install as an npm dependency
Your syndicate definitions live alongside your application code. The package loads them from your project’s config/agents/ directory. You can copy starter configurations directly from the examples included with the package.
import { loadSyndicate, registerAvailableProviders } from 'melchizedek-agents';
registerAvailableProviders(); // routes model ids to the keys you have
const config = loadSyndicate('mine.yaml'); // reads <your-repo>/config/agents/Requires Node 22.12 or newer. The Google ADK is a peer dependency so your application controls the shared model registry. Set MELCHIZEDEK_AGENTS_DIR if you want to load files from an alternate directory.
Run as an HTTP server
The server exposes every file in your agents directory as an A2A endpoint. Callers can supply their own model key with each request. Set a server secret before you expose the port to an external network.
Set GOOGLE_GENAI_API_KEY in your environment, and set A2A_SERVER_SECRET for any deployment beyond your local machine.
Sessions stay in memory unless you supply Supabase credentials. Adding database keys enables session persistence and long-term memory. The SQL migration scripts to provision both tables ship inside the package.