AIPocket is a Chrome MV3 AI access wallet that lets websites request user-approved model access without receiving your provider API keys.

It keeps provider credentials in the extension, lets websites request scoped permission, and streams approved model output back through the extension.

Demo video: https://www.youtube.com/watch?v=XxX6oH8E-Co

Wallet	Connection approval

Provider management	Demo app

Many AI-powered websites ask users to paste provider API keys directly into the web app. That gives the website long-lived credentials it does not need.

AIPocket moves API keys into a browser extension. Websites receive only scoped, revocable access to approved providers and models.

• Store provider API keys inside the extension.
• Add OpenAI-compatible, Anthropic-compatible, OpenRouter, and Gemini providers.
• Approve website access per origin, provider, model list, and session.
• Enforce optional per-session request limits.
• Stream model output back to websites without exposing provider keys.
• Use @aipocket/connect-modal to integrate with web apps.

npm install
npm run build

Load apps/extension/dist in Chrome:

1. Open chrome://extensions.
2. Enable Developer mode.
3. Click Load unpacked.
4. Select apps/extension/dist.

1. Open the extension popup.
2. Go to Providers.
3. Click Add.
4. Choose OpenAI-compatible, Anthropic-compatible, OpenRouter, or Gemini.
5. Enter provider name and API key.
6. Enter endpoint when the provider type shows an endpoint field.
7. Optionally set Max requests per session.
8. Click Check connection.
9. Click Save provider.

AIPocket uses the aiWallet provider protocol internally for website integrations.

import { connectAiWallet, requestResponseStream } from "@aipocket/connect-modal";

const permission = await connectAiWallet({
  providerId: "provider_openai",
  models: ["gpt-5.5"],
  reason: "This app needs AI access for chat responses"
});

await requestResponseStream({
  sessionId: permission.sessionId,
  providerId: permission.providerId,
  model: permission.models[0],
  input: "1+2=?",
  onDelta(delta) {
    console.log(delta);
  }
});

See docs/integration.md for full integration details.

Live demo: https://dist-red-nine-94.vercel.app

npm run dev -w @aipocket/demo-web

Open the local URL in the same Chrome profile where AIPocket is installed. Connect the demo, approve access in the extension, keep the prompt 1+2=?, and send. Expected output: 3.

Demo video: docs/assets/videos/demo.mov

See docs/local-demo.md for a full walkthrough.

• apps/extension: Chrome MV3 extension.
• apps/demo-web: React demo website.
• packages/connect-modal: website-facing integration helper.
• packages/protocol: shared protocol types and validation helpers.
• docs: architecture, setup, and integration guides.

npm run test
npm run typecheck
npm run build

Websites never receive API keys. The extension validates origin, session, provider, approved model, expiration, and request limit before brokering any upstream request.

Current MVP protections:

• Provider API keys stay in extension storage.
• Websites only receive session metadata and streamed output.
• Sessions are scoped to origin, tab, frame, provider, approved models, and expiration.
• Stream requests are rejected when provider/model/session checks fail.
• Optional request limits are enforced per approved session.

AIPocket is preparing for a public Chrome Web Store v0.1.0 release.

• Improve provider discovery and provider selection UX for websites.
• Add usage visibility and stronger quota controls.
• Harden MV3 stream lifecycle behavior.
• Prepare Chrome Web Store listing assets and review checklist.
• Publish integration packages when protocol stabilizes.

Apache-2.0. See LICENSE.