Hey all! I just published onyx-text-plugin β€” a drop-in-style alternative to ai-text-plugin that runs on the free FreeAIXYZ gateway. No API key, no account, no quota.

πŸ”— https://perchance.org/onyx-text-plugin

What it does

Same call style as ai-text-plugin: instruction, startWith, stopSequences, onChunk/onFinish, outputTo, String-like result with .text / .generatedText / .stop() 24 free models across 8 families (general, coding, reasoning, creative, 18+), with model: "auto" capability-based picking Tool calling: calculator, web search, and clock, with an automatic Up-to-10-round agent loop Real token-by-token SSE streaming, reasoning traces (Logos models), structured error codes Special calls: getMetaObject, listModels (live catalog), executeTool, preload Use it in your generator like this:

freeAI = {import:onyx-text-plugin}
let reply = await root.freeAI({
  instruction: "You are Bob, a gruff blacksmith.\n" + chatLog,
  startWith: "Bob:",
  stopSequences: ["\nUser:"],
  model: "onyx-codex",
  tools: "builtin",
  onChunk: (d) => { replyEl.textContent = d.fullTextSoFar; },
});

The generator page itself is full interactive docs + a live playground (model picker, tool toggles, reasoning fold, API reference, error table) β€” so you can try everything before importing.

Two honest caveats: stop sequences aren't re-included like ai-text-plugin does, and there's deliberately no vision support β€” I live-tested the gateway's vision slots and they hallucinated instead of seeing images, so images throw a clear error instead of faking it.

Feedback and bug reports welcome! If you build something with it, drop a link β€” I'd love to see it.

[–] [S] 2 points 1 month ago

Yeah, that makes sense. The API-key risk is definitely something worth being careful about, especially if the generator can be shared publicly and someone could accidentally leave their key in it.

The time-limit idea could help, but I agree that removing the API key before publishing is probably the safest approach. The CC license is also really nice since people can build on it and improve it while still giving you credit.

And no worries about the time it takes-real life comes first. I appreciate you working on this at all, and I’ll definitely keep an eye out for it whenever you get it into a usable state. Good luck with the bugs and security side of it!

  • source
  • parent
  • context
  • [–] [S] 2 points 1 month ago (2 children)

    Yeah, that actually sounds pretty cool. I can see why the security part would be a pain though, especially with making sure people don’t accidentally expose their API keys when sharing generators.

    Even if the workflow is a bit clunky with having to copy/paste into a new generator, I think having the option to use your own OpenAI-compatible API would still be really useful. And yeah, being able to pay for our own model usage would probably help Perchance too.

    No pressure on getting it done quickly though. Better to take your time and get the bugs/security sorted out properly. I’d definitely give it a try when you get it working.

  • source
  • parent
  • context
  •  

    Would it be possible to add an optional custom OpenAI-compatible API configuration to Perchance AI Coder?

    This could be useful for people who prefer a different model or want more control over the AI Coder's behavior, especially given some of the recent concerns about the current AI helper/model.

    Ideally, the settings could include:

    • Model ID β€” a text input where users can enter the model name/ID.
    • Model selection β€” optionally allow selecting from models returned by the configured API.
    • Base URL β€” for example, an OpenAI-compatible endpoint such as "https://example.com/v1".
    • API key β€” optional input for providers that require authentication.
    • Default Perchance model β€” keep the existing model as the default, so this would be completely optional.

    The important part would be supporting OpenAI-compatible APIs, rather than tying the feature to one specific provider. This would let users connect compatible local or third-party endpoints without requiring Perchance to host or provide every model.

    For example, the configuration could look something like:

    API Base URL: https://example.com/v1 Model ID: my-coding-model API Key: ********

    Then AI Coder could send requests using the standard OpenAI-compatible chat/completions interface.

    This could also provide a way for users who prefer an older/different coding model to use their own provider while keeping the normal Perchance experience available for everyone else.

    Would the Perchance devs consider adding something like this?