When we ask Google Gemini: what is the time in Singapore for Thursday, February 29th, 2024 9:00am (UTC-08:00) Pacific Time?
, it will returns:
There seems to be a mistake. February 29th, 2024 doesn't exist. February only has 28 days in non-leap years.
Would you like to try a different date?
Obviously, 2024 is a leap year.
Let's build a serverless function to calculate the timezone for a specific time to get rid of LLM hallucinate. This tool can be integrated with OpenAI, Gemini, Ollama, and other LLMs.
curl -fsSL https://get.yomo.run | sh
Detail usages of the cli can be found on Doc: YoMo CLI.
yomo serve -c ./yomo.yml
the configuration file yomo.yml
is as below:
name: generic-llm-bridge
host: 0.0.0.0
port: 9000
bridge:
ai:
server:
addr: 0.0.0.0:9000
provider: openai
providers:
openai:
api_key: <SK-XXXXX>
model: <gpt-4o>
YoMo support multiple LLM providers, like Ollama, Mistral, Llama, Azure OpenAI, Cloudflare AI Gateway, etc. You can choose the one you want to use, details can be found on Doc: LLM Providers and Doc: Configuration.
yomo run app.go
Test in your terminal:
curl http://127.0.0.1:9000/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-4o",
"messages": [
{
"role": "user",
"content": "what is the time in Singapore for February 28th, 2024 9:00am (UTC-08:00) Pacific Time?"
}
]
}'
You will get response like:
{
"id": "chatcmpl-9tXZYje8ppe0vPAYYeIyrGsRMfkbQ",
"object": "chat.completion",
"created": 1723024120,
"model": "gpt-4o-2024-05-13",
"choices": [
{
"index": 0,
"message": {
"role": "assistant",
"content": "February 29th, 2024 at 9:00 AM Pacific Time (UTC-08:00) is equivalent to March 1st, 2024 at 1:00 AM in Singapore Time (UTC+08:00)."
},
"finish_reason": "stop"
}
],
"usage": {
"prompt_tokens": 360,
"completion_tokens": 108,
"total_tokens": 468
},
"system_fingerprint": "fp_c9aa9c0491"
}
Check Docs: Self Hosting for details on how to deploy YoMo LLM Bridge and Function Calling Serverless on your own infrastructure. Furthermore, if your AI agents become popular with users all over the world, you may consider deploying in multiple regions to improve LLM response speed. Check Docs: Geo-distributed System for instructions on making your AI applications more reliable and faster.
We know data is precious for every company, but managing multiple data regions is a big challenge. Vivgrid.com is a geo-distributed platform that routes user requests to the nearest LLM Bridge service. You can benefit from it to reduce latency and improve user experience while keeping your Function Calling Serverless deployed within your own infrastructure, even in your private cloud. Details can be found in Docs: How to keep data security in LLM Function Calling.
Accelerating your LLM tools will improve user experience and increase user engagement. If LLM response speed is your top priority, you can consider deploying your LLM Bridge service on Vivgrid. Your function calling serverless will be deployed on every continent. Check Docs: Deploy LLM function calling serverless on Vivgrid for more details.
yc deploy app.go
yc logs
For more about cli yc
usage, please check Docs: Vivgrid CLI.