Market data tools for
the Vercel AI SDK.
Register TickerDB methods as AI SDK tools. Your language model gets access to live market summaries, watchlists, and ticker event history — grounding financial responses in real data.
Install the dependencies.
Add the TickerDB SDK alongside the Vercel AI SDK.
npm install tickerdb ai @ai-sdk/openai Set TICKERDB_KEY in your environment variables. The SDK reads it automatically.
Register tools. Stream responses.
Define TickerDB methods as AI SDK tools with typed parameters. The model calls them automatically when it needs market data.
import { TickerDB } from "tickerdb"; import { tool } from "ai"; import { z } from "zod"; const client = new TickerDB(process.env.TICKERDB_KEY); export const marketTools = { getSummary: tool({ description: "Get a market summary for a ticker", parameters: z.object({ ticker: z.string().describe("Stock ticker symbol"), }), execute: async ({ ticker }) => client.getSummary(ticker), }), getSummaryEvents: tool({ description: "Ticker event history via summary field/band filters", parameters: z.object({ ticker: z.string().describe("Stock ticker symbol"), field: z.string().default("rsi_zone"), band: z.string().default("deep_oversold"), }), execute: async ({ ticker, field, band }) => client.getSummary(ticker, { field, band }), }), };
import { openai } from "@ai-sdk/openai"; import { streamText } from "ai"; import { marketTools } from "@/lib/market-tools"; export async function POST(req) { const { messages } = await req.json(); const result = streamText({ model: openai("gpt-4o"), messages, tools: marketTools, }); return result.toDataStreamResponse(); }
Multi-step analysis.
Your model can chain tool calls — get a full summary, use summary event mode for historical context, then pull another ticker for comparison. Each call returns categorical data the model understands without extra prompting.
Track state changes effortlessly.
Most market data APIs return point-in-time snapshots. TickerDB tracks state transitions — your agent sees what changed, not just what is.
{ "ticker": "AAPL", "changes": [ { "field": "rsi_zone", "from": "neutral", "to": "oversold" }, { "field": "trend", "from": "uptrend", "to": "downtrend" } ] }
What your agent sees.
Every tool returns categorical facts — not raw OHLCV data. Your agent can branch on "oversold" without needing to know what RSI > 70 means.
{ "ticker": "NVDA", "trend": "strong_uptrend", "momentum": { "rsi_zone": "overbought", "macd_signal": "bullish" }, "volatility": "high", "fundamentals": { "pe_zone": "above_historical_avg", "earnings_surprise": "positive" } }
What you can call.
Every tool returns categorical, pre-computed data. Your agent gets facts it can reason about immediately.
Full categorical snapshot for a single asset — trend, momentum, volatility, volume, extremes, fundamentals, support/resistance.
Live summary data for all tickers in your saved watchlist.
Field-level diffs for your watchlist since the last pipeline run.
Add tickers to your persistent watchlist.
Remove tickers from your watchlist.
Multi-field filtering across all assets. Build complex queries with arbitrary filter combinations.
All queryable fields with types, values, and descriptions. Always free.
Your plan tier, rate limits, and current API usage.
Register a webhook URL for watchlist change notifications.
List your registered webhook URLs.
Remove a registered webhook.
Built for how models consume data.
Categorical data, less prompt engineering
Responses like "rsi_zone": "oversold" are already in a format the model understands. No need to explain what RSI > 70 means.
Compact responses
Tool-call context windows are limited. TickerDB responses are a fraction of the tokens you'd need to pass raw OHLCV data.
Pre-computed daily
No infrastructure to maintain. No cron jobs, no indicator math, no data pipelines. TickerDB handles computation and syncing.