API Improvements

I'm currently writing a webui for ollama but I find the API quite limited/cumbersome. What is your vision/plan regarding it? Is it in a frozen state, or are you planning to improve it? Here's some criticism: * mixed model/generation endpoints. some namespacing would be nice. * mixed `model`/`name` params that refer to the same thing. * `/api/tags`: why is this named tags? * `GET /api/tags` to get all available local models but `POST /api/show` to get one? * some endpoints throw errors, some return `status` as a JSON property. * No way to query the available public models repository * `POST /api/create`: doesn't allow to specify the `Modelfile` as just raw text, so there's no way to create models without file system access (client-side). Also no way to specify model file using just an object. Also for this to work, `FROM` needs to handle remote resources aswell. * `POST /api/show`: returns a string which forces the client to parse it to get the actual data. It would be nice it it also returned a JSON object. * `POST /api/embeddings`: without batching support is mostly useless * `template` in `Modelfile`: to properly support chat agents it would be nice to have a chat-specific generation endpoint, and to be able to iterate over them in the `template`. otherwise the feature itself is quite limited and requires the client to mostly override and re-implement all the logic (and it also needs to know all the underlying model parameters). (this is how Hugginface does https://huggingface.co/HuggingFaceH4/zephyr-7b-beta/blob/main/tokenizer_config.json#L34) Example: define `Modelfile` `template` : ``` {{range .Messages}} <|{{ .Role }}|> {{ .Content }} </s> {{end}} ``` instead of: ``` {{- if .System }} <|system|> {{ .System }} </s> {{- end }} <|user|> {{ .Prompt }} </s> <|assistant|> ``` and then passing the messages as a JSON array to `POST /api/chat/generate` ``` …