Route Claude CLI traffic through Kong AI Gateway and Gemini

This is a Konnect tutorial and requires a Konnect personal access token.

1. Create a new personal access token by opening the Konnect PAT page and selecting Generate Token.

2. Export your token to an environment variable:

    export KONNECT_TOKEN='YOUR_KONNECT_PAT'
   

   Copied!

3. Run the quickstart script to automatically provision a Control Plane and Data Plane, and configure your environment:

    curl -Ls https://get.konghq.com/quickstart | bash -s -- -k $KONNECT_TOKEN --deck-output
   

   Copied!

   This sets up a Konnect Control Plane named quickstart, provisions a local Data Plane, and prints out the following environment variable exports:

    export DECK_KONNECT_TOKEN=$KONNECT_TOKEN
    export DECK_KONNECT_CONTROL_PLANE_NAME=quickstart
    export KONNECT_CONTROL_PLANE_URL=https://us.api.konghq.com
    export KONNECT_PROXY_URL='http://localhost:8000'
   

   Copied!

   Copy and paste these into your terminal to configure your session.

This tutorial requires Kong Gateway Enterprise. If you don’t have Kong Gateway set up yet, you can use the quickstart script with an enterprise license to get an instance of Kong Gateway running almost instantly.

1. Export your license to an environment variable:

    export KONG_LICENSE_DATA='LICENSE-CONTENTS-GO-HERE'
   

   Copied!

2. Run the quickstart script:

   curl -Ls https://get.konghq.com/quickstart | bash -s -- -e KONG_LICENSE_DATA 
   

   Copied!

   Once Kong Gateway is ready, you will see the following message:

    Kong Gateway Ready
   

decK is a CLI tool for managing Kong Gateway declaratively with state files. To complete this tutorial, install decK version 1.43 or later.

This guide uses deck gateway apply, which directly applies entity configuration to your Gateway instance. We recommend upgrading your decK installation to take advantage of this tool.

You can check your current decK version with deck version.

For this tutorial, you’ll need Kong Gateway entities, like Gateway Services and Routes, pre-configured. These entities are essential for Kong Gateway to function but installing them isn’t the focus of this guide. Follow these steps to pre-configure them:

1. Run the following command:

   echo '
   _format_version: "3.0"
   services:
     - name: example-service
       url: http://httpbin.konghq.com/anything
   routes:
     - name: example-route
       paths:
       - "/anything"
       service:
         name: example-service
   ' | deck gateway apply -
   

   Copied!

To learn more about entities, you can read our entities documentation.

Before you begin, you must get the following credentials from Google Cloud:

• Service Account Key: A JSON key file for a service account with Vertex AI permissions
• Project ID: Your Google Cloud project identifier
• Location ID: The region where your Vertex AI endpoint is deployed (for example, us-central1)
• API Endpoint: The Vertex AI API endpoint URL (typically https://{location}-aiplatform.googleapis.com)

Export these values as environment variables:

export GEMINI_API_KEY="<your_gemini_api_key>"
export GCP_PROJECT_ID="<your-gemini-project-id>"
export GEMINI_LOCATION_ID="<your-gemini-location_id>"
export GEMINI_API_ENDPOINT="<your_gemini_api_endpoint>"

1. Install Claude:

    curl -fsSL https://claude.ai/install.sh | bash
   

   Copied!

2. Create or edit the Claude settings file:

    mkdir -p ~/.claude
    nano ~/.claude/settings.json
   

   Copied!

   Put this exact content in the file:

    {
        "apiKeyHelper": "~/.claude/anthropic_key.sh"
    }
   

   Copied!

3. Create the API key helper script:

    nano ~/.claude/anthropic_key.sh
   

   Copied!

   Inside, put a dummy API key:

    echo "x"
   

   Copied!

4. Make the script executable:

    chmod +x ~/.claude/anthropic_key.sh
   

   Copied!

5. Verify it works by running the script:

    ~/.claude/anthropic_key.sh
   

   Copied!

   You should see only your API key printed.