// gin

Market data for
Gin apps.

TickerDB Go SDK + Gin. Pre-computed market data in your handlers, no infrastructure.

// setup

Install the SDK.

One dependency. No MCP server, no WebSocket connections — just a Go module that calls the TickerDB HTTP API.

terminal

$ go get github.com/tickerdb/tickerdb-go

// code example

Two handlers, five minutes.

Initialize the client once, call methods from your handlers. Every method returns a struct ready for c.JSON.

package main

import (
    "github.com/gin-gonic/gin"
    tickerdb "github.com/tickerdb/tickerdb-go"
)

func main() {
    client := tickerdb.NewClient("tapi_your_api_key")
    r := gin.Default()

    r.GET("/summary/:ticker", func(c *gin.Context) {
        summary, _ := client.Summary(c.Param("ticker"))
        c.JSON(200, summary)
    })

    r.GET("/events/:ticker", func(c *gin.Context) {
        events, _ := client.GetEvents(c.Param("ticker"), c.Query("field"), c.Query("band"), nil)
        c.JSON(200, events)
    })

    r.Run(":8080")
}

// state changes

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.

r.GET("/watchlist/changes", func(c *gin.Context) {
    changes, _ := client.Watchlist.Changes()
    c.JSON(200, changes)
})

json

{
  "ticker": "AAPL",
  "changes": [
    {
      "field": "rsi_zone",
      "from": "neutral",
      "to": "oversold"
    },
    {
      "field": "trend",
      "from": "uptrend",
      "to": "downtrend"
    }
  ]
}

// ai integration

Feed an AI agent.

TickerDB's categorical output is designed for LLMs. Feed a summary directly into a prompt — the model already understands terms like "oversold" and "strong_uptrend" without extra context.

r.GET("/briefing/:ticker", func(c *gin.Context) {
    summary, _ := client.Summary(c.Param("ticker"))
    data, _ := json.Marshal(summary)

    message, _ := anthropicClient.Messages.New(context.TODO(),
        anthropic.MessageNewParams{
            Model:     anthropic.ModelClaudeSonnet4_20250514,
            MaxTokens: 1024,
            Messages: []anthropic.MessageParam{
                anthropic.NewUserMessage(
                    anthropic.NewTextBlock(
                        "Analyze this market data and provide a brief:\n" + string(data),
                    ),
                ),
            },
        },
    )

    c.JSON(200, gin.H{"analysis": message.Content})
})

// available methods

What you can call.

Every method returns categorical, pre-computed data as a plain dictionary. No raw data to parse, no indicators to compute.

client.GetSummary(ticker, opts)

Full technical + fundamental snapshot for a single asset.

client.GetWatchlist(opts)

Batch summaries for a portfolio.

client.GetWatchlistChanges(opts)

Field-level diffs for your watchlist since the last pipeline run.

client.AddToWatchlist(tickers)

Add tickers to your persistent watchlist.

client.RemoveFromWatchlist(tickers)

Remove tickers from your watchlist.

client.Search(filters, opts)

Search across all assets with multi-field filters.

client.GetSchema()

Discover all queryable fields and their types.

client.GetAccount()

Your plan tier, rate limits, and current API usage.

client.CreateWebhook(url)

client.ListWebhooks()

List your registered webhook URLs.

client.DeleteWebhook(id)

Remove a registered webhook.

full method reference →

// why tickerdb + gin

Built for how agents 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.

// what your agent sees

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.