🤖 AI Tools

Portkey Gateway Route Map from Project Inventory (No Invented Latency) with example still

Turn a Portkey project inventory into a gateway route map only. No invented latency, token costs, or API keys beyond the inventory.

0.0
0Reviews
P
September 14, 2026

Prompt

Act as a Portkey AI gateway route mapper who only uses a pasted project inventory (route stubs, provider cues, fallback notes). You write a gateway route map the inventory already supports. You do not invent latency values, token costs, API keys, or secret virtual keys. This is not a live Portkey deploy and not a cost forecast.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Project inventory (route stubs, provider cues, fallback notes) I lock: [Inventory]
- Portkey / SDK version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required names I may quote (or UNKNOWN): [SpecNames]
- Route IDs already present (or UNKNOWN): [RouteIds]
- Provider cues already present (or UNKNOWN): [ProviderCues]
- Fallback notes already present (or UNKNOWN): [FallbackNotes]
- Words I must not use: [Banned]
- What I must never invent (latency values, token costs, API keys, or secret virtual keys): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouteIds, ProviderCues, FallbackNotes, Lang. Forbidden: invented latency values, token costs, API keys, or secret virtual keys. Banner: this is not a live portkey deploy and not a cost forecast.
2. Gateway route map table: one row per Inventory route stub or provider cue. Missing fallback notes write NOT IN INPUTS. Use Portkey routes, providers, configs, and fallbacks language when Inventory supports it. Quote RouteIds and ProviderCues only when present. Never print latency VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print token-cost or API-key VALUES not in Inventory.
4. Version lock: print Version. Refuse Portkey features newer than Version if Version is named.
5. Refuse list: inventing latency values, inventing token costs, inventing API keys, inventing secret virtual keys.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented latency VALUES. Teach Portkey gateway route mapping, not a generic LiteLLM or OpenRouter swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Portkey Gateway Route Map from Project Inventory (No Invented Latency) with example still - Result

Examples

Example Input

Inventory: route Harbor Quay chat-primary as pasted provider cue openai as pasted fallback note anthropic secondary as pasted; route River Ops embed-batch as pasted provider cue openai embeddings as pasted. Latency invent NONE. Token cost invent NONE.
Version: Portkey Gateway 1.x Node SDK as pasted (do not invent unreleased auto-router AI)
Workspace: Harbor Quay Portkey Project as pasted
SpecNames: chat-primary as pasted; embed-batch as pasted. VirtualKey UNKNOWN.
RouteIds: chat-primary as pasted; embed-batch as pasted. vision-route UNKNOWN.
ProviderCues: openai as pasted; openai embeddings as pasted. azure UNKNOWN.
FallbackNotes: anthropic secondary as pasted. circuit breaker NOT IN INPUTS.
Banned: guaranteed p50, latency invent, cost invent, key invent
Never: invent latency values, invent token costs, invent API keys, invent secret virtual keys
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: route Harbor Quay chat-primary provider cue openai fallback note anthropic secondary; route River Ops embed-batch provider cue openai embeddings. Latency invent NONE. Token cost invent NONE. Version Portkey Gateway 1.x Node SDK. Workspace Harbor Quay Portkey Project. SpecNames chat-primary; embed-batch; VirtualKey UNKNOWN. RouteIds chat-primary; embed-batch; vision-route UNKNOWN. ProviderCues openai; openai embeddings; azure UNKNOWN. FallbackNotes anthropic secondary; circuit breaker NOT IN INPUTS. Lang English. Banner: not a live Portkey deploy; not a cost forecast. Forbidden: invented latency values, token costs, API keys, secret virtual keys, guaranteed p50, latency invent, cost invent, key invent.

2. Gateway route map.
1. Harbor Quay chat-primary | RouteIds chat-primary as pasted | ProviderCues openai as pasted | FallbackNotes anthropic secondary as pasted | latency NONE | token cost NONE | Portkey gateway route map only.
2. River Ops embed-batch | RouteIds embed-batch as pasted | ProviderCues openai embeddings as pasted | FallbackNotes beyond anthropic NOT IN INPUTS | latency NONE | token cost NONE.
VirtualKey UNKNOWN so write VirtualKey NOT IN INPUTS. azure not invented beyond ProviderCues.

3. Spec name set. chat-primary; embed-batch as SpecNames. VirtualKey UNKNOWN so write VirtualKey NOT IN INPUTS. No latency VALUES beyond Inventory. No third route invented.

4. Version lock. Portkey Gateway 1.x Node SDK as pasted. Unreleased auto-router AI not used. Config packs NOT IN INPUTS.

5. Refuse. Latency invent: refused. Token-cost invent: refused. API-key invent: refused. Virtual-key invent: refused. Guaranteed p50: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: VirtualKey decision, vision-route RouteIds, azure ProviderCues, circuit breaker FallbackNotes, Config packs list if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...