From 020a66c01fbfc383f1c81bc232cc0e8987a9a1d1 Mon Sep 17 00:00:00 2001 From: Krrish Dholakia Date: Wed, 12 Nov 2025 13:44:38 -0800 Subject: [PATCH] docs(model_access_guide.md): explain how model access works on litellm --- docs/my-website/docs/proxy/model_access_guide.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/my-website/docs/proxy/model_access_guide.md b/docs/my-website/docs/proxy/model_access_guide.md index 1c4e5a56bec..4eb273facba 100644 --- a/docs/my-website/docs/proxy/model_access_guide.md +++ b/docs/my-website/docs/proxy/model_access_guide.md @@ -18,6 +18,17 @@ model_list: In here, we onboard a model deployment for the model `gpt-4o` and assign it to the model group `my-custom-model`. +## Client-side request + +Here's what a client-side request looks like: + +```bash +curl --location 'http://localhost:4000/chat/completions' \ +-H 'Authorization: Bearer ' \ +-H 'Content-Type: application/json' \ +-d '{"model": "my-custom-model", "messages": [{"role": "user", "content": "Hello, how are you?"}]}' + +``` ## Access Control When you give access to a key/user/team, you are giving them access to a "model group".