DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add a custom media provider to the pipeline with Noobi AI

Wire your own REST image, audio or 3D provider into Noobi AI through its provider store and service.

Credentials. Provider API keys are sealed by Electron safeStorage, so keep test keys out of commits, logs and pull requests.

Who it is forA developer who has a generation API for images, audio or 3D models and wants Noobi AI to call it for game assets.

The problemGame production needs assets, and a team's preferred generation service is not available out of the box.

The outcomeA forked Noobi AI build where your provider is a configured route, with its generated assets passing through the existing asset validation.

What you need first

  • macOS, the current tested and packaged target
  • Node.js 22 LTS and npm
  • A ChatGPT/Codex account
  • An available image route: a configured image provider or Codex ImageGen
  • Godot 4 with exactly matching Web export templates, only for Godot projects

Steps

  1. git clone https://github.com/Innate-Labs/Noobi.ai.git
  2. cd Noobi.ai
  3. npm ci
  4. Read src/main/mediaProviderStore.ts and src/main/mediaGenerationService.ts, then add your provider adapter following the existing REST provider pattern.
  5. npm run typecheck
  6. npm test

Prompt for your agent

In the Noobi.ai repo at <path>, add a REST provider adapter for <provider name> by following src/main/mediaProviderStore.ts and src/main/mediaGenerationService.ts. Expect a passing typecheck and test run; verify that the new route is configurable and that generated assets still pass the existing validation before proposing a pull request.

Caveat. The README names the files to change but does not document the adapter interface, so read the source before writing code and run `npm run smoke:media` only if you accept its provider quota use.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page