Data Visualization

Minara turns your natural-language prompts into tables, spreadsheets, charts, and annotated K-lines. This mode is designed for quick market reads, wallet comparisons, and portfolio breakdowns on supported chains/assets.

When to use

• Compare token performance over time

• See holder/whale distributions

• Break down a portfolio by asset/chain

• Track a wallet’s activity and holdings

• Turn Deep Research outputs into visuals

What you get

• A structured table/spreadsheet as the source of truth

• Up to 5 preferred charts (Line, Bar/Column, Pie, K-line with annotations) chosen per request

• Visuals that match your prompt intent (rankings, trends, composition)

Quick start

1. Switch to Data Visualization mode.

1. Write a clear prompt: asset(s), chain, timeframe, metric(s).

2. Pick Preferred Charts (up to 5) or let Minara auto-select.

1. Review outputs (table + charts). Refine with follow-ups (e.g., “last 30d, exclude stablecoins”).

2. Save or reuse the prompt inside a workflow/report if needed.

Sample prompts

• “Show top 15 ETH whales by holdings; table + pie.”

• “BTC, ETH, SOL daily price and 30d performance; line + table.”

• “My portfolio by chain and asset; bar + pie + table.”

• “Compare weekly volume of UNI vs. SUSHI, last 90 days; line.”

• “Top 20 holders of TOKEN on Base; table + bar.”

• “Annotated K-line for SOL with major moves last 14 days.”

Chart guidance (what fits what)

• Trends over time → Line, K-line (+ annotations)

• Rankings / top-N → Bar/Column

• Composition / allocation → Pie (and table)

• Detail audit / export → Table/Spreadsheet (always generated)

Best practices

• Be specific: asset + chain + timeframe + metric.

• Start with a table, then add charts you’ll actually read.

• Limit scope: fewer assets/time helps speed, lowers cost.

• Disambiguate tokens with contract addresses for small/meme coins.

• Use consistent intervals (daily/weekly) for comparisons.

Cost & limits

• Credits scale with: time range, number of entities, data fan-out, and number of charts rendered.

• Very broad prompts may be trimmed to keep outputs readable and costs predictable.

• Some assets/chains/metrics may be unsupported; you’ll get a clear notice and a table fallback when possible.

Troubleshooting

• No chart returned: add chain/contract, narrow timeframe, or pick fewer metrics.

• Wrong asset matched: supply the contract.

• Charts look off: check the table first; adjust interval/aggregation.

• Slow/expensive: reduce entities/timeframe; prefer table-only, then add 1–2 charts.

• K-line missing annotations: pick a shorter period or major assets with richer events.