Installation
Get the Axiom Protocol plugin running in your OpenClaw instance.
Prerequisites
- A running OpenClaw instance with plugin support enabled
- An OpenRouter API key (
sk-or-v1-...) — get one at openrouter.ai - An Axiom Protocol Worker endpoint — deploy your own from the ACP-PROJECT repository or use a hosted endpoint
Install the Plugin
The Axiom Protocol plugin is distributed as an OpenClaw plugin package. Add it to your OpenClaw configuration:
{
"id": "axiom-protocol",
"name": "Axiom Protocol",
"description": "Multi-model consensus via phi-convergence",
"enabled": true
}Environment Variables
Set the OPENROUTER_API_KEY environment variable so the plugin can authenticate with OpenRouter:
export OPENROUTER_API_KEY="sk-or-v1-your-key-here"API key security
The API key is marked as sensitive in the plugin manifest. It is never logged or exposed in tool outputs. You can also pass it directly via the apiKey configuration parameter instead of using an environment variable.
Verify Installation
Once installed, the plugin registers two tools: axiom_consensus and axiom_verify. Test with a simple consensus query:
axiom_consensus query="What is the capital of France?"If the plugin is correctly configured, you should receive a consensus result with a D-score, confidence percentage, and the agreed-upon answer from multiple models.
Default models
If you don't specify models, the plugin defaults to openai/gpt-5.4-mini, anthropic/claude-haiku-4-5, and google/gemini-2.5-flash. You can change the defaults in the configuration.
Next Steps
- Configure worker URL, models, iterations, and consensus threshold
- Learn about axiom_consensus and axiom_verify tools
- Understand error codes and retry logic