Shakespeare — provider lockdown (BYOK)
Shakespeare is strictly forbidden from using any provider owned by Meta, OpenAI, or xAI. Its bring-your-own-key picker could be pointed at OpenAI or xAI — so Shakespeare is allowed in the catalog only under this binding recipe, which locks the picker to permitted providers and machine-verifies that the excluded ones are unreachable. This is enforcement of the exclusion, not an exemption from it.
Configure (≈2 minutes)
Section titled “Configure (≈2 minutes)”-
Open Shakespeare at shakespeare.diy.
-
Go to Settings → AI Provider.
-
Choose a permitted provider — one of: Anthropic, DeepSeek, Kimi (Moonshot), OpenRouter, OpenCode Zen, PayPerQ, or local Ollama.
-
Paste your own API key for that provider (BYOK). It’s stored locally in your browser’s IndexedDB — it is not sent to Shakespeare’s servers.
-
Do not select OpenAI or xAI.
Verify (≈5 minutes)
Section titled “Verify (≈5 minutes)”The configuration is only trustworthy if you confirm it. Watch the network while you use the app:
# In the browser devtools Network tab, or via a proxy/inspector,# exercise Shakespeare for ~5 minutes and confirm NO requests to:# api.openai.com# api.x.aiIf you picked Anthropic, you should see traffic to api.anthropic.com and
nothing to any excluded host. If you picked local Ollama, you should see traffic
only to localhost.
Applying the same pattern elsewhere
Section titled “Applying the same pattern elsewhere”Any agent harness you use to build with this catalog — Goose, Claude Code, Aider — should follow the same BYOK discipline: pick a permitted provider, supply your own key, and verify the network. See the quickstart.