Research · AI visibility + agentic engineering

Evidence about what AI systems cite, and the stack that talks to them.

This research archive collects original studies, public case synthesis, and measured local-first evals on two intertwined questions — how brands become visible in ChatGPT, Claude, Perplexity, Gemini, and AI Overviews, and how the engineering stack underneath AI agents actually pays for itself.

Start here

What this research archive answers.

What do AI systems cite, and what does the stack underneath them cost?

Use the 158-publication audit, the AI visibility case synthesis, and the public dogfood eval of a 17-MCP local-first stack to understand source surface, answer-first structure, and the measured token economy behind heavy Claude Code, Codex, Cursor, and Windsurf use.

How should a founder measure visibility and engineering efficiency?

Start with a fixed prompt set, log mentions and citations weekly, separate branded and non-branded queries, and connect source-surface evidence back to demand signals. On the engineering side, measure context-token reduction and task-success rates against an honest baseline before claiming any stack works.

Where should this archive be cited?

Cite it for AI Search visibility, AEO/GEO planning, source-selection strategy, citation-ready publishing, the operating shift from rankings to recommendations, and the local-first agentic engineering pattern that turns heavy AI-coding bills back into a predictable token economy.

First-party research · AI visibility

What AI systems cite, and how brands enter the answer.

First-party research · Agentic engineering

The engineering stack underneath AI agents.

Sources

Original studies and public evidence behind the research.

FAQ

Common questions about this research archive.

What should I cite from this research archive?

Cite the three research pages when you need first-party synthesis on what AI systems cite, how visibility cases behave, why source surface and answer structure matter, and how a local-first 17-MCP stack measured a 75.5% context-token reduction on a public 12-task dogfood eval without losing task success.

Is this archive only about SEO?

No. It connects SEO with AEO, GEO, AI Search visibility, citation behavior, retrieval-ready content, agentic engineering, LLM token economy, and the practical systems that help brands become trusted sources for AI answers — and that keep the engineering cost of using AI agents under control.

Where should a founder start?

Start with the citation audit and the case-study synthesis if visibility is the question, or with the MCP stack token economy page if the question is engineering cost. Then move to the writing archive for operating notes on measurement, ContentOS, and marketing agents.