Iron Meet existing tools where they are
Connect compatible developer tools and existing agents through a familiar OpenAI-style base URL instead of requiring an immediate rebuild.
Proxy KeysBring the AI tools your team already uses
Bring the AI tools your team already uses
onto a governed path.
Connect Cursor, Cline, other OpenAI-compatible tools, and compatible agents your organization already runs to Iron Gorilla’s LLM Proxy. Issue named keys, see who owns them, and revoke access when work changes—without rebuilding the client first.
How it works
Start governing model traffic before every tool has been rebuilt.
Add Iron Gorilla as an OpenAI-compatible provider, create a named key, and update the client with the supplied base URL and one-time secret. Requests then use the organization’s enabled models, routing rules, approvals, and trace path through the LLM Proxy.
Product Walkthrough
Connect one developer tool, then review and revoke its access.
Create a named key, copy the one-time secret, configure an OpenAI-compatible client, review ownership, and follow the resulting request evidence.
Know who owns the access
Give each key a useful name and keep its status, creator, owner, and organization binding visible.
End access when the work changes
Create a replacement when needed, update the client, and revoke the old key on your team’s schedule.
Why it matters
What this changes once the work gets real.
The secret appears once
Copy a newly created key when it is issued; the full secret is not displayed again.
Organization routing still applies
Client configuration uses enabled models while provider choice, fallback, approvals, and routing remain organization-level controls.
Requests leave useful evidence
Review provider, model, decision, latency, tokens, and cost in the existing LLM Proxy trace experience.
Bring existing AI development onto a path your organization can review.
Connect compatible tools now, keep ownership visible, and move deeper into Iron Gorilla on your own schedule.