Skip to content

About

Ace Data Cloud model Pipe and service Tools for Open WebUI

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

18 Commits

Folders and files

Repository files navigation

Ace Data Cloud for Open WebUI

Connect Ace Data Cloud chat models with Open WebUI's native OpenAI-compatible Connection, then install only the service Tools your users need. Each of the 17 Tools is a separate Python file and can be imported independently. An optional Pipe Function offers a personal model key for each user. Current-source import, ordinary-user permissions, native model discovery and an existing-task Tool lookup passed on Open WebUI v0.12.0-slim; the browser screenshots and paid first-call examples below are from the earlier v0.11.4 test. See the acceptance boundaries.

简体中文教程 · Service actions and API permissions · Current models and pricing

Publication status (2026-10-19): source PR #1 is merged. The v0.1.1 GitHub release provides separate Python files, import JSON, per-service ZIPs and a SHA-256 manifest; follow the download/import guide. Open WebUI Community posts remain unverified. A source merge or GitHub download is not a Community listing; verify each published post's author and exact source before Get.

Find a service independently

Users usually search for a service name. The proposed Community titles therefore start with Suno, Seedance, Happy Horse, GPT Image, or Nano Banana, followed by by Ace Data Cloud. These are Ace integrations, not official plugins from those services' creators. Each installs as one Tool file; you do not need to import the other services or run a Pipelines server. As of 2026-10-18, no verified Community post/Get URL is available for these entries, so the official install step remains pending.

Search for Separate walkthrough 中文教程 Source
Suno, music, lyrics Suno Suno 中文 One Tool
Seedance, video Seedance Seedance 中文 One Tool
HappyHorse, Happy Horse, video Happy Horse Happy Horse 中文 One Tool
GPT Image, image editing GPT Image GPT Image 中文 One Tool
Nano Banana, image editing Nano Banana Nano Banana 中文 One Tool

The walkthroughs include official publication status, the exact Tool, registration/General Application, copy/create Key screenshots, per-user Key placement, a single intended submit, same-ID retrieval, usage and troubleshooting. Per-entry publication drafts and source hashes are ready for the existing Ace account's manual duplicate check and Share flow. Suggested tags and categories must be confirmed in the actual website form; they are not proof of indexing or search rank. Older screenshots below retain the earlier Ace-first names.

1. Start Open WebUI and review the source

If you already run Open WebUI v0.11.4 or later, continue to step 2. For a local first run, this copyable command contains no Ace Data Cloud key:

docker run -d --name open-webui -p 127.0.0.1:3000:8080 \
  -e WEBUI_SECRET_KEY="$(openssl rand -hex 32)" \
  -e ENABLE_VALVE_ENCRYPTION=true \
  -v open-webui:/app/backend/data \
  ghcr.io/open-webui/open-webui:v0.11.4

Open http://localhost:3000 and create the first account, which becomes the administrator. This command starts one local container; for a long-lived deployment, keep WEBUI_SECRET_KEY in your secret manager and reuse it if you replace the container. Changing it makes encrypted Valve values unreadable. The server needs HTTPS access to api.acedata.cloud. Review every Python file before importing it; Open WebUI executes Functions and Tools inside its server process.

2. Get the right Ace Data Cloud key

  1. Sign in at Ace Data Cloud → Applications.
  2. Open General Application. Copy its API key with the copy icon (1) or choose Manage Keys (2) to create a separate Open WebUI key. A service-specific key works only for that service.
  3. Check your service access, current price and balance. If you enable Allowed APIs for a restricted key, include every endpoint the chosen Connection, Pipe or Tool calls. The service table names them. A shared administrator Connection and each user's Tool Valve may use different keys.

Copy the API key from General Application

Paste the token string only. Do not include Bearer or quotation marks. A platform management token beginning with platform- is not the application API key expected here. Do not paste a key into chat text, a prompt, a workflow export, or a GitHub issue.

3. Connect chat models with the native Connection

This is Open WebUI's recommended route for an OpenAI-compatible provider. Ace Data Cloud already provides /v1/models and /v1/chat/completions, so a Pipe is not needed for ordinary model access.

As an Open WebUI administrator, open Admin Panel → Settings → Connections → OpenAI API, add a connection, and enter:

