Hey,
that’s awesome! :) Will check it soon.
You're welcome. :)
Saw that you added loads, nice!! :)
I'm fixing a bug with the text output path at the moment, as well as adding an input for API registration URL + making it easier for users to select languages and api key etc when clicking apply. Please let me know if there is anything in the process you'd like to change!
Thank you very much,
Yeah, the API registration URL is a solid idea.
The Description box has a character limit, so I couldn't put in all the info I wanted for some APIs. Plus, I hit a limit while uploading, so I couldn't finish adding everything.
I'm not sure if this is the way to go, but it would be awesome if every important thing had its own URL and Description for the setup. Like, we need it for the API Key, Models, and Pricing/Limits. The model section would be for when a preset is just for the site in general—like my Cloudflare one—instead of a specific model. If it's already for a specific model like Gemini 2.5 Flash-lite, then we don't need that section. This might even keep the info more up-to-date so people don't always have to dig through the guide. Or would that be overcomplicating it? Just an idea! :)
*Edit
I totally blew it. I wasn't looking and missed the %api_key% part and the %source%, %target%, so I just put "YOUR API KEY" instead. Sorry, I'll get those fixed.
*Edit 2
Maybe we could add %region% to the Request header and something like %country_code% to the API URL? Some presets like Azure Translate actually require it.
URL: "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&to=hu"
H: "Ocp-Apim-Subscription-Region": "westeurope"
https://api.cloudflare.com/client/v4/accounts/CLOUDFLARE_ACCOUNT_ID/ai/run/@cf/deepseek-ai/deepseek-r1-distill-qwen-32b. It would be great if we had a placeholder for that as well.Ah! I'll make sure to increase the character limit. Might increase the upload limit too, it's just there to avoid abuse and ensure users' safety as much as possible.
Hmm. I do agree that each section ought to have its own description and URLs.. Just trying to think of a good way to implement this so it doesn't look more overwhelming than actually just having one single description and allowing the preset creator to just create links directly in that one description. Otherwise we'll end up with a lot of input boxes on the same page.
Could you elaborate on the models? Not sure I fully understood what you meant. :-(
No worries about the %% placeholders, I noticed, I just forgot to let you know haha. Thanks!
Ahh, yes! Have you found any other edge cases of placeholders being needed? I'm thinking that there may be many, in which case I believe I should add optional generic placeholders like %placeholder_1%, %placeholder_2% or similar to alleviate the issue instead of adding edge case upon edge case.
Thank you for the suggestions, very helpful! :)
No problem, makes sense.
About the model URL thing—I meant that I have presets like Gemini 2.5 Flash that are made for that specific model, so you're good to go. But I also have presets where I just made a general template instead of making a million versions for every model, like with OpenRouter. The OpenRouter preset has a model in it, but if users want to change it, they gotta go find another one on their site. Since models change all the time and I was too lazy to make one for every single variation :(, I just went with a basic template.
Yeah, sorry about that—it’s so tiny and the color is so close to the app's theme that I totally missed it. Or maybe it just slipped my mind. Happens to me sometimes! :)
Nope, I think that’s it for what we have right now, but I’ll let you know if I find more. :)
Thank you! This app is just getting better and better. :)
*Edit
Since uploading is working again, I got as much up there as I could. I added Gemini 2.5 Flash and that OpenRouter one I mentioned. Azure is also included, where we'd need the language code in the API URL and the region in the headers.
Ah okay, got it!
I went ahead and implemented a way to add custom placeholders in your presets, which will mostly solve the differentiating model issue, as well as regions etcetera.
I'm refraining from adding a new section for api key/models/limits etcetera at the moment. I feel like it should be possible to get most of that information nicely input into the description now that users can click on links & select text from it, and directly paste that into the placeholder input.
I did just get an idea though - it would be cool for the user who creates the preset to be able to 'tag' the model name in the description, which then could be clicked on to automatically be added to a custom %model% placeholder that the user created. Or maybe even making it so that if you tag a line of text in the description, it will show up as a selectable dropdown option connected to the placeholder input.. Not sure if I'm making myself understandable here lol, I'm sleep deprived.
Cheers for the feedback, I'll take a look at making that text more legible. (I really need to get a higher resolution screen..)
Thank you very much for adding these. Please let me know if you find any bugs with the placeholders, but it should work fine afaik.