ProviderDock

ProviderDock onboarding guide

Get started without guessing

Follow one clear path from workspace setup to a production-ready integration. ProviderDock manages provider access, tenant isolation, usage controls, and reliability while your application keeps its existing customer experience.

WATCH THE WALKTHROUGH

From signup to useful reports

This narrated, captioned walkthrough shows account setup, console navigation, tenant creation, provider connection, live API-key creation, the first gateway request, and reports populated with representative data.

1 minute
Read the walkthrough transcript
  1. Sign up and open the console. Create an account, choose or create a workspace, and review the setup checklist.
  2. Create a customer tenant. Isolate provider credentials, tokens, usage, limits, and audit activity.
  3. Connect an approved provider. Validate and encrypt OpenAI, Anthropic, or Azure OpenAI credentials.
  4. Generate a live tenant key. Copy the restricted key into a server-side secret manager.
  5. Send the first request. Use the SDK or authenticated HTTPS gateway from your server.
  6. Review reports. Inspect request volume, provider usage, latency, tokens, estimated cost, errors, failovers, and audit activity.

The walkthrough uses representative screens and sample data; it contains no customer information.

Secure by design

Provider credentials and live tenant tokens stay outside browser and mobile code.

Built for scale

Tenant isolation, limits, failover, usage records, and provider health are built in.

Developer friendly

Use the native TypeScript SDK or the same authenticated REST gateway from your language.

ONE CLEAR PATH

Five steps to production

Complete these steps in order. Each step gives you the next action without duplicating the workflow in another menu.

  1. BUSINESS ADMIN PATH

    Set up your workspace

    Create or select the company workspace, invite only the people who need access, and confirm the workspace owner and administrator roles.

    Open the ProviderDock console

  2. CUSTOMER ISOLATION

    Add customer tenants

    Create one tenant per customer using a stable external ID from your SaaS. Each tenant keeps credentials, tokens, limits, and usage records isolated.

  3. PROVIDER CONNECTIONS

    Connect approved providers

    Add OpenAI, Anthropic, or Azure OpenAI credentials in the console. ProviderDock validates and encrypts each connection before it can receive tenant traffic.

  4. LANGUAGE INTEGRATION

    Integrate with your code

    Store a live tenant token only in your server secret manager, keep your existing browser-to-server endpoint, and choose the language your backend already uses.

    Choose your programming language

    JavaScript and TypeScript use the official ProviderDock SDK. Other server languages call the same secure, OpenAI-compatible HTTPS endpoint.

    Native SDK · Node.js server
    ask.tsNative SDK
    npm install provider-dock
    import ProviderDock from "provider-dock";

const providerDock = new ProviderDock({
  apiKey: process.env.PROVIDERDOCK_API_KEY!
});

const response = await providerDock.responses.create({
  model: process.env.PROVIDERDOCK_MODEL ?? "gpt-4.1-mini",
  input: "Hello from TypeScript"
});

console.log(response.output_text);

    Keep PROVIDERDOCK_API_KEY in server-side secrets. Browser and mobile clients should call your authenticated application endpoint, never ProviderDock directly.

    Open the complete integration reference

  5. PRODUCTION CHECKLIST

    Validate and go live

    • Confirm a request succeeds through an isolated staging tenant.
    • Verify request metadata contains no prompt or response content.
    • Test revoked tokens, unavailable models, provider timeouts, and budget limits.
    • Run keyboard and automated WCAG A/AA checks on your customer-facing flow.
    • Keep a temporary rollback path until production behavior is stable.
    Open your workspaceSee a production example