Overview of modes
General Mode
Flexible, conversational analysis for exploratory questions
Workflow Mode
Structured, expert methodologies for complex analyses
Live Query Mode
Real-time blockchain node/API data for current state queries
General Mode
Default mode for most conversations. FlipsideAI interprets your question, generates a plan, writes queries, and produces results.How it works
1
Question interpretation
FlipsideAI analyzes your prompt and identifies intent
2
Table schema lookup
Matches your question to available Flipside data tables
3
Query generation
Writes SQL queries to extract the relevant data
4
Execution & analysis
Runs queries and generates explanatory text, charts, or tables
Best for
- Exploratory research
- One-off questions
- Flexible, iterative analysis
- Custom approaches that donât fit standard frameworks
Example
Characteristics
- Flexible: Adapts to your specific needs
- Conversational: Responds naturally to follow-ups
- Non-deterministic: Same question might yield slightly different approaches on different runs
- Exploratory: Great for discovering insights you didnât know to look for
Workflow Mode
Specialized mode using pre-trained, expert methodologies. Triggered automatically when FlipsideAI detects a match, or manually via@ selection.
How it works
1
Workflow detection
FlipsideAI identifies that your question matches a specialized Workflow
2
Methodology application
Applies a pre-defined, structured analytical approach
3
Step-by-step execution
Follows a consistent set of steps (quasi-deterministic)
4
Formatted output
Presents results according to the Workflowâs structure
Best for
- Complex, multi-step analyses
- Comparative studies requiring consistency
- Recurring analyses (monthly reports, protocol monitoring)
- Situations where expert methodology matters
Example
Characteristics
- Structured: Follows a predetermined approach
- Consistent: Same question yields same methodology
- Quasi-deterministic: Results are reproducible
- Expert-level: Codifies best practices for specific analyses
Live Query Mode
Real-time mode for querying current blockchain state directly from nodes or APIs. Use this when historical data isnât enough.How it works
1
Live data request
You explicitly request âlive queryâ or current state data
2
Node/API access
FlipsideAI queries blockchain nodes or APIs directly (not Flipsideâs historical tables)
3
Real-time results
Returns current balances, pool states, prices, etc.
Best for
- Current balances: âWhatâs the WETH balance of this address right now?â
- Live pool state: âWhatâs the current liquidity in this Uniswap pool?â
- Real-time pricing: âWhatâs the current price of ETH across DEXs?â
- Comparing live vs historical: âHow does current TVL compare to yesterdayâs?â
Example
Characteristics
- Real-time: Data is current as of query execution
- Node-dependent: Speed depends on node response time
- Explicit trigger: You must request âlive queryâ mode
- Limited scope: Only works for current state queries, not historical trends
Live Query Mode is not enabled by default. You must explicitly ask for it: - âUse live query
toâŚâ - âGet the current balanceâŚâ - âQuery the node forâŚâ
How modes interact
Combining modes
You can mix modes within a single conversation:Mode switching
FlipsideAI switches modes automatically based on context:- General â Workflow: When it detects a matching Workflow
- General â Live Query: When you explicitly request real-time data
- Workflow â General: When you ask follow-up questions outside the Workflowâs scope
Overriding modes
You can force a specific mode:- Avoid Workflows: âDonât use a Workflow, I want a custom approachâ
- Force Live Query: âUse live query mode for thisâ
- Request general mode: âIgnore specialized Workflows, just give me a quick answerâ
System workflow explained
Hereâs what happens under the hood when you ask a question:1
1. Workflow detection
System checks: Does this match a pre-trained Workflow?
- Yes â Trigger Workflow Mode
- No â Continue to step 2
2
2. Mode determination
- Does the user request âlive queryâ? â Live Query Mode - Is this a standard question? â General Mode
3
3. Table schema lookup
Identify which Flipside tables contain relevant data
4
4. Query generation
Write SQL based on: - Available tables - Userâs question - Workflow instructions (if applicable) -
Rules (if set)
5
5. Execution
Run queries and retrieve results
6
6. Results processing
Generate:
- Explanatory text
- Visualizations (charts, tables)
- Reports or Artifacts
Choosing the right mode
- Use General Mode
- Use Workflow Mode
- Use Live Query Mode
- Youâre exploring and donât know exactly what youâre looking for
- The question is straightforward and doesnât need expert methodology
- You want maximum flexibility
- Youâre iterating quickly
Pro tips
Start general, then go structured
Start general, then go structured
For unfamiliar topics:
- Start with General Mode to explore
- Once you understand the landscape, use Workflows for deep dives
Combine live and historical data
Combine live and historical data
Ask which mode is being used
Ask which mode is being used
If youâre unsure:
- âAre you using a Workflow for this?â
- âIs this live data or historical?â
- âWhat tables are you querying?â
Use Rules to control output across modes
Use Rules to control output across modes
Rules apply regardless of mode:
- Set a âpresentation-readyâ Rule â works in General, Workflow, and Live Query modes
- Rules control how results are presented; modes control what analysis is performed