50/50 RevShare Integration: OpenUI & AIML API

Hi! I'm Hugo from aimlapi.com — an AI aggregator that gives access to 1000+ models in one API, trusted by 400k+ users.

We'd love to be available as a verified provider option inside OpenUI — so we went ahead and did all the technical work on our side, in our fork: https://github.com/aimlapi/openui-aimlapi (branch feat/aimlapi-example, rebased cleanly on main).

To build our partnership, we offer a 50/50 revenue share on all traffic from this integration. (P.S.: tracking starts as soon as this release goes live, so no earnings will be lost during setup)

My contacts: [email protected] (email / Slack), Telegram: @hug0the

---

Is your feature request related to a problem? Please describe.

Every example in examples/ points at OpenUI Cloud Completions (https://api.thesys.dev/v1/embed). There is no reference implementation of <AgentInterface /> running against an OpenAI-compatible provider directly, so the two things that change when no Gateway is in the path are not shown anywhere: the openuiLibrary system prompt has to be compiled locally with generateSystemPrompt() instead of cloud: true, and invalid OpenUI Lang is no longer corrected server-side — only the renderer's own recovery is left.

Describe the solution you'd like

An examples/miscellaneous/aimlapi example: the Vercel AI SDK example's client wiring and tools, with createOpenAICompatible({ baseURL: "https://api.aimlapi.com/v1" }) as the provider and the model picked by an AIMLAPI_MODEL env var, so the same app can be pointed at any of the 1,000+ models AI/ML API serves under one key by changing one variable. Listed in examples/README.md and examples/examples.json under miscellaneous.

Describe alternatives you've considered

• Documenting the direct-provider path in the Vercel AI SDK example's README rather than adding an example — that example is about Cloud Completions, and carrying both paths in one route makes it harder to read.
• Putting it under agent-frameworks — the seam here is the model provider, not the agent runtime, so miscellaneous ("backend services that do not justify another top-level category") is the right home.

Additional context

Examples-only, nothing under packages/ changes, so no changeset. Opening this issue first as the contributing guidelines ask — happy to open the PR against main as soon as you confirm the direction.