
Argent with Portkey
Already route AI traffic through Portkey? Keep it. Argent adds the agent and the person behind each call, your approved models, redaction, budgets and a signed record.
What Argent does with Portkey
Portkey routes and manages model traffic. Argent governs it: who is calling, what they may send and what it costs.
- Built in: Portkey's connection settings ship with Argent, so agents reach it through Argent by changing their base URL and key.
- Agent and owner on every call: each request is tied to a registered agent and its human owner.
- Approved models: the model in each request is checked against your approved list and access rules before it reaches Portkey.
- Sensitive data: redacted before the request leaves your network.
- Budgets and record: every call priced, held against a budget and signed.
How it connects
Agents point at Argent, and Argent forwards to your Portkey.
- Add Portkey as an endpoint on the AI Providers page. Its key goes to your vault and Argent keeps only the reference.
- Register each agent with an owner and give it its Argent key.
- Point agents at Argent. Their base URL becomes the gateway route; Argent attaches the Portkey key on the way out.
Your vault can be HashiCorp Vault or OpenBao, AWS Secrets Manager, CyberArk Conjur or Infisical.
What you configure
Everything below is set once in the Argent console and applies to every agent that calls Portkey through the gateway.
| Setting | Where | What it does |
|---|---|---|
| Approved models | Policy > Model and endpoint access | Default deny: a call is allowed only when the model is on the approved list. The list is platform AND tenant AND agent, and each layer can only narrow the one above. |
| Access rules | Same page | Allow or deny by provider, route type, model, hosted tools, function tools and output type, for the tenant, a department, a person or one agent. The narrowest rule wins, and a 7-day impact preview shows what a draft would change. |
| Sensitive data | DLP | Per entity type: redact and record, record only, or block the request. |
| Budgets and caps | Budgets | Budgets for the company, org, department, person and agent. Each request is priced and held against the budget before it leaves, and an emergency cap stops a runaway agent now. |
| Mode | Per control | Off, watch or enforce. Watch records what would have been refused and changes nothing on the wire. |
Start in watch, read what would have been refused, then switch on enforce. See Watch Before You Enforce.
What the record shows
Every Portkey call leaves one signed record, allowed or refused.
- One row per call: the agent and the person who owns it, the tenant, the model, the decision and the policy that made it, latency, and the cost, token and cache figures.
- Tamper-evident: each row is hash-chained to the one before and signed with an ed25519 key held in Vault Transit, so an edited or missing row shows.
- Real cost: cost comes from the usage block in Portkey's own reply, priced from your price book in USD per million tokens.
- No unpriced spend: an agent under a budget that calls a model with no price is refused, so a new model cannot slip past a cap.
Conversations can be opened and replayed from the record. See Session Replay and One-Click Audit Evidence.
Related capabilities and goals
Where to go next.
- Capabilities: Model Control, Sensitive Data Redaction, AI Spend Caps, Keyless Agents.
- Goals: Model control and routing, Budget and token spend, See all AI in your company.
- Works with: Portkey, Kong AI Gateway, Cloudflare AI Gateway, OpenAI.
- Everything else Argent connects to: All integrations.
Download files
- PDFArgent Model Control data sheetApproved models, Model Swap, model classes and failover. One page.
- PDFArgent Keyless Agents data sheetProvider keys stay in your vault; agents carry only their own Argent key. One page.
- PDFArgent Sensitive Data Redaction data sheetPersonal data and secrets found and redacted before a prompt leaves. One page.
Want this running on your own use cases?
All downloads