Framework compatibility
New integrations should use Keys REST for resolve/catalog and @restormel/keys-elements for UI. Legacy npm adapters are deprecated — see npm → REST migration.
Compatibility at a glance
| Framework | Recommended path | Status |
|---|---|---|
| Any (server) | Keys REST + Gateway key | Supported |
| Next.js / React / SvelteKit / Astro | @restormel/keys-elements | Supported |
| Agents / IDE | @restormel/mcp, @restormel/aaif | Supported |
| Local tooling | @restormel/keys-cli, @restormel/doctor | Supported |
| Vue / Nuxt | Keys REST + Web Components | Supported via elements |
Install paths
Resolve (no npm core):
// Resolve via Keys REST (any language / framework)
const res = await fetch(
`${process.env.RESTORMEL_KEYS_BASE}/keys/v1/projects/${projectId}/resolve`,
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.RESTORMEL_GATEWAY_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ workload: "chat" }),
},
);
const { data } = await res.json();UI (Web Components — all frameworks):
pnpm add @restormel/keys-elementsimport "@restormel/keys-elements";
// In HTML or any framework template:
// <rk-key-manager user-id="u_123"></rk-key-manager>
// <rk-model-selector project-id="…"></rk-model-selector>CLI + doctor:
pnpm add -D @restormel/keys-cliSee also
- Cloud API — Gateway key, Developer Portal, OpenAPI
- Migrate from @restormel/keys npm
- CLI, MCP, AAIF
- Dashboard — projects and provider vault