Migrate from Portkey

Portkey was acquired by Palo Alto Networks in April 2026 (~$130M). The roadmap is now tied to Prisma AIRS, PAN’s AI security platform. If you need a gateway with an independent roadmap and managed runner support, this guide walks you through the move.

Migration time: 10–20 minutes. The base URL format is similar enough that existing SDK code changes are minimal.

Environment variable mapping

Portkey env var	Curate-Me equivalent	Notes
`PORTKEY_API_KEY`	`CM_API_KEY` (`cm_sk_...`)	Format changes; same role
`PORTKEY_GATEWAY_URL`	`OPENAI_BASE_URL=https://api.curate-me.ai/v1/openai`	Per-provider path
`OPENAI_API_KEY` (virtual key)	Store in Secrets → `OPENAI_API_KEY=cm_sk_...`	Provider key stored server-side
`PORTKEY_VIRTUAL_KEY`	—	Replaced by Curate-Me stored secrets
`PORTKEY_CONFIG`	—	CM governance is per-org in the dashboard
`PORTKEY_TRACE_ID`	Automatic via `X-CM-Trace-Id` header	No code change needed

Before / after code diff

Python


-from portkey_ai import Portkey
-
-client = Portkey(
-    api_key="PORTKEY_API_KEY",
-    virtual_key="PORTKEY_VIRTUAL_KEY",
-)
-response = client.chat.completions.create(
-    messages=[{"role": "user", "content": "Hello"}],
-    model="gpt-4o",
-)
+from openai import OpenAI
+
+client = OpenAI(
+    base_url="https://api.curate-me.ai/v1/openai",
+    api_key="cm_sk_your_gateway_key",
+)
+response = client.chat.completions.create(
+    messages=[{"role": "user", "content": "Hello"}],
+    model="gpt-4o",
+)
print(response.choices[0].message.content)

With Portkey’s config header (if you use custom configs):


-headers = portkey.createHeaders(
-    api_key="PORTKEY_API_KEY",
-    config="pp-config-xxx",
-)
-client = OpenAI(api_key="OPENAI_API_KEY", default_headers=headers)
+# CM governance config is set in the dashboard — no per-request header needed
+client = OpenAI(
+    base_url="https://api.curate-me.ai/v1/openai",
+    api_key="cm_sk_your_gateway_key",
+)

TypeScript


-import Portkey from 'portkey-ai';
-
-const portkey = new Portkey({
-  apiKey: process.env.PORTKEY_API_KEY,
-  virtualKey: process.env.PORTKEY_VIRTUAL_KEY,
-});
-const response = await portkey.chat.completions.create({
-  messages: [{ role: 'user', content: 'Hello' }],
-  model: 'gpt-4o',
-});
+import OpenAI from 'openai';
+
+const client = new OpenAI({
+  apiKey: process.env.CM_API_KEY,   // cm_sk_...
+  baseURL: 'https://api.curate-me.ai/v1/openai',
+});
+const response = await client.chat.completions.create({
+  messages: [{ role: 'user', content: 'Hello' }],
+  model: 'gpt-4o',
+});
console.log(response.choices[0].message.content);

curl


-curl https://api.portkey.ai/v1/chat/completions \
-  -H "x-portkey-api-key: $PORTKEY_API_KEY" \
-  -H "x-portkey-virtual-key: $PORTKEY_VIRTUAL_KEY" \
-  -H "Content-Type: application/json" \
-  -d '{"model":"gpt-4o","messages":[{"role":"user","content":"Hello"}]}'
+curl https://api.curate-me.ai/v1/openai/chat/completions \
+  -H "X-CM-API-Key: $CM_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"model":"gpt-4o","messages":[{"role":"user","content":"Hello"}]}'

Step-by-step migration

Create a Curate-Me account and get your gateway key

Import your Portkey virtual keys

The curate CLI can read a Portkey virtual key export and print the equivalent CM secret-store commands:


# Export your virtual keys from the Portkey dashboard first, then:
curate import-portkey-config portkey-virtual-keys.json

Output example:


# Curate-Me equivalent of your Portkey virtual keys
# Review and run these commands to set up provider secrets:
 
curl -X POST https://api.curate-me.ai/v1/admin/secrets \
  -H "X-CM-API-Key: $CM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider": "openai", "secret": "sk-your-openai-key", "label": "migrated-from-portkey"}'
 
curl -X POST https://api.curate-me.ai/v1/admin/secrets \
  -H "X-CM-API-Key: $CM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider": "anthropic", "secret": "sk-ant-your-key", "label": "migrated-from-portkey"}'
 
export CM_API_KEY=cm_sk_your_gateway_key
export OPENAI_BASE_URL=https://api.curate-me.ai/v1/openai

The CLI helper is a print-only stub — it prints commands but does not mutate any state. Review and run the output manually.

Migrate Portkey Configs to CM governance policies

Portkey’s “Config” objects map to Curate-Me governance policies:

Portkey Config feature	Curate-Me equivalent
`strategy: fallback`	Provider failover (roadmap)
`strategy: loadbalance`	Multi-key load balancing (roadmap)
`cache: {mode: simple}`	Response caching (roadmap)
`retry: {attempts: 3}`	SDK-side retry via `RetryPolicy` in the Python SDK
`budget.total_budget`	Per-org daily budget in Costs → Budgets
`metadata.user`	Per-request metadata via `X-CM-User-Id` header

Set a daily budget


curl -X POST https://api.curate-me.ai/v1/admin/budgets \
  -H "X-CM-API-Key: cm_sk_your_gateway_key" \
  -H "Content-Type: application/json" \
  -d '{"daily_limit_usd": 50.0, "scope": "org"}'

Update your environment variables


# Remove Portkey vars
unset PORTKEY_API_KEY
unset PORTKEY_VIRTUAL_KEY
unset PORTKEY_GATEWAY_URL
 
# Add Curate-Me vars
export CM_API_KEY=cm_sk_your_gateway_key
export OPENAI_BASE_URL=https://api.curate-me.ai/v1/openai
export OPENAI_API_KEY=cm_sk_your_gateway_key

Verify your first request


curl https://api.curate-me.ai/v1/openai/chat/completions \
  -H "X-CM-API-Key: $CM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o",
    "messages": [{"role": "user", "content": "Migration test — what year is it?"}]
  }'

Check Dashboard → Traces for the new request trace with X-CM-Request-Id.

Portkey feature equivalents

Portkey feature	Curate-Me equivalent
Virtual keys	Stored secrets (Settings → Provider Secrets)
Configs / routing strategies	Governance policies (dashboard per-org)
Prompt playground	Dashboard → Playground
Prompt library	Coming soon
Logging (Portkey logs)	Traces dashboard (full request/response)
Semantic caching	Roadmap
Provider fallback	Roadmap
Observability (Portkey analytics)	Dashboard → Costs + Traces
Guardrails add-on	Built-in PII scanning + content safety (no add-on)

Rollback

If you need to revert:


# Restore Portkey env vars
export PORTKEY_API_KEY=your-old-portkey-key
export PORTKEY_VIRTUAL_KEY=your-virtual-key
unset OPENAI_BASE_URL  # or restore to https://api.portkey.ai/v1
unset CM_API_KEY

Your provider secrets remain stored in Curate-Me and can be deleted via DELETE /v1/admin/secrets/{id} if you want a clean break.