Custom EndPoint | CyberSEO Pro | Support Forum

Thanks for your suggestion - it's a great idea, and we do plan to implement support for custom OpenAI compliant API endpoints.

The main challenge is figuring out the best way to integrate this feature in a way that's seamless for users - both in the plugin settings and within shortcodes - while maintaining backwards compatibility with the current setup.

If you have any specific thoughts or ideas about how you'd like to see this implemented in the UI or shortcode structure, feel free to share them. Your input would be very helpful in designing the most intuitive and flexible solution.

Thanks for your detailed message and ideas, and you're absolutely right that the ability to use custom OpenAI-compatible endpoints would be a powerful feature. However, the challenge here is not the actual query logic - that's the easy part.

What really requires thoughtful planning is the UI and how to seamlessly integrate this feature into various parts of the plugin: shortcode generation, feed configuration UI, automated translation, rewriting, and more.

For example, simply adding two fields (API endpoint and key) may seem sufficient at first, but then questions immediately arise:

• How would you choose between multiple custom endpoints?
• How would this integrate with AI-driven features outside of shortcodes, such as translation or rewriting?
• How do we avoid breaking compatibility for existing users?

That's exactly why we're taking our time to get the interface right, so that it's intuitive, flexible, and future-proof.

Regarding your comment about the AI model selection in the "AI Engine generation" tab. This is an example of an outdated UI, the result of poor architectural decisions made earlier in the plugin's evolution. Unfortunately, many users still rely on it, so we can't remove it without disrupting their workflow. So we strongly recommend using shortcodes in the HTML post template instead. These give you full control over the AI model and all of its parameters. For example, the [or_text] shortcode for OpenRouter allows you to use any supported model - there are no restrictions.

However, the kind of advanced logic you're aiming for (like assigning numeric values like "veridicity: 8" as tags or metadata) is best handled through custom PHP snippets using the plugin's built-in API functions.

Since we understand that not every user is a developer - and that's why we suggest the Login to see this link. It's an AI assistant that is familiar with the plugin and can generate the PHP snippets you need based on your exact requirements.

In practice, implementing support for custom endpoints requires a much more thorough approach than just adding a couple of fields and generating dynamic shortcodes. We are already working on implementing this as conveniently, logically and without risk of breaking the current architecture.

Most likely a fixed shortcode with parameters like id, endpoint and model will be used rather than a dynamic shortcode name. This approach provides flexibility, scalability and compatibility with the rest of the plugin. Support for advanced UI customizations for custom endpoints is also planned.