Coming soon

Final CLI and config steps will ship when the connector enters beta. Join the waitlist below and we’ll send the launch command.

Get connected in 3 steps

1
Run npx @agentvalet/register - generates an RS256 keypair, records your agent in the registry, and outputs your OWNER_ID.
2
Set the MCP server via openclaw mcp set agentvalet https://api.agentvalet.ai/mcp/v1/YOUR_OWNER_ID - or edit ~/.openclaw/openclaw.json with the config above.
3
Restart OpenClaw. AgentValet tools are immediately available to agents routing through your gateway. Approve platforms in the dashboard and they appear as callable tools.

Self-hosted, end to end

OpenClaw agents can call SaaS platforms via AgentValet without storing credentials in the gateway config. Since OpenClaw is self-hosted alongside AgentValet, both stay inside your own infrastructure.

Fully self-hosted stack
OpenClaw runs on your server. AgentValet runs on yours too (self-hostable). No data leaves your infrastructure - Telegram/Discord/Slack messages in, governed SaaS calls out, everything proxied through systems you control.
No credentials in gateway config
OpenClaw's config never holds API keys for downstream services. All credentials live in AgentValet's encrypted vault.
Messaging → governed actions
When an agent triggered from Telegram needs to update a Notion page or post to Slack, that call goes through AgentValet's permission matrix.
Per-agent scoping
Different OpenClaw agents (different chat bots, different users) can have different platform permissions - all managed in one place.
Full audit trail
Every platform call logged: which gateway agent, which user session, which SaaS action, and when. Review in the dashboard at any time.

OpenClaw integration is coming soon

Join the waitlist to get early access and the final install command when the connector ships.