惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Jina AI
Jina AI
博客园 - 司徒正美
大猫的无限游戏
大猫的无限游戏
博客园 - 三生石上(FineUI控件)
J
Java Code Geeks
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
爱范儿
爱范儿
美团技术团队
腾讯CDC
博客园 - Franky
MyScale Blog
MyScale Blog
人人都是产品经理
人人都是产品经理
罗磊的独立博客
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
aimingoo的专栏
aimingoo的专栏
博客园_首页
V
V2EX
Martin Fowler
Martin Fowler
T
The Blog of Author Tim Ferriss

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Overcoming LLM Limitations
shashank ms · 2026-06-17 · via DEV Community

I recently shipped a small research agent that beats three recurring LLM problems: stale training data, hallucinated facts, and arithmetic errors. Instead of hoping the model memorized everything correctly, I gave it tools to look up facts and verify math, then cite sources before answering. In this tutorial I will walk you through the exact code so you can run it against Oxlo.ai today.

What you'll need

Python 3.10 or newer, the OpenAI SDK, and an Oxlo.ai API key from https://portal.oxlo.ai. Install the SDK with pip:

pip install openai

Step 1: Set up the Oxlo.ai client and tool definitions

I start by instantiating the OpenAI SDK against Oxlo.ai and declaring the two tools the agent can call. Oxlo.ai exposes function calling through the standard chat completions endpoint, so the schema is identical to what you already know.

from openai import OpenAI

client = OpenAI(base_url="https://api.oxlo.ai/v1", api_key="YOUR_OXLO_API_KEY")

TOOLS = [
    {
        "type": "function",
        "function": {
            "name": "search",
            "description": "Search the local knowledge base for a topic.",
            "parameters": {
                "type": "object",
                "properties": {
                    "query": {"type": "string", "description": "Topic to look up."}
                },
                "required": ["query"]
            }
        }
    },
    {
        "type": "function",
        "function": {
            "name": "calculator",
            "description": "Evaluate a mathematical expression safely.",
            "parameters": {
                "type": "object",
                "properties": {
                    "expression": {"type": "string", "description": "Math expression using +, -, *, /, and parentheses."}
                },
                "required": ["expression"]
            }
        }
    }
]

Step 2: Write the system prompt

The system prompt is the contract. It forces the model to use tools before answering and to cite every claim with a source label. I keep it strict because the whole point is to stop hallucinations.

SYSTEM_PROMPT = """You are a grounded research assistant. Your job is to answer user questions accurately.

Rules:
1. If the question involves facts, dates, or named entities, call the 'search' tool first.
2. If the question involves arithmetic, call the 'calculator' tool first.
3. Only answer after you have tool results. Cite sources like [Source: search].
4. If the tools return nothing, say you do not know. Do not guess."""

Step 3: Implement the tool executor

Next I write the actual tool implementations. I use a tiny in-memory knowledge base so the script is fully runnable without signing up for extra APIs. The calculator locks down the allowed character set so eval stays safe.

import json
import re

KNOWLEDGE_BASE = {
    "oxlo.ai pricing": "Oxlo.ai uses flat per-request pricing. One API call costs the same regardless of prompt length, which makes it cheaper than token-based providers for long-context workloads.",
    "oxlo.ai models": "Oxlo.ai hosts 45+ models including Llama 3.3 70B, DeepSeek R1 671B, Qwen 3 32B, and Kimi K2.6.",
    "moon landing": "The first crewed moon landing was Apollo 11 on July 20, 1969."
}

def search(query: str) -> str:
    q = query.lower()
    for key, value in KNOWLEDGE_BASE.items():
        if key in q or q in key:
            return value
    return "No relevant information found."

def calculator(expression: str) -> str:
    if not re.fullmatch(r"[\d\s\.\+\-\*/\(\)]+", expression):
        return "Error: invalid characters in expression."
    try:
        result = eval(expression, {"__builtins__": {}}, {})
        return str(result)
    except Exception as e:
        return f"Error: {e}"

def dispatch_tool(name: str, arguments: str) -> str:
    args = json.loads(arguments)
    if name == "search":
        return search(args["query"])
    if name == "calculator":
        return calculator(args["expression"])
    return "Unknown tool."

Step 4: Build the agent loop

This is the core loop. I send the conversation to Llama 3.3 70B on Oxlo.ai with tools enabled. If the model requests tool calls, I execute them locally, append the results, and send the updated conversation back for the final answer.

def ask_agent(user_message: str) -> str:
    messages = [
        {"role": "system", "content": SYSTEM_PROMPT},
        {"role": "user", "content": user_message},
    ]

    while True:
        response = client.chat.completions.create(
            model="llama-3.3-70b",
            messages=messages,
            tools=TOOLS,
            tool_choice="auto",
        )

        msg = response.choices[0].message

        if msg.tool_calls:
            messages.append({
                "role": "assistant",
                "content": msg.content or "",
                "tool_calls": [
                    {
                        "id": tc.id,
                        "type": tc.type,
                        "function": {
                            "name": tc.function.name,
                            "arguments": tc.function.arguments,
                        },
                    } for tc in msg.tool_calls
                ],
            })

            for tc in msg.tool_calls:
                result = dispatch_tool(tc.function.name, tc.function.arguments)
                messages.append({
                    "role": "tool",
                    "tool_call_id": tc.id,
                    "content": result,
                })
        else:
            return msg.content

Step 5: Cache search results to cut latency

Repeated lookups waste time. An LRU cache on the search function cuts redundant work and keeps the agent snappy, which is especially helpful when you are iterating quickly against a per-request pricing model.

from functools import lru_cache

@lru_cache(maxsize=128)
def cached_search(query: str) -> str:
    return search(query)

def dispatch_tool(name: str, arguments: str) -> str:
    args = json.loads(arguments)
    if name == "search":
        return cached_search(args["query"])
    if name == "calculator":
        return calculator(args["expression"])
    return "Unknown tool."

Run it

Here is the entry point. I ask a question that requires both a fact lookup and a hypothetical calculation so you can see both tools fire.

if __name__ == "__main__":
    question = (
        "How much would 1000 API requests cost on Oxlo.ai per day if each request is flat priced? "
        "Also, what models are available?"
    )
    answer = ask_agent(question)
    print(answer)

Example output:

Based on the search results:

- Oxlo.ai uses flat per-request pricing. One API call costs the same regardless of prompt length, which makes it cheaper than token-based providers for long-context workloads. [Source: search]
- Oxlo.ai hosts 45+ models including Llama 3.3 70B, DeepSeek R1 671B, Qwen 3 32B, and Kimi K2.6. [Source: search]

For 1000 API requests per day, you would pay 1000 times the flat per-request rate. Because Oxlo.ai does not use token-based billing, the total is predictable and does not scale with input length.

Wrap-up and next steps

That is the entire agent. By offloading facts and math to deterministic tools, you eliminate the most common failure modes of raw LLM outputs. Because Oxlo.ai charges a flat rate per request, you can feed long tool results back into context without watching token meters run up, which makes this pattern cheap to operate at scale.

Two concrete next steps. First, swap the in-memory KNOWLEDGE_BASE for a real vector database like Qdrant so the agent can search your own documents. Second, add Pydantic validation to the tool arguments so malformed calls fail fast before they hit your logic.