Skip to content
DeepTokenInference Gateway
HomeDashboardModelsPromptsLeaderboardDocsPricingEnterpriseBlog
    1. Home/
    2. Help/
    3. Getting Started
    Three-minute setup

    Getting Started with DeepToken

    Create an account, issue an API key, and send your first OpenAI-compatible request through the DeepToken gateway with routing, metering, and team controls enabled from day one.

    Gateway base URL

    https://api.deeptoken.app/v1

    Create account

    Sign up, verify your email, and choose whether you are working solo or inside an organization.

    Issue API key

    Create a scoped key, set optional model and IP limits, then store the secret in your secret manager.

    Send request

    Point any OpenAI-compatible SDK at the /v1 gateway and pass a supported model id.

    Watch usage

    Review tokens, latency, fallback hops, costs, and request status from the dashboard.

    Govern spend

    Use budgets, organizations, scoped keys, and billing exports before production traffic grows.

    Make your first request

    DeepToken follows the OpenAI Chat Completions schema, so most existing SDK code only needs a new base URL and API key. The model id stays explicit while routing and fallback are handled by the gateway.

    curl https://api.deeptoken.app/v1/chat/completions \
      -H "Authorization: Bearer $DEEPTOKEN_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "model": "gpt-4o-mini",
        "messages": [
          { "role": "user", "content": "Say hello from DeepToken" }
        ]
      }'

    Route by model, not provider

    Use catalog model ids in your client code. DeepToken resolves the upstream provider, applies health-aware fallback, records token usage, and keeps your application isolated from provider-specific changes.

    Production tip

    Start with a primary provider plus at least one fallback for latency-sensitive traffic. Keep strict budgets on new keys until your usage pattern is stable.

    Control usage and billing

    Every request is metered into quota with model, key, route, and organization context. This keeps finance exports and engineering debugging aligned.

    • Monthly budgets per API key or organization
    • Request logs with latency, status, retries, and token counts
    • Quota balance, invoices, and CSV exports
    • Audit trail for key, member, routing, and billing changes

    Recommended next steps

    Open API keysCreate or rotate keys and apply model, budget, and IP controls.Browse modelsFind model ids, context windows, and capabilities before coding.View pricingCompare quota packs, subscriptions, and usage assumptions.
    Need integration help?

    Send context about your SDK, provider needs, budget limits, or organization setup. The request goes into the DeepToken operations queue.

    Contact support