Set up a proxy

Your proxy is the public product boundary. It authenticates your users, applies policy, then forwards approved requests to ToolPlexer with a server-side key.

How it works

user or agent → your proxy → ToolPlexer API → provider endpoint

1. Expose your product API

Choose the interface your users need. It can be a narrow function API, a REST surface, or an MCP server. Do not expose the raw ToolPlexer API key.

2. Validate and authorize

Before forwarding a request:

• authenticate the caller and resolve its tenant
• validate input against the inspected endpoint schema
• enforce an endpoint allowlist
• apply rate limits and spend caps
• redact sensitive fields in logs

3. Forward approved calls

const response = await fetch("https://api.toolplexer.com/v1/run", {
  method: "POST",
  headers: {
    Authorization: "Bearer <proxy-server-side-key>",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ provider, endpoint, input }),
});

Forward the run status and runId without hiding whether the request was blocked, failed, stopped, or completed. Poll through your proxy so callers never need ToolPlexer credentials.

4. Own billing and observability

Record the tenant, endpoint, quoted price, provider status, and final settlement in your system. Charge users according to your product model and keep a clear mapping back to the ToolPlexer run ID for support.