AI Providers for Unity - Beka Forge

AI Providers AI Providers is a standalone Unity package for developers who want LLM connectivity without rebuilding provider infrastructure in every tool. It gives you reusable provider assets, local API-key handling, editor setup, and request transport in one focused layer. That makes it especially useful for editor utilities, production pipelines, internal tools, and optional runtime features where you want flexibility across providers without turning connectivity code into its own project. Support and updates: Bekaforge | Discord What makes it valuable - Gives you one reusable provider layer instead of rewriting setup, auth handling, and transport code for every new tool. - Supports hosted APIs, OpenAI-compatible services, local Ollama workflows, and custom JSON-style integrations. - Keeps provider definitions reusable and easier to organize across multiple Unity tools and experiments. Core workflow - Create or duplicate provider assets, set local credentials, test the connection in the editor, and reuse the same provider definitions across projects. - Use the blocking request path for editor utilities and the coroutine-based request path for runtime-safe flows with timeout and retry support. - Store API keys locally instead of inside provider assets, which is cleaner for shared tools and version-controlled repositories. Best fit - Unity developers building editor windows, automation helpers, workflow tools, or internal content pipelines. - Teams that want one consistent provider layer for several AI-enabled utilities instead of maintaining separate integrations. - Projects that need optional LLM connectivity without adopting a heavy all-in-one framework. Practical positioning - This package is not trying to be a full consumer-facing generation suite on its own. - Its strength is being a clean reusable provider and transport layer that higher-level Unity tools can build on. - That is exactly what makes it attractive for teams that care about extensibility, maintainability, and reuse. A strong fit for Unity developers who want a reusable LLM integration foundation instead of rebuilding provider assets, local settings, and request code every time.