Portkey MCP. Stop guessing your LLM costs and usage.

Listen up. You run an AI stack; you don't just connect it—you put it through the Portkey gateway first. That’s your central control point for every token spent and every dollar billed across all your models. Forget jumping between OpenAI dashboards, Anthropic consoles, or whatever billing report gives you a headache.

Your agent handles everything here.

Cost Guardrails and Policy Management

You gotta make sure nobody blows the budget, right? You set up guardrails using create_policy to enforce specific usage limits or hard spending caps for entire projects or user groups. If someone starts chewing through tokens too fast, that policy stops them dead in their tracks.

If a project wraps up and those guardrails aren't needed anymore, you use delete_policy to clean up the system. You can review every active budget rule or usage ceiling with list_policies, seeing exactly who’s hit what consumption rate and which projects are affected by current limits.

Tracking Usage and Performance Logs

When things go sideways, you need data, not guesses. The agent pulls a summary of recent AI calls using list_logs. This gives you IDs, timestamps, how many tokens were used, the latency number, and the cost code for every single interaction.

Need to debug one specific failure? You don't waste time sifting through thousands of entries; you just pull deep info on that exact gateway log entry using get_log_details. For compliance or a big-picture review, you generate detailed, filterable log files with export_logs, letting you narrow down activity by date range or model type.

You can also submit user feedback—a simple like or dislike recorded via submit_feedback against any specific response log to track and improve your model quality.

Auditing the System Infrastructure

You gotta know what’s running under the hood, too. To see which LLM models are actually available through your gateway, you run list_models; this tells you if it's chat-enabled or just for embeddings, and what provider handles it.

When you need to audit how requests are being routed—like checking retry rules or fallbacks—you list all active gateway configurations using list_configs. For the money side of things, you check out which virtual API keys are in use via get_virtual_keys, seeing exactly what provider key is running, its limits, and how much it's consumed.

Policy Management Details

To get a complete picture of your system’s financial exposure, the agent also lets you list all defined policies using list_policies. This shows you the name, the current consumption rate against the cap, and which users are tied to that rule. You can manage these rules by setting them up with create_policy or removing them completely with delete_policy.