AGKit vs OpenRouter
Choose AGKit when you want models connected to actions inside your app, with routes, credentials, and spending controls managed in Cloud.
OpenRouter routes model requests and provides a management API for creating, rotating, and limiting keys.
 AGKit | OpenRouter | |
|---|---|---|
| Application stack | Swift, Android, React Native, and Web; one Cloud backbone | API integration across client and server stacks |
| Application actions | Agent runtime, tool contracts, permission hooks, and cancellation | Application tools are implemented by the integrator |
| Configuration | Cloud-managed model tiers, credentials, and agent profiles | Model routing and provider selection |
| Production controls | End-user identity, project/user budgets, and configured attestation | Programmatic keys, credit limits, and usage controls |
| Application responsibility | Tool implementation, state validation, approvals, and actual undo | Integrate application identity, state, and recovery |
Choose your platform and access path for SDK availability and setup. Guard and confirmation support depends on the SDK execution path you integrate.
Where OpenRouter fits
You want to select from multiple model providers while keeping your existing application runtime. Its routing options and per-key credit limits give your team controls to build around.
Where AGKit fits
You want to connect models to application tools and operate that experience through Cloud. App code expresses a tier; Cloud owns the model binding, profile, credentials, and spending controls.
What your team implements
With either approach, your application implements the actions and validates changes to its state. AGKit adds the runtime lifecycle; your app still decides what needs approval and how a change is reversed.