Skip to content

add origin_power_ai plugin v1.0.0 (author: origin-power-ai) - #3078

Merged
crazywoola merged 1 commit into
langgenius:mainfrom
origin-power-ai:add-origin_power_ai-v1.0.0
Sep 14, 2026
Merged

add origin_power_ai plugin v1.0.0 (author: origin-power-ai)#3078
crazywoola merged 1 commit into
langgenius:mainfrom
origin-power-ai:add-origin_power_ai-v1.0.0

Conversation

@Ikki6666

@Ikki6666 Ikki6666 commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

Adds the Origin Power AI model provider plugin under our organization handle. This is the same plugin as the currently listed ikki6666/origin_power_ai v0.0.5 (Verified by Dify), submitted under the org handle as a new listing — see Reviewer notes.

  • Origin Power AI is a unified OpenAI-compatible gateway that aggregates GLM, MiniMax and other mainstream models behind a single API key
  • 5 predefined models (glm-5.3-flash / glm-5-turbo / glm-4.7 / glm-5.3 / glm-5.2) with context size, vision and tool-call capabilities
  • Customizable-model support so users can add any model served by their OpenAI-compatible endpoint
  • Streaming, tool calling, reasoning-content wrapping and usage-based token accounting (based on the official openai_api_compatible plugin, Apache-2.0)
  • PRIVACY.md bundled; manifest repo, contact and meta.minimum_dify_version fields set
  • Version starts at 1.0.0 because this is a new author directory with no prior versions

Risk level

  • Low risk
  • Medium risk
  • High risk

The plugin forwards user prompts and conversation context to the API endpoint configured by the workspace administrator (an arbitrary user-supplied URL) via plain HTTP requests. No other external calls; nothing is sent to the plugin author. Identical risk profile to the already-listed v0.0.5.

Required checks

  • I have read and followed the Marketplace submission requirements.
  • I have read and comply with the Plugin Developer Agreement.
  • I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
  • The package contains only files needed at runtime.
  • The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
  • The package does not contain executables or bundled binaries, or I explained why they are required below.
  • The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
  • The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
  • All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

The plugin makes network requests only to the model gateway endpoint configured by the workspace administrator when setting up the provider. This is the arbitrary-URL capability detected by the scanner: requests.get in provider/origin_power_ai.py (credential validation via GET /models, no token spend) and requests.post in models/llm/llm.py (OpenAI-compatible /chat/completions calls). Requests carry only the conversation data required to call the LLM API and are authenticated with the API key entered by the administrator. The plugin does not call any other service, does not send data to the plugin author, and does not persist data locally.

Local validation

  • Packaged with the Dify Plugin CLI (v0.6.10):

    dify plugin package ./ -o origin_power_ai-1.0.0.difypkg
  • Verified the package contents: 24 files, .git/ excluded, .env excluded, no virtual environments, no bundled binaries. The file list is identical to the currently listed ikki6666/origin_power_ai v0.0.5 package — only manifest.yaml differs (author and version).

  • Verified the in-package manifest: author: origin-power-ai, version: 1.0.0, repo pointing at the org repository, privacy: ./PRIVACY.md.

  • Installed and ran the plugin against a self-hosted Dify 1.17.0 instance through the plugin daemon remote-debug channel: provider credentials were validated with GET /v1/models, and a real end-to-end chat invocation (streaming) passed.

Reviewer notes

  • This PR supersedes the existing ikki6666/origin_power_ai listing. Per langgenius/dify-plugins#3066, listing ownership cannot be transferred, so this is submitted as a new listing under our organization handle. The plugin name is unchanged (origin_power_ai), so the Plugin ID becomes origin-power-ai/origin_power_ai.
  • The old listing should be marked deprecated with a redirect to the new one, as confirmed by @crazywoola in [Plugin Ops] Transfer marketplace listing ownership to an organization? #3066. We are not publishing any further version under the old author directory.
  • The source repository moved from Ikki6666/origin-power-ai (301-redirects) to origin-power-ai/dify-plugin-origin-power-ai.
  • Test limitation: validated on self-hosted Dify 1.17.0 (Community Edition) only; not separately validated on Dify Cloud.
  • Heads-up for users: Dify does not migrate plugin identity, so existing users must uninstall the old plugin and install this one, re-entering their provider credentials.
  • close [Plugin Ops] Transfer marketplace listing ownership to an organization? #3066

@crazywoola
crazywoola merged commit 1268b5a into langgenius:main Sep 14, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium Medium-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Plugin Ops] Transfer marketplace listing ownership to an organization?

2 participants