base on Keep your WARP+ traffic topped up with Cloudflare Workers. # warpflare  Keep your WARP+ traffic topped up with Cloudflare Workers. This project is inspired by [WARP-CLASH](https://github.com/vvbbnn00/WARP-Clash-API). > **Warning** > > This project is entirely non-commercial and is intended solely for educational > and communicative purposes. Please do not use it for illegal activities, as > the consequences will be borne by the user. > > This project is exclusively for advanced users with programming skills and is not recommended for beginners. ## Requirement - A Cloudflare account is required. ## Instructions To get started, follow these steps: 1. **Fork** this project by [](https://deploy.workers.cloudflare.com/?url=https://github.com/yuchanns/warpflare). 2. Add **three** required secrets to `Settings > Security > Secrets and variables > Actions > Repository Secrets > New repository secrets`: - `CLOUDFLARE_ACCOUNT_ID`: Find your account ID using the [instructions here](https://developers.cloudflare.com/fundamentals/setup/find-account-and-zone-ids/). - `CLOUDFLARE_API_TOKEN`: Create this token with the `Edit Cloudflare Workers` template and permission of `D1 Edit` included. See image below for reference:  - `SECRET_KEY`: Choose any value for authorizing access to the subscription URL. 3. Go to `Actions > Deploy` and manually run the workflow by clicking `Run workflow`. The firs deploy might be failed, please retry. 4. Find the route for your worker in your Cloudflare dashboard under `Workers & Pages`. 5. Assuming the route is `warp.xxx.workers.dev`, you can access the subscription using: - `https://warp.xxx.workers.dev/sub?token=${SECRET_KEY}&proxyFormat=full&randomName=true&best=true`: detect the subscription type based on user-agent. - `https://warp.xxx.workers.dev/api/:subType?token=${SECRET_KEY}&proxyFormat=full&randomName=true&best=true`: manually specify the subscription type to use. The available parameters are shown in the table below: |Name|Options|Description| |---|---|---| |subType|clash, quantumult, v2ray, shadowrocket, sing-box|**PR**s are welcome| |proxyFormat|only_proxies, with_groups, full|only for clash| You can control the worker behavior using the following environment variables (**not** secrets): |Name|Default|Description| |---|---|---| |LOSS_THRESHOLD|10|Packet loss rate (percentage)| |DELAY_THRESHOLD|500|Delay threshold (ms)| |RANDOM_COUNT|The number of nodes|10| |GET_DATA_INTERVAL|2|Interval for replenishing `WARP+` traffic (min)| |SAVE_ACCOUNT_INTERVAL|10|Interval for dropping accounts (min)| |RESET_ACCOUNT_INTERVAL|2880|Interval for resetting accounts (min)| **Why do I need to reset the account?** If you replenish your traffic excessively using an account, Cloudflare will reject your request and you will receive an error 426 which represents that you have sent too many requests. Simply proxying your requests will not solve the issue as the limitation is account-specific. Therefore, you need to reset your account. After resetting your account, please refresh your subscription to obtain the updated private key. ## Optimization Even though default IPs are embedded, you may encounter varying levels of loss and delay based on your location. To enhance your overall experience, it is essential to optimize your IP. To get started, clone this project and turn off all the proxies on your local network. Make sure to have a node environment and pnpm installed. Install project dependencies for the first time using `pnpm install`. Next, navigate to the project path and run the following command: ```bash pnpm optimize ``` This will upload a sql to your worker to obtain optimized IPs. Once the subscription is refreshed, a set of optimized nodes will be distributed. ## Roadmap - [ ] Telegram bot ", Assign "at most 3 tags" to the expected json: {"id":"10094","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"