kayx23 commented on code in PR #13209: URL: https://github.com/apache/apisix/pull/13209#discussion_r3084915236
########## docs/en/latest/plugins/ai-rate-limiting.md: ########## @@ -147,13 +289,15 @@ If the rate limiting quota of 300 prompt tokens has been consumed in a 30-second The following example demonstrates how you can use `ai-proxy-multi` to configure two models for load balancing, forwarding 80% of the traffic to one instance and 20% to the other. Additionally, use `ai-rate-limiting` to configure token-based rate limiting on the instance that receives 80% of the traffic, such that when the configured quota is fully consumed, the additional traffic will be forwarded to the other instance. -Create a Route which applies rate limiting quota of 100 total tokens in a 30-second window on the `deepseek-instance-1` instance, and update with your LLM providers, models, API keys, and endpoints, if applicable: +Create a Route which applies a rate limiting quota of 100 total tokens in a 30-second window on the `deepseek-instance-1` instance, and update with your LLM providers, models, API keys, and endpoints, if applicable: + +<Tabs groupId="api"> +<TabItem value="admin-api" label="Admin API"> ```shell -curl "http://127.0.0.1:9180/apisix/admin/routes"; -X PUT \ +curl "http://127.0.0.1:9180/apisix/admin/routes/1"; -X PUT \ -H "X-API-KEY: ${admin_key}" \ -d '{ - "id": "ai-rate-limiting-route", Review Comment: Please keep the style of resource creation consistent across plugin docs. Other plugin docs are adopting the style where the ID of the resource is placed in the PUT body, with a meaningful ID. It seems that this writing style is being reverted in this doc. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
