Services that call third-party APIs
Last updated: September 11, 2026
Some services on OSC are built to send content to an AI provider. This page lists every one that asks you for an AI provider credential, plus the two of our own features that call a provider on our account, so you can see before you deploy where content would go.
The "Whose API key" column is the important one. Where it says Yours, the service is inert until you supply your own credentials. You decide whether the call happens, the usage bills to your account, and you rather than Eyevinn are the exporter for that transfer. Where it says Ours, Eyevinn makes the call on its own account and the transfer sits in our sub-processor register.
OSC never sends your content to an AI provider on an Eyevinn key, except through the two platform features named below. Everywhere else, an AI call happens only because you supplied the credential for it.
Catalogue services, on your own API key
These are open source projects we publish in the catalogue. Each one is designed to call the provider named below, and each needs your own API key before it will do so. Two are worth reading the documentation for before you deploy them, because the content that leaves is not only yours: Subtitle Generator uploads the audio from the media you give it, and S3 Sync Vectorstore uploads the documents you sync, which may be documents your own users provided.
For Claude Runner and Codex Runner the credential is technically optional only because each accepts one of two alternative sign-in methods. Neither runs without one of the pair. Encore Profile Server is the one genuine exception on this list: it works without a key, and Claude powers a single endpoint.
| Service | Provider that receives the content | Whose API key | Documentation |
|---|---|---|---|
| Subtitle Generatoreyevinn-auto-subtitles | OpenAI | Yours | Read more |
| S3 Sync Vectorstoreeyevinn-s3-sync-vectorstore | OpenAI | Yours | Read more |
| OpenAI Assistantboldare-openai-assistant | OpenAI | Yours | Read more |
| AI Code Reviewereyevinn-ai-code-reviewer | OpenAI | Yours | Read more |
| Image Description Generatoreyevinn-img-alt-gen | OpenAI | Yours | Read more |
| Codex Runnerbirme-codex-runner | OpenAI | Yours | Read more |
| Ephemeral Token Serviceeyevinn-ephtoken-svc | OpenAI (Realtime API) | Yours | Read more |
| Claude Runnerbirme-claude-runner | Anthropic | Yours | Read more |
| Open Buildereyevinn-open-builder | Anthropic | Yours | Read more |
| Claude Code Slack Botmpociot-claude-code-slack-bot | Anthropic | Yours | Read more |
| Encore Profile Servergrusell-encore-profile-server | Anthropic | Yours | Read more |
| movierecommendatoralexbj75-movierecommendator | OpenAI and Anthropic | Yours | Read more |
Platform features, on your API key
These are ours rather than catalogue services, but they run on a credential you supply, so the same reasoning applies as for the catalogue above. Both send the code or content you point them at to the provider you configured.
Platform features, on our API key
These are ours rather than catalogue services, so Eyevinn is the exporter and the transfer sits inside our sub-processor register with Standard Contractual Clauses, a data processing agreement, a 7-day retention limit and pseudonymized user identifiers. Note that ask-osc-architect is available to any connected MCP client and needs no separate activation, so it is not something you switch on.
| Service | Provider that receives the content | Whose API key | Documentation |
|---|---|---|---|
| OSC AI assistant (web console)platform feature | OpenAI and Anthropic | Ours | See the register |
| ask-osc-architect (MCP tool)platform feature | OpenAI and Anthropic | Ours | See the register |
What this page does not tell you
This list is built by reading the configuration schema of every service in the catalogue and finding the ones that ask you for an AI provider credential. That is a precise test, and it has a limit: it cannot see a key baked into an image, a key you enter later through a service's own interface, or a provider that needs no key. So read it as the services that ask you for an AI credential, not as the only software that could ever reach a model.
We also make no claim about what the other services in the catalogue do on the network. They are independent open source projects, many of them exist precisely to talk to something outside OSC, such as object storage, mail relays, payment providers or your own git host, and we have not audited all of them. Check the documentation and the source of anything you deploy.
Three services we could not classify without deploying them: Supergateway, which connects to whatever MCP server you point it at and can carry credentials in free-form environment variables; Dynamic OG, which describes itself as AI-powered but exposes no provider credential; and Flowsint, whose enricher keys are entered at runtime rather than at deploy time.
If you would rather not
Every service in the catalogue is open source, so any of these can be self-hosted and pointed at a provider of your choosing, including one you run yourself. Deploying OSC does not require deploying any service on this page.
The full list of sub-processors we engage, with each one's location and the transfer safeguard we rely on, is at www.osaas.io/subprocessors. How we handle personal data is at www.osaas.io/privacy.
Every service in the catalogue was checked against its configuration schema on 11 September 2026, 188 of 188, no sampling. If you find a service that calls out and is not listed here, please tell us at privacy@eyevinn.se.