Field Value
API Base URL https://api.acedata.cloud/v1
API Key Your Ace Data Cloud application API key, entered privately in the admin UI

Save and Verify Connection. The base URL must end in /v1; Open WebUI appends /models and /chat/completions. A restricted key needs both /v1/models and /v1/chat/completions. In Admin Panel → Settings → Models, grant the intended users or group Read access to the chosen models. Select a model returned by your account's live model list; model availability and price can change. For a small chat check, send Reply with the single word OK. and confirm the reply is OK.

The administrator's Connection key is shared by everyone authorized to use those models. Keep that key in the server configuration and restrict model access to the intended users. Service Tools below use their own per-user keys and billable switches. If each chat user must bring a separate Ace Data Cloud key, use the optional Pipe in step 4. Open WebUI's experimental direct per-user Connections have different browser storage and CORS requirements; they are not the same deployment path.

4. Optional: install the personal-key model Pipe

As an Open WebUI administrator:

  1. Open Admin Panel → Functions → Import From Link. Import functions/acedatacloud_pipe.py from its GitHub file URL, review the code, and save it as acedatacloud_models.
  2. Turn the Pipe Active. Its admin Valves contain MODEL_IDS, initially gpt-5.6-luna,deepseek-v4.1-flash-1017,deepseek-v4.1-flash,deepseek-v4-flash,deepseek-flash,deepseek-v4-pro,deepseek-v3.2. Keep only public chat model IDs available to your Ace key. The Pipe adds each ID to the model picker; it does not grant users access by itself.
  3. In Admin Panel → Settings → Models, give the intended users or group Read access to each Pipe model (or make each public to signed-in users). In the local test, a regular user saw no Pipe models until both model IDs received read access. Avoid BYPASS_MODEL_ACCESS_CONTROL for this setup.

Installed and active model Pipe in the admin panel

As a regular user, choose Ace Data Cloud/gpt-5.6-luna from the model picker. Open Chat Controls → Valves, switch the first selector from Tools to Functions, select Ace Data Cloud Models, and paste your key into Api Key. The field is masked on screen; the admin should enable Valve encryption at rest as in step 1.

Pipe model appears in the regular user's model picker

Set the personal model key in Chat Controls → Valves → Functions

Send Reply with the single word OK. A successful first chat returns OK. The Pipe sends the selected model ID and messages to https://api.acedata.cloud/v1/chat/completions using your User Valve key. A restricted key needs /v1/chat/completions; the Pipe does not call /v1/models because the administrator controls its short model list. The screenshots in this section show the tested personal-key path.

5. Install one Tool and make a real search

As an administrator, open Workspace → Tools, use the Create menu's Import From Link, and import tools/google_search.py. Review and save it as acedatacloud_google_search. Grant the intended users or group Read access. Granting read access lets them run the Tool; the ability to create or import Tools must remain with trusted administrators. You can repeat this step for any service file in the service table.

17 separate Tools installed in the test workspace

As a regular user:

  1. In a new chat, select a working Ace Data Cloud chat model from the native Connection, or Ace Data Cloud/gpt-5.6-luna if using the optional Pipe. Click the four-diamond Integrations icon next to the composer → Tools. Search for Google Search by Ace Data Cloud. The screenshots show the tested Pipe model.
  2. Click its sliders icon. In User Valves, enter your application key and turn on Allow Billable Calls; click Save. For a restricted key, allow /serp/google.
  3. Toggle this Tool on for the chat and send the exact first-run prompt below. Open WebUI's Native tool-calling mode is the tested default.

Select Google Search independently

Personal key is masked and billable calls are an explicit switch

Use Google Search by Ace Data Cloud exactly once for the official Open WebUI documentation about Tools. Return the first result title and URL; do not make any other search calls.

The tested result contained Tools / Open WebUI and https://docs.openwebui.com/features/extensibility/plugin/tools/. Open View Result from search to inspect the tool output. One matching usage record for the test key had HTTP 200 and deducted 0.009 Credits under that account's discount; check your current price. Turn Allow Billable Calls off when you are finished.

A regular user's real Google Search Tool result

6. Generate one image, then query the same task

