Marco is the in-product assistant for Macro by Mark. It can help you find a page, explain an indicator, read a chart, plan a forecast, or understand a release. It is useful because it works from the product context that the server can verify for the current request.
Marco is help for research and product navigation. It is not a source of personal investment advice, legal advice, medical advice, or guaranteed forecasts.
What Marco can help with
| Task | Example |
|---|---|
| Learn a concept | "Explain yield curve inversion like I'm new." |
| Understand an indicator | "What does core PCE measure, and why does the Fed care?" |
| Read a chart | "How should I interpret this chart?" |
| Find a page | "Where do I find release dates?" |
| Plan a forecast | "How would I compare ARIMA and ETS for unemployment?" |
| Check a source-backed value | "What is the latest CPI?" |
| Work with saved pages | "Summarize my dashboard." |
Questions about a current value, release date, news item, forecast run, or saved workspace object need source context for that request. If Marco cannot verify the data, it should say what is missing instead of giving a number or date.
Trust labels
Marco replies can include a compact trust label.
| Label | Meaning |
|---|---|
| Grounded answer | The reply has source cards that support the requested factual claim. |
| Conceptual answer | The reply explains a concept or workflow and does not need live data. |
| Limited source | Marco did not receive the source needed for part of the request. |
For data values, a source card should identify the series, provider, date, units, frequency, seasonal adjustment when known, and the retrieval or update time when available. An indicator page can support metadata. It does not prove a latest value unless the value was retrieved in the chat context.
Product and pricing answers
For product-scale questions, Marco follows the current public product facts and pricing surfaces. If a claim depends on the current catalog, plan, or account state, Marco should rely on server-supplied product context instead of guessing.
For plan questions, Marco follows the pricing page and the caller's server-resolved entitlement. Budget messages are shown only as user-facing availability state, not as model-vendor or internal routing details.
Current data and releases
Marco treats "latest," "current," "next," and "today" as source-required words. For example:
Can answer with retrieval
What is the latest CPI?
If the server retrieves a live observation card, Marco can state the value with the date, units, provider, and update time.
Limited without retrieval
What is the latest CPI?
If no live observation card is available, Marco should explain CPI and point you to the likely indicator page, but it should not state a number.
Release cards can include schedule data and, when available, actual, prior, consensus, and surprise fields. If those fields are missing, Marco should name the gap rather than infer it.
Forecasting questions
Marco can explain forecasting workflows and help compare the live forecast baselines used by Macro by Mark: ARIMA, ETS, ridge, and ensemble. Forecast answers should cover:
- model or workflow
- horizon
- assumptions
- uncertainty
- how to reproduce or inspect the result
Marco should not claim a forecast is accurate. It should not turn a forecast or macro view into a buy, sell, hold, trading signal, or portfolio allocation.
Private workspace context
Dashboard, watchlist, workspace note, project, and saved-run questions require signed-in, server-authorized retrieval. Marco does not receive private saved objects just because you are on a dashboard page. It receives compact source summaries only when you ask for that private context and the server authorizes the request.
If you are signed out, Marco can explain how dashboards or watchlists work, but it cannot inspect your saved objects.
Language and profile preferences
Marco may use a small set of preferences to shape the reply:
- current locale
- signed-in profile language
- timezone
- country
- experience level
- focus areas
Those fields help with language, date and number formatting, explanation depth, and examples. They are not source cards. Marco does not use raw cookie values, analytics history, marketing signals, or private saved records through this preference path.
Asking better questions
Name the series or page
"What does core CPI measure?" is easier to ground than "what is this?"
Say whether you need a value or an explanation
"Explain CPI" can be answered conceptually. "What is the latest CPI?" requires a retrieved observation.
Give dates for historical questions
"What was CPI in March 2026?" is better than "what was CPI back then?"
Separate macro analysis from trading decisions
Ask for a risk framework or scenario analysis, not a buy or sell call.
Conversations and history
Signed-in users keep multiple saved conversations, similar to ChatGPT or Claude. Use the New conversation button in the Marco header to start a fresh thread; the History button opens your saved list grouped by Today, Yesterday, Last 7 days, and Older. Click a conversation to switch into it, or use the trash icon on a row to delete just that thread. The Clear button in the header wipes all your saved Marco history at once.
Each thread holds up to 40 messages, and you can keep up to 50 threads per account. Older threads are automatically removed after the retention window (default 90 days) so the saved history stays manageable.
Visitors keep tab-local history only — Marco still works, but signing in unlocks the saved-history surface.
Rich formatting in responses
Marco's replies render full GitHub-flavored markdown:
- Headings, bold and italic, bulleted and numbered lists, blockquotes, tables, and task lists.
- Fenced code blocks with syntax highlighting and a per-block copy button.
- LaTeX math inline (
$y = mx + b$) and as display blocks ($$\\hat{y} = X\\beta + \\varepsilon$$). - Internal links to indicator pages, forecasts, dashboards, and the glossary are clickable and stay inside Macro by Mark.
External links are restricted to http and https (no javascript:
or data: URLs) and open in a new tab.
Full-page Marco at /marco
For long research sessions, visit /marco for a centered chat surface without the floating widget — same Marco, same saved history, but with a wider reading column. The floating launcher hides automatically while you're on that page.