> ## Documentation Index
> Fetch the complete documentation index at: https://monid.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# When to Use a Proxy

> Run your own proxy when you want full control over billing, validation, and endpoint access.

Run your own proxy in front of Monid when you want **maximum control** over the user experience — billing, validation, and which endpoints users can reach.

## Use a Proxy When

* You want to charge users through **your own billing system**, in dollars, credits, or subscription tiers — with or without markup.
* You need to **whitelist or blocklist** specific Monid endpoints.
* You want to **validate or transform** every request and response.
* Users shouldn't need a Monid account of their own.
* You want Monid to feel like a native part of your product.

## Skip a Proxy When

* Users should own their Monid account and pay Monid directly.
* You don't want to operate any backend infrastructure.

## Examples

<AccordionGroup>
  <Accordion title="Calendar app that runs Monid tools during scheduling">
    A calendar app installs the Monid Skill into its agent and points `MONID_API_BASE_URL` at its proxy. The agent asks Monid to enrich meeting attendees; the proxy validates the request, charges the user credits from the app's own wallet, and forwards approved calls to Monid.
  </Accordion>

  <Accordion title="Vertical SaaS with curated tools">
    A legal research SaaS only wants a handful of Monid endpoints exposed to its users. Its proxy blocklists everything else and adds a 20% markup on Monid's per‑result pricing.
  </Accordion>

  <Accordion title="Enterprise deployment with audit logging">
    An enterprise product logs every Monid request and response for compliance, redacts PII before it leaves the network, and enforces per‑department rate limits — all inside its proxy — before forwarding to Monid.
  </Accordion>
</AccordionGroup>

Ready to build? Continue to [Set Up Your Own Proxy](/integrations/proxy).