russellballestrini/russell.ballestrini.net
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

modified: content/2025-03-21-introducing-slop.rst

Browse source
This commit is contained in:
Russell Ballestrini 2025-03-21 14:33:19 -04:00
parent b3bf006d02
commit 735eb44a18
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/2025-03-21-introducing-slop.rst
View file

@ -34,7 +34,7 @@ Ideally a SLOP server will be created in every programming language and placed i
- **/chat**: Talk to AI models.
- **/tools**: Use predefined utilities (e.g., calculator, greeter).
This is where you can call public or private tools or algorythms to work on public or private data and return a result.
This is where you can call public or private tools or algorithm to work on public or private data and return a result.
A tool could be written in ANY programming language & does not need to be written in the same language as your SLOP server.
As long as your code in your slop server knows how to dispatch the process and return a result it may be used in agentic flows!
Yes, this includes that narly ffmpeg bash script you still use sometimes.
@ -44,7 +44,7 @@ Ideally a SLOP server will be created in every programming language and placed i
- **/models**: list of models & types upstream to the SLOP server.
RFC in developemnt could be moved to /info/models (html) or /info/models.[html,xml,json,yaml,etc]
right now I have a Python algorythm that dynamically determines a list of models the upstream SLOP server can provide in my implementation.
right now I have a Python algorithm that dynamically determines a list of models the upstream SLOP server can provide in my implementation.
People have ask for us to also keep track of the type of model, for example embeddings or image or video or various hybrid enums.
Right now it's a simple list returned in JSON.