Upstream Original Address:
Don’t let the upstream discover it, otherwise it can still remain stable as long as the upstream doesn’t change the method. We can enjoy it as long as they don’t modify it.
Usage Effect:
I used it non-streaming. Actually, to make it more stable, you should ask the AI to convert it into a Docker project, which can avoid the stability issues caused by CF’s cookie credential.
Online Experience (Does not guarantee stability; for stable long-term use over months, ask the AI to convert it into a Docker project and automatically refresh credentials):
https://liaobots-2api.to2ai.workers.dev/
I have been using hundreds of kilobytes of text input stably:
Open Source Repository:
As long as the upstream doesn’t notice me, I’m fine. I’ve noticed that many manufacturers have started paying attention to me recently, so I’ll try to stay low-key.
To改造的话主要是围绕这个方向来：
- Auto Keep Alive: Use CF Cron Triggers to periodically request and keep the Cookie active.
- Just keep the cookie and related credentials alive, then the stability depends on whether the upstream will shut down this service or not.