Install tools/gpt_image.py as a separate Tool and grant read access. This example uses one gpt-image-2 image at 1024x1024, quality low. Check current pricing and balance first. If your key restricts APIs, allow both /openai/images/generations and /openai/tasks.

In a new chat, enable only GPT Image by Ace Data Cloud under Integrations → Tools. Open its sliders icon, paste your personal key, and turn on Allow Billable Calls. Send:

Call GPT Image by Ace Data Cloud generate_image exactly once with model gpt-image-2, size 1024x1024, quality low, and prompt: A single lime green origami boat on a plain cream background, clean studio photograph, no text. Report the task ID. Do not call generate_image again or poll automatically.

The generation Tool returns a task_id. That is an accepted task, not a completed image. Record the ID and turn Allow Billable Calls off. The actual test submitted exactly one new generation and returned task 7893131f-77d0-4f93-b779-d192a74dd3e8.

One generation call returned a task ID

The lower part of this real capture shows an unsuccessful follow-up: the Tool was no longer attached to that chat, so the model could not call retrieve_task. The submitted task ID remained valid. Re-enable the Tool in a new chat as follows; do not regenerate the image.

Open a new chat, re-enable GPT Image by Ace Data Cloud in Integrations → Tools, and keep billable calls disabled. Use your own task ID in this read-only prompt:

Use the attached GPT Image by Ace Data Cloud retrieve_task function exactly once on task ID <your-task-id>. Report status, success, and the first media URL. This is a read-only lookup. Never generate a new image.

If the status is pending, repeat only retrieve_task with the same ID later. If the model says the tool is unavailable, re-enable the Tool in the chat before asking again. Wait for status: succeeded and success: true, then open the returned image URL. A green chat reply alone does not prove that a media task completed.

The same task completed and returned a media URL

Actual first-run image from the completed task

In Ace Data Cloud Console usage, locate the single generation request and its Credits deduction. For the test above, one matching ApiUsage record had HTTP 200 and deducted 0.099 Credits under that account's discount. This is an observed test charge, not a promised price; consult the current price and your package rate. Task queries did not submit another generation.

Other independent Tools

The service table and Dify comparison list each of the 17 Tool files, its exposed action methods, task-query path, restricted-key Allowed APIs, and the larger Dify action surface. Media Tools default Allow Billable Calls to off. Each exposes a read-only retrieve_task method where the service uses asynchronous tasks. Google Search and Face Transform return results directly. Nano Banana supports explicit nano-banana-2.1 selection for generation or editing; the first-run default remains nano-banana-2-lite until you check its current price. Grok video now defaults to Dify's public grok-imagine-video-1.5-fast:reverse, 6 seconds, 480p. These files cover the named first-run actions, not every advanced Dify action or API catalog variant.

Troubleshooting and security

Symptom Check
Connection model, Pipe model or Tool missing for a regular user Administrator must grant read access to each model and Tool. Import permission is separate. For a Connection, also verify the base URL and /v1/models access.
Tool says key or billable calls missing Fill that Tool's own User Valves; the shared Connection key or optional Pipe key is separate. Turn on the billable switch only for the call you intend.
HTTP 401 / 403 Use an application API key, check expiration, service access, balance and Allowed APIs.
HTTP 400 Check the exact model, action and parameters in the service table.
HTTP 429 Reduce concurrency and wait; do not enable automatic paid retries.
Timeout / HTTP 5xx / missing task ID Inspect request history before resubmitting a billable generation. Do not create a second task just to poll.
pending or empty media list Use retrieve_task on the same ID later.

Tools and Functions execute arbitrary Python inside Open WebUI. Inspect each file before import, restrict Tool creation to trusted administrators, keep your instance updated, and enable ENABLE_VALVE_ENCRYPTION=true with a stable WEBUI_SECRET_KEY. A masked password field alone does not encrypt values in the database. Open WebUI v0.11.4 has optional experimental Tool Permissions → Ask for approval; it is off by default and does not gate automations or channel replies. The per-user billable switch in these Tools stays off by default.

Privacy · Source and development checks · Community submission pack · Report a problem · dev@acedata.cloud

About

Ace Data Cloud model Pipe and service Tools for Open WebUI

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages