Set up direct access

Use ToolPlexer as an internal capability layer. End users do not need a ToolPlexer account or key.

1. Create a server-side key

Create a workspace key from the dashboard and store it in your server-side secret manager. Never send it to a browser or mobile client.

2. Choose an integration pattern

Dynamic capabilities

Use the full workflow when the capability is selected at runtime:

POST /v1/discover  →  POST /v1/inspect  →  POST /v1/run

discover and inspect are free. run is the billed operation.

Curated capabilities

If your product exposes a fixed function, keep the provider and endpoint in your backend and send only validated input:

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

Inspect the endpoint once during implementation and validate user input against its schema before calling run.

3. Handle asynchronous runs

Runs can return a runId before the provider finishes. Poll GET /v1/runs/get?id=<run-id> until a terminal status, or use the CLI/MCP wait controls when those clients own the workflow.

Apply your own authorization, rate limits, spend caps, redaction, and audit logging before forwarding requests. Charge users through your own billing model; ToolPlexer charges the workspace behind the server-side key.