Integration llamaindex
Give LlamaIndex the web without giving up your privacy.
Cited answers, clean Markdown, matching JSON, and browser tasks for LlamaIndex.TS, as native LlamaIndex tools.
@tabstack/llamaindex
ollama.com/blog
docs.openwebui.com
ANSWER
Two runtimes shipped it.
Why LlamaIndex
Tabstack, inside LlamaIndex.
@tabstack/llamaindex adds Tabstack to LlamaIndex.TS as native agent tools. Pass the array to an agent and it gets cited research, clean page content, matching JSON, and browser tasks.
post /research
query: "which runtimes…"
mode: "balanced"First call
Start with a current question.
LlamaIndex makes the call, and Tabstack handles the web. Research searches live sources, reads the pages, and returns a cited answer, so your agent gets the findings without running every search itself.
npm install @tabstack/llamaindex llamaindex zod
export TABSTACK_API_KEY="your-key-here"
import { tabstackTools } from "@tabstack/llamaindex";
import { agent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";
import { Settings } from "llamaindex";
Settings.llm = openai({ model: "gpt-4o" });
const researcher = agent({ tools: tabstackTools });
const result = await researcher.run(
"What are Vercel's current pricing plans? Cite your sources.",
);
console.log(result.data);
Tools
Five tools, one key.
Each Tabstack endpoint is a tool in tabstackTools. Pass the whole array, or import the ones a run should reach.
| Tool | Returns |
|---|---|
research_question | A cited answer from multiple live sources |
extract_page_content | A page as clean Markdown |
extract_structured_data | JSON matching a schema you define |
generate_structured_data | A page transformed into the JSON you describe |
automate_browser_task | A completed browser task, from plain-language steps |