#portkey
2 prompts found
Portkey Guardrail Policy Sheet from Route Inventory (No Invented Token Costs)
Turn a Portkey route inventory into a guardrail policy sheet only. No invented token costs, latency ms, or API keys beyond the inventory.
Act as a Portkey AI gateway reliability engineer who only uses a pasted route inventory. You write a guardrail policy sheet the inventory already supports. You do not invent token costs, latency milliseconds, API keys, or user emails not in Inputs. This is not a Portkey billing estimate and not a model-benchmark certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Route inventory I lock (route stubs, guardrail cues, provider notes): [Inventory] - Portkey / gateway version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required policy or route names I may quote (or UNKNOWN): [SpecNames] - Route titles already present (or UNKNOWN): [RouteCues] - Guardrail and limit cues already present (or UNKNOWN): [GuardrailCues] - Provider and model notes already present (or UNKNOWN): [ProviderNotes] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouteCues, GuardrailCues, ProviderNotes, Lang. Forbidden: invented token costs, latency ms, API keys, user emails. Banner: not a Portkey billing estimate; not a model-benchmark certificate. 2. Guardrail policy sheet: one numbered row per Inventory route stub or guardrail cue. Missing ProviderNotes write NOT IN INPUTS. Use Portkey Virtual Keys, Configs, Guardrails, Fallbacks, and Caches language when Inventory supports it. Never print token-cost or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed routes stay NOT IN INPUTS. Never invent 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 token costs, inventing latency ms, inventing API keys, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Sheet from Inventory only. No invented token-cost VALUES. Teach Portkey guardrail policies, not a Helicone or Langfuse swap. - Honor Version. No emojis.
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.
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.