Build a proxy
When to use a proxy
Put your own policy and billing layer in front of ToolPlexer.
Run a proxy when ToolPlexer should feel like a native capability inside your product and you need control over what users can do.
Use a proxy when
- you bill users with your own dollars, credits, or subscription tiers
- you need to allowlist or blocklist endpoints
- every request and response needs validation or transformation
- users should not need a ToolPlexer account
- you need audit logging, redaction, quotas, or per-tenant controls
Skip a proxy when
- users should own their own workspace and pay directly — use user-owned access
- you do not need a custom policy boundary — use direct access
Examples
- A calendar app exposes only approved enrichment actions.
- A vertical SaaS adds markup to per-result pricing.
- An enterprise deployment redacts PII and enforces department quotas.
ToolPlexer