Routing HTTP path strings...without HTTP?
bit of a weird one, hear me out! i'm working on an application which uses llms + tools to hit some "endpoints" like
for clarity, you can imagine my LLM tool to be defined as:
the issue here is the fetch. there is no reason perform a real fetch request to a real endpoint when the API itself is just a construct for the llm. in reality, it would be much more efficient to:
of couse, we need the
LMK!
/api/v1/posts/api/v1/posts/1234for clarity, you can imagine my LLM tool to be defined as:
the issue here is the fetch. there is no reason perform a real fetch request to a real endpoint when the API itself is just a construct for the llm. in reality, it would be much more efficient to:
of couse, we need the
matchLMK!
Similar Threads
Was this page helpful?
