Provider preset proposal: Ace Data Cloud in administrator endpoint setup

[acedatacloud-dev]

User-visible provider setup without hand-writing YAML

LibreChat users can currently add Ace Data Cloud as a custom OpenAI-compatible endpoint, but every operator must know the endpoint URL and fields. We would like to contribute an operator-selectable provider preset for the existing admin configuration form: choosing Ace Data Cloud fills its display name, logo, https://api.acedata.cloud/v1, apiKey: user_provided, model discovery and automatic-title-off defaults. The operator still decides whether to enable it; users then see Ace in their normal model selector and enter their own key. This does not enable a provider, spend credits, or share an administrator credential without operator choice.

The implementation should use a small data-driven preset list alongside existing generic custom-endpoint fields, rather than a new protocol client or a fork of chat inference. We would target the admin panel creation dialog/schema integration and cover preset-to-draft mapping, preserving edits, disabled/empty states and personal-key behavior. It would not modify billing, routing, fallback, agent permissions or the provider credentials of existing deployments.

We have separately submitted the allowed official configuration collection entry: LibreChat-AI/librechat-config-yaml#94 . That opt-in collection is not claimed as a default provider integration. Five existing media services are being packaged via Agent Plugins; they are separate from this model-provider proposal.

Before opening a core feature PR, please confirm whether a provider preset catalog belongs in LibreChat-AI/admin-panel, in the main shared configuration schema, or should remain only in the official config collection. Ace Data Cloud Dev would like to take the bounded implementation if maintainers approve and assign it. We have read the contribution requirement for prior feature discussion and issue assignment, and will not open an unsolicited core feature patch while that decision is pending.

This is a technical integration proposal. No sponsorship, preferred ranking, default network request, credential grant, or paid generation is requested.

[acedatacloud-dev]

Published implementation update (2026-10-19): the separate media integration source is now merged and has a public v0.1.0 release: https://github.com/AceDataCloud/LibreChatPlugins/releases/tag/v0.1.0 . It contains five independently installable Agent Plugins, not a mandatory combined pack. We downloaded all five public assets and SHA256SUMS and verified single-plugin roots, hashes, licenses and complete bilingual onboarding; native parser and package/install tests pass. No paid model/media requests were issued.

The official service guide PR LibreChat-AI/docs#837 now references those released artifacts. Operator-installed packages and this official configuration collection contribution LibreChat-AI/librechat-config-yaml#94 remain explicitly separate from the requested provider preset. No claim of global marketplace discovery or default Ace provider is made. Real LibreChat OAuth/UI/tool-call evidence is still pending.

We will continue to follow the feature-approval/assignment process for the provider preset and will not open an unsolicited core patch while the preferred implementation location is undecided.