clearer documentation on accessing web UI and chatgpt-api

5ac6b6a717f0156aeadac56232de2a1d12363989 · 2024-07-24 14:27:37 -0700 · Alex Cheema

Files touched

M README.md

Diff

commit 5ac6b6a717f0156aeadac56232de2a1d12363989
Author: Alex Cheema <alexcheema123@gmail.com>
Date:   Wed Jul 24 14:27:37 2024 -0700

    clearer documentation on accessing web UI and chatgpt-api
---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0aa0885c..334e9bfc 100644
--- a/README.md
+++ b/README.md
@@ -109,7 +109,9 @@ That's it! No configuration required - exo will automatically discover the other
 
 The native way to access models running on exo is using the exo library with peer handles. See how in [this example for Llama 3](examples/llama3_distributed.py).
 
-exo also starts a ChatGPT-compatible API endpoint on http://localhost:8000. Note: this is currently only supported by tail nodes (i.e. nodes selected to be at the end of the ring topology). Example request:
+exo starts a ChatGPT-like WebUI (powered by [tinygrad tinychat](https://github.com/tinygrad/tinygrad/tree/master/examples/tinychat)) on http://localhost:8000
+
+For developers, exo also starts a ChatGPT-compatible API endpoint on http://localhost:8000/v1/chat/completions. Example with curl:
 
 ```sh
 curl http://localhost:8000/v1/chat/completions \

← 9a373c2b make configurable discovery timeout · back to Exo · styling for tinychat model selector 94201257 →