Skip to main content
Run your own proxy in front of Monid, then point your users’ agents (via Skill or MCP) at your proxy. Your service sits in the middle and handles everything before the request reaches Monid.

​
How It Works

1

Create your own proxy server

Stand up an HTTP server at a URL you control (e.g. https://your-proxy.example.com). It will accept the same request shapes as the Monid API.
2

Install the Monid Skill or CLI and point it at your proxy

Install the Monid Skill and the Monid CLI, then set the environment variable to your proxy URL:
All Monid CLI traffic will now hit your proxy instead of https://api.monid.ai.
3

Your proxy decides and forwards

Every discover, inspect, and run call arrives at your proxy. Inspect the request, apply your own auth / billing / allowlist, and forward approved requests to https://api.monid.ai using your own Monid credentials. Return the response to the caller.

​
What Your Proxy Can Do

  • Validate incoming requests — authenticate your own users, enforce rate limits, and check inputs.
  • Bill your own way — charge in dollars, credits, or subscription tiers, with or without markup on Monid’s per‑call and per‑result pricing.
  • Whitelist or blocklist endpoints — restrict which Monid endpoints your users can reach.
  • Rewrite or enrich responses — add your own metadata, cache results, or transform payloads.

​
Environment Variable

Set the Monid client’s base URL to your proxy:
The Skill, MCP, CLI, and API clients all respect this variable.

​
Forwarding to Monid

Inside your proxy, forward approved requests to Monid using your own API key or an OAuth access token. Include an x-workspace-id header — get available workspace IDs from GET /v1/auth/workspaces:
See the API Reference for the full request and response formats.

​
When to Use This

Use the proxy model when you want maximum control over the user experience, billing, and available tools — for example, embedding Monid inside a calendar app, a workflow product, or a curated agent platform.