Parallel's Agrawal Builds Agent Search to Replace Ad-Supported Web
Sequoia Capital
Former Twitter chief executive Parag Agrawal argues the ad-funded web will collapse as AI agents replace human browsers, requiring a new game-theoretic monetization model to pay publishers for agentic data usage within 12 to 24 months.
## Background
Published on August 25, 2026 by Sequoia Capital on RSS / web, this podcast episode features hosts Sonya Huang and Andrew Reed interviewing Parag Agrawal, former Twitter CEO and founder/CEO of Parallel Web Systems. The show notes explain how Parallel is building search infrastructure specifically for AI agents, treating human click data as a bug, and designing new economic models based on Shapley values to compensate publishers as agents replace human web traffic.
## TL;DR
Parag Agrawal argues that traditional search infrastructure built for human clicks is ill-suited for the emerging agentic web, where AI agents will execute queries at 1,000 times the volume of humans. Instead of launching a massive static index upfront, Parallel Web Systems built a search agent first, using real-time crawling to refine its architecture and cut search latency to 200 milliseconds while reducing token usage. Addressing the collapse of ad-supported web models as agents bypass ads, Agrawal outlines a framework using game-theoretic Shapley values to directly monetize content creators based on their actual data contributions. Parallel aims to serve as the core search infrastructure layer for model providers and enterprise agents, highlighted by its official integration into Google Cloud Platform.
## Atmosphere & style
The conversation carries an intellectually rigorous, forward-looking, and deeply technical tone, driven by Agrawal's insider perspective as a former Big Tech executive tackling foundational infrastructure problems. The dynamics between Agrawal and co-hosts Sonya Huang and Andrew Reed are collaborative and analytical, balancing deep technical architectural breakdowns—such as token extraction, memory hierarchies, and Shapley value calculations—with high-stakes economic strategy. It feels like an insider masterclass on the future of the internet, characterized by pragmatic optimism, sharp engineering clarity, and a ambitious focus on reshaping web economics for autonomous software.
## Key takeaways
- `00:00` Human clickstream data and browsing metrics act as a bug rather than a feature when training and optimizing search engines designed for AI agents.
- `00:00` AI agents are projected to query and consume web content at a scale 1,000 times greater than human internet users, requiring an entirely new architectural foundation.
- `05:00` Parallel Web Systems bypassed traditional upfront crawling and indexing costs by launching a search agent product that performs targeted, on-demand web fetching.
- `10:00` Rather than building frontier foundational models, Parallel operates as a specialized search infrastructure layer that acts as a multiplier on top of third-party LLMs.
- `10:00` Parallel's Turbo product optimized search compute to compress trillion-page web data into ~1,000 contextual tokens, reducing latency from 3 seconds to 200 milliseconds.
- `15:00` Agentic search eliminates low-quality web slop and human interface friction by extracting precise, highlighted excerpts directly from authoritative primary sources.
- `25:00` Foundation model pre-training web crawls prioritize cheap raw token volume and ignore complex, JavaScript-rendered sites that contain critical long-tail real-time data.
- `25:00` Parallel partnered with Google Cloud Platform (GCP) to integrate its system as an official search and grounding provider alongside traditional Google Search.
- `30:00` A single human prompt to a reasoning or background background monitoring agent routinely triggers tens to thousands of secondary backend queries across the web.
- `35:00` The transition to agentic search breaks the ad-supported economic model of the internet by removing human attention and ad impressions from content consumption.
- `35:00` Current fixed-fee licensing agreements between AI labs and top publishers fail to scale with the exponential growth of inference volume and exclude long-tail creators.
- `40:00` Parallel utilizes Shapley value game theory models to estimate data contributions and dynamically redistribute LLM inference revenue back to content creators.
- `45:00` Content publishers are moving into a dual-publishing model, maintaining human-readable sites alongside structured, context-dense views optimized for AI agents.
- `50:00` Agentic web infrastructure is evolving from reactive tool-based pulling toward push-based architectures where agents register continuous monitoring criteria.
## Detailed walkthrough
### `00:00` Rethinking Search for an Agentic Web
Parag Agrawal, former CEO of Twitter and founder of Parallel Web Systems, outlines a fundamental shift in how search infrastructure must be built for artificial intelligence. Traditional search engines were designed around human behaviors: keying in short, incomplete queries, clicking links, and providing feedback via manual ratings and clickstream data. Agrawal argues that for search agents, **human click data is a bug, not a feature.** Because AI models process information far more thoroughly, an agentic search engine must optimize for agent feedback instead of human browsing habits.
Building Parallel Web Systems meant completely unlearning the operational strategies of running a post-product-market-fit giant like Twitter. Rather than managing an established platform with hundreds of millions of daily active users, Agrawal had to approach the web from the perspective of a pre-product-market-fit startup building technology for a customer base—autonomous agents—that has yet to fully arrive.
- **Key Premise:** AI agents will query and consume web data at **1,000x** the volume of human internet users, requiring entirely new search architecture and monetization models.
- **Core Technology Thesis:** Advances in model compression allow research from LLM training to be directly applied to search indexing and ranking, making full-scale web search far more tractable for a startup.
---
`05:00` Tackling the Infrastructure of Giants Incrementally
Standard web search relies on massive infrastructure: continuously crawling hundreds of billions of URLs, building a central index in memory, and executing multi-stage retrieval and ranking to match billions of queries against billions of web pages. Historically, maintaining a full web-scale index was an expensive endeavor feasible only for tech giants like Google and Bing. Parallel challenges this status quo by eliminating the need for upfront capital expenditure through an incremental indexing strategy.
Rather than launching a full-scale search engine on day one, Parallel initially shipped a **search agent product**. When a complex user query arrived, the search agent performed real-time, on-demand crawling to retrieve the necessary pages. While traditional search indexing acts as a latency optimization for humans who expect instant responses, agents executing deep research are often willing to wait longer—ranging from one to ten minutes. By targeting workflows where companies previously outsourced data collection to human workers, Parallel gathered critical evaluation datasets while incrementally expanding its search index.
- **Initial Use Cases:**
- Insurance underwriting workflows and claims processing
- Sales data enrichment
- Financial research and overnight data curation replacement
- **Competitive Edge:** Competing with human data annotators sitting in front of search engines was vastly easier on day zero than competing directly with Google’s instant search infrastructure.
---
`10:00` Search Infrastructure vs. AI Model Development
While some industry observers might view Parallel Web Systems through the lens of a modern AI "neolab," Agrawal draws a clear distinction: Parallel does not view its core output as a standalone frontier model. Instead, its systems act as a multiplier on top of existing models. When an outside laboratory releases a superior base model, Parallel’s infrastructure automatically gains access to broader use cases without having to bear the astronomical cost of pre-training mega-scale foundational models.
```
+----------------------------------------------------------------------+
| Parallel System Architecture |
| |
| [ Trillion Web Pages ] ---> [ Memory Hierarchy ] ---> [ Tiny Model ]|
| |
| Goal: Distill billions of web documents into the precise ~1,000 |
| tokens required by an agent context window in real time. |
+----------------------------------------------------------------------+
```
Parallel's internal research focuses heavily on adapting lightweight model architectures to solve a massive retrieval challenge: filtering through a trillion web pages to extract the precise 1,000 relevant tokens requested by an agent. The company recently upgraded its architecture, cutting its read-time search latency down from **3 seconds to just 200 milliseconds**.
> "Every query is essentially: give me 1,000 tokens from a trillion web pages on the web and make sure they're the right thousand tokens... Until last week we would give ourselves 3 seconds to throw a bunch of compute at read time to do it. This week... we shipped a product which now does it in 200 milliseconds."
---
`15:00` Bypassing Web Slop and Human Interface Limitations
Standard deep research loops often rely on basic search engine APIs (like Google), but this pattern wastes context windows and inflates costs. Parallel minimizes token usage by filtering out fluff before passing information to an LLM. Because agents can formulate detailed, well-specified queries without typos, search engines receive far richer signal upfront, eliminating the guesswork inherent in human search.
```
+-----------------------------------------------------------------------+
| Human vs. Agent Retrieval |
+-----------------------------------------------------------------------+
| HUMAN SEARCH |
| Short/Lazy Queries -> Fast SEO Page -> Fluff/Slop -> Manual Scroll |
| |
| AGENTIC SEARCH (Parallel) |
| Detailed Query -> Deep SEC PDF -> Precise Excerpt -> Context Window |
+-----------------------------------------------------------------------+
```
Agrawal highlights why the modern web is filled with low-quality, SEO-optimized "slop." Humans are naturally lazy; if a search engine directs a user straight to an authoritative 300-page SEC filing PDF to find a single revenue figure, the document takes seconds to load, forcing the user to dig through dozens of pages. SEO sites exploit this by extracting that number and placing it above the fold on a fast-loading page. For agents, this trade-off is irrelevant: Parallel extracts exact, highlighted excerpts straight from authoritative primary sources and streams them directly into the agent’s context window.
- **Token Efficiency:** Using Parallel allows agents to consume **under half the tokens** typically required by standard search APIs, directly lowering costs and speeding up runtimes.
- **Optimization Triad:** Agentic search is treated as a continuous trade-off among **quality, cost, and latency**.
- **Interface Evolution:** Agents bypass autocomplete menus and click-bait landing pages, interfacing directly with structured indexing systems.
`20:00` Inside the Multi-Layer Search Architecture and the Pursuit of Quality
Parag Agrawal walks through the complex, multi-layered architecture required to process an agent query across massive volumes of web data. Rather than relying on a single static index, the system acts as an orchestrator. Upon receiving a request, the initial system layer formulates and crafts specialized sub-queries for various backend datastores. These backends span a primary massive web index, a dedicated fresh index, structured indexes, and specialized knowledge graphs.
Once queries are routed, each component executes a multi-stage process of retrieval and iterative re-ranking. The challenge is winnowing down tens or hundreds of billions of web URLs down to tens of thousands, then isolating specific paragraphs and excerpts, and ultimately boiling everything down to a tight, high-signal payload of roughly 1,000 tokens returned directly to the requesting AI model. Different versions of Parallel's search API adjust the amount of compute thrown at each step of this pipeline to navigate specific latency and cost tradeoffs.
When asked about the "North Star" metric for search quality (analogous to Google's traditional objective of landing the right answer in the top three results), Agrawal views stringing together query intent with web data as a "forever problem." Matching a billion needs to a billion pieces of information is an infinite optimization loop, where the challenge is deciding when incremental improvements no longer justify the compute expense. However, as foundation models grow cheaper and more capable every few months, the bar constantly shifts. If a search system can deliver a 20% edge in matching efficiency or signal clarity, that distinction creates a massive competitive moat.
- Parallel's query pipeline narrows down hundreds of billions of candidate URLs to an ultimate context window payload of ~1,000 high-signal tokens.
- Optimization parameters trade off compute allocation across various ranking layers to meet target cost and latency bounds.
- System design focuses on the "memory hierarchy" to store and retrieve data efficiently under strict performance constraints.
- Agrawal asserts that matching intent to data is a perpetual challenge where even a 20% quality advantage yields significant market leverage.
---
`25:00` Why Model Labs Won't Own Search and Parallel's Major Partnership with Google Cloud
Addressing the counterintuitive premise that large model labs might naturally dominate search infrastructure because of their existing pre-training web crawls, Agrawal points out a fundamental flaw in that logic. Pre-training web crawls are fundamentally misaligned with what search agents actually need. Foundation model developers focus on sheer token volume—seeking trillions of tokens as cheaply as possible—and routinely abandon slow, JavaScript-heavy, or hard-to-render pages. In contrast, an agent search index must be "completionist," waiting on complex client-side rendering to fetch fresh, long-tail data that the base model never saw during training.
Agrawal notes that 9 out of 10 enterprise LLM deployment scenarios require active web connectivity and grounding to perform real work. While model labs could theoretically build custom real-time search infrastructure, it represents a completely separate technical stack. This creates a buy-versus-build dynamic where Parallel positions itself as the primary search infrastructure layer for model providers.
Highlighting a major commercial milestone, Agrawal reveals a strategic partnership with Google Cloud (GCP). Under this agreement, Parallel Search is directly integrated into GCP as an official grounding and search provider alongside Google Search itself. Developers building enterprise AI agents or chat applications on GCP can choose Parallel to ground Gemini or other models, backed by deep technical and product co-engineering between the two engineering teams.
> "For them, it's like 'I'll take X trillion tokens'... For us, we are completionist."
- Model labs optimize pre-training crawls for compute-to-token efficiency, skipping complex JavaScript sites that contain critical real-time information.
- Parallel Search is integrated into Google Cloud Platform (GCP) as an official search and grounding partner for enterprise agents alongside standard Google Search.
- The GCP integration involved joint engineering work across technical, product, and commercial teams to optimize Gemini model grounding.
- Agrawal anticipates that the vast majority of commercial LLM workloads will require real-time web retrieval infrastructure.
---
`30:00` The 1000x Search Multiplier: From Simple Queries to Background Enterprise Agents
The discussion turns to what a "1,000x increase" in search volume actually looks like in practice. Agrawal explains that even standard interactive search agents execute 5 to 20 sub-searches under the hood to answer a single human prompt. When users dial up the reasoning intensity or ask for deep research, a single prompt can trigger hundreds or even thousands of automated backend queries.
The true shift in scale, however, comes from asynchronous "background agents" operating on schedule without direct human initiation. Agrawal shares real-world examples: credit risk monitoring systems evaluating portfolios of 10,000 small businesses every week by scraping fresh web signals, or internal executive prep agents (such as the custom ones used at Parallel or Notion) that scan massive amounts of private and public web data ahead of every scheduled calendar event. A single prompt setting up an automated workflow can result in continuous, compounding background searches indefinitely.
This demand pattern shaped Parallel's early product engineering roadmap. In its initial years, the team deliberately ignored system latency to focus entirely on optimizing retrieval quality and unit economics, knowing that model distillation and speed optimizations are well-understood engineering problems compared to core search quality. Once those quality and cost baselines were achieved, Parallel released **Turbo**, which Agrawal describes as the fastest, highest-quality agentic web search product on the market.
- A single standard query to a search agent routinely generates 5 to 20 background queries, scaling to hundreds for complex reasoning tasks.
- Enterprise background agents—such as automated credit risk monitoring across 10,000 SMBs—multiply human search volume by factors of hundreds of thousands.
- Parallel prioritized quality and cost optimization over speed during its first two years, postponing latency work until core performance was solved.
- The company recently launched **Turbo**, achieving market-leading speed and low latency for agentic web queries.
---
`35:00` The Collapse of the Ad-Supported Web and the Need for a New Economic Engine
Agrawal transitions to a topic he views as existential for the internet: the breakdown of web economics under an agentic paradigm. Reflecting on his background building ad systems at Twitter, he defends the traditional advertising model, calling it an extraordinarily efficient mechanism for differential pricing. Ads subsidized the free web, allowing platforms like Google and Twitter to offer powerful tools to humanity at zero monetary cost by capturing high-margin revenue from a minority of commercial interactions.
This economic foundation relies entirely on human attention and manual page views. When automated AI agents act on behalf of users, the traditional monetization loop breaks down completely. Publishers cannot convert anonymous agent scrapes into ad impressions or subscription sign-ups. In response, content owners are increasingly incentivized to block AI crawlers or wall off their sites, creating an unsustainable ecosystem tension.
Agrawal criticizes the current status quo of fixed-fee licensing deals struck between major publishers and AI labs. These deals are restricted to top-tier media outlets, completely ignoring the long tail of web content. Furthermore, fixed-sum contracts fail to scale alongside the exponential growth of AI inference—meaning publishers see their relative share of value evaporate as inference volume surges 7x or 50x year-over-year. To resolve this, Parallel is working on a scalable monetization framework inspired by mathematical principles like Shapley values, designed to measure actual data contribution and compensate content creators dynamically based on usage and value delivery.
> "I know most people hate ads. I used to do ads and build systems for ads. I love ads... ads is the reason that so much amazing content and technology is available for free to all of us."
- Ad-supported business models succeed due to differential pricing, using high-value commercial queries to subsidize free access across the broader web.
- AI agents break traditional publisher business models by consuming site content without generating ad impressions or standard subscription conversions.
- Existing publisher licensing deals with AI labs are flat-fee structures that fail to scale with the exponential growth of AI inference volume.
- Parallel is building an economic alternative using concepts like Shapley values to directly compensate content owners based on the programmatic value their data provides to agents.
`40:00` Economic Attribution, Incentive Alignment, and Shapley Values
The discussion focuses on the economic challenges of the agentic web and how content providers should be compensated. Parag outlines three core reasons why AI model companies currently pay content creators or publishers:
* **Freshness during inference:** Fetching up-to-date data for real-time display in products like ChatGPT or Claude.
* **Training data:** Acquiring corpus data for foundational or fine-tuned model training.
* **Liability protection:** Securing legal coverage for pre-existing training data already utilized.
Because a single complex agentic query can trigger ten or more searches, allocating value across multiple web sources requires rigorous mathematical modeling. Parag highlights that the core underlying issue is incentive alignment. He walks through a theoretical thought experiment: if one piece of content is withheld from the corpus and the agent's output quality drops, one must evaluate how much additional compute or model enhancement is required to regain that lost quality. If spending one cent of compute restores equivalent customer value, that source is effectively worth close to one cent.
To formalize this intuition, Parallel uses game theory, specifically **Shapley values**. Originally used in cooperative game theory (and in machine learning for feature importance), Shapley values mathematically calculate how to distribute a joint reward when a group collaborates to create something larger than the sum of its parts.
```
┌─────────────────────────┐
│ Shapley Value Framework │
└────────────┬────────────┘
│
┌───────────────────────┴───────────────────────┐
▼ ▼
┌───────────────────────┐ ┌───────────────────────┐
│ Theoretical Ideal │ │ Practical Challenge │
├───────────────────────┤ ├───────────────────────┤
│ Simulates all feature │ │ Calculating exact │
│ combinations to divide│ │ values costs more │
│ revenue fairly. │ │ than the search text. │
└───────────────────────┘ └───────────────────────┘
│
▼
┌───────────────────────┐
│ Parallel Solution │
├───────────────────────┤
│ Train ML models to │
│ estimate Shapley │
│ values via simulation.│
└───────────────────────┘
```
However, computing exact Shapley values directly across the web is computationally impractical because calculating a content owner's $1 share could cost several dollars in simulation compute. Parallel addresses this by training predictive machine learning models to estimate Shapley values based on eval quality data and counterfactual web-access scenarios.
- **Market Dynamics:** Parag compares this approach to second-price ad auctions, where systemic feedback loops and auto-bidding established long-term market trust and true value discovery.
- **Variable Data Pricing:** Under this model, unique, highly differentiated data yields higher payouts. Additionally, reader context matters: data accessed for a high-stakes task by an investment banker commands a higher payout than the same data accessed for casual reading.
- **Macro Economics:** Allocating 2% to 10% of total LLM inference spending toward web data providers would dwarf existing web content business models outside of walled gardens like Facebook or LinkedIn.
- **Timeline:** Parag projects that within 12 to 24 months, this mathematical payout model will distribute meaningful revenue to a wide spectrum of web content publishers.
---
`45:00` The "Parallel Web" and Dual-Publishing for AI Agents
Addressing the decline in human traffic on sites like Stack Overflow, Parag explains that solving economic incentives for publishers was the core motivation for starting the company. He reveals that the original incorporated entity name was **Shapley Inc.** (and the team secured `Shapley.ai`), though it was always intended as a placeholder while operating in stealth under the working title "NuCo."
After six to eight months, the company rebranded to **Parallel Web Systems** (Parallel) to reflect two core concepts:
1. Executing massive web operations concurrently in parallel.
2. The emergence of a parallel web tailored specifically for AI agents alongside the human web.
```
┌──────────────────────────┐
│ Dual-Publishing Paradigm │
└─────────────┬────────────┘
│
┌───────────────────────┴───────────────────────┐
▼ ▼
┌───────────────────────┐ ┌───────────────────────┐
│ Human-Facing Web │ │ Agentic Parallel Web │
├───────────────────────┤ ├───────────────────────┤
│ Formatted for visual │ │ Optimized for rapid │
│ browsing, layout, and │ │ extraction, structured│
│ manual reading. │ │ context, and APIs. │
└───────────────────────┘ └───────────────────────┘
```
Publishers are entering a dual-publishing era. Content creators will design one view of a page for human visual consumption and a parallel structure optimized for agentic ingestion. Andrew and Parag note that high-value formats—such as corporate earnings transcripts and API documentation—have already flipped to being primarily read and processed by agents rather than human eyes.
- **Internal API Testing:** Parallel tests its own API documentation primarily using agents rather than human readers, reflecting the agent-first reality of software integration.
- **Public Company Communication:** Executive communications and earnings reports will increasingly be structured specifically to avoid misinterpretation by financial AI agents.
---
`50:00` The 3-Level Evolution: From Search Tools to Push-Based Agentic Infrastructure
Parag outlines a three-level framework for how AI agents interact with web infrastructure:
1. **Level 1 (Tool Usage):** Agents use the web via basic, traditional web-search tools, mirroring human search behaviors through simple prompt-and-response interfaces.
2. **Level 2 (Multi-Agent Systems & Orchestrator Harnesses):** Complex multi-agent architectures (such as coding harnesses or long-running "AI Scientist" systems) spawn sub-agents that throw compute and data at multi-step tasks.
3. **Level 3 (From Pull to Push):** The web shifts from reactive fetching ("pull") to proactive notification ("push"). Instead of an agent constantly querying for updates, agents register standing criteria with the web layer: *"Call me when X changes."*
Parag shares his internal team mantra: if a task can be done today with available GPUs, do it immediately; tomorrow's agentic work should be triggered asynchronously by dynamic changes in the real world—whether updated web content, new satellite imagery, or downstream outputs from another agent. In Level 3, continuous compute is allocated across the entire web, continuously monitoring for changes and executing workflows automatically on behalf of users.
- **Host Team Closing:** Sonya Huang and Andrew Reed thank Parag Agrawal for sharing his vision for agentic web infrastructure, marking Andrew's debut co-hosting appearance on the show.
## Notable quotes
> `10:00` Every query is essentially: give me 1,000 tokens from a trillion web pages on the web and make sure they're the right thousand tokens... Until last week we would give ourselves 3 seconds to throw a bunch of compute at read time to do it. This week... we shipped a product which now does it in 200 milliseconds. — Parag Agrawal
> `25:00` For them, it's like 'I'll take X trillion tokens'... For us, we are completionist. — Parag Agrawal
> `35:00` I know most people hate ads. I used to do ads and build systems for ads. I love ads... ads is the reason that so much amazing content and technology is available for free to all of us. — Parag Agrawal
## Mentioned
Parag Agrawal, Sonya Huang, Andrew Reed, Twitter, Parallel Web Systems, Parallel, Sequoia Capital, Google, Bing, Google Cloud Platform, GCP, Gemini, ChatGPT, Claude, Notion, Stack Overflow, Shapley Inc., Turbo
[10:00] Parag Agrawal: Every query is essentially: give me 1,000 tokens from a trillion web pages on the web and make sure they're the right thousand tokens... Until last week we would give ourselves 3 seconds to throw a bunch of compute at read time to do it. This week... we shipped a product which now does it in 200 milliseconds.
[25:00] Parag Agrawal: For them, it's like 'I'll take X trillion tokens'... For us, we are completionist.
[35:00] Parag Agrawal: I know most people hate ads. I used to do ads and build systems for ads. I love ads... ads is the reason that so much amazing content and technology is available for free to all of us.
Original transcript
[0:00] our view at parallel. is that human click data He's a bug. an agent doing work with search should rely on agent feedback not human feedback. We believe that These models are really good at compressing information and we can benefit from a lot of the research that have gone into building models. and apply it to search indexing and ranking. And so you can now make many, many arguments, and that's the arguments we made back then, that actually now it's way more tractable as a problem because of the existence of agents, not just as in technology, but as a distinct customer. *music* Parag, thank you so much for joining us today. We're delighted to have you on the show. For those who don't know, Parag of Twitter CEO fame was CEO of Twitter before selling it to Elon and is now back on the founder arc. You founded a company called Parallel Web Systems, which is scaling up. agentic search for the agentic web. We're very excited to have you here today to talk about the future of search and the future of the internet. So let's get started. What's Parallel? - Thank you, Sonia, for having me. Thanks, Andrew, for joining us. I'm really excited about this conversation. At Parallel, we're building a bunch of technology in order to allow agents to search and use the web. So just like humans forever have figured out how to use browsers and search engines and clicking and browsing around the web to access information, agents need to do the same things. We started parallel with the bet that agents would do it a thousand X more than humans ever have. and as a result we need to reinvent the technology that can power search for agents. but also the business models that go alongside it. And that's what we're doing at Barul. Okay, I want to go back into what's what makes human and agent search so different. But before we get there, you've told us that, you know, you're, you're unlearning a lot of the lessons that you learned from running Twitter as you build build parallel. Why is that? Listen, when I was at Twitter in leadership roles. Twitter was a post product market fit, extraordinarily scaled business. where your feedback loops were from the hundreds of millions of customers using the product for 30 plus minutes every day. In that world you operate differently than a pre-product market fit company based on the premise that In a few years... a new customer is going to show up on the internet and let's go build technology for the not yet here. Customer. that we are all learning every day and every week. Fantastic. Okay, let's talk about Parallel. I have a question, actually. Can I jump in? No, you cannot, Andrew. I'm Andrew. I didn't get an introduction, but I'm also happy to be an inaugural guest on the Training Data podcast. Andrew is making his podcast debut on Training Data. We are honored to have you finally here. Thank you. Um... I feel like all of us in Silicon Valley have a very surface level idea of search. Like what is search? Like the job to be done is getting the answer makes sense. But we all know there's crawling and there's an index and there's ranking. But maybe let's take a big step back and explain. What is the problem of web search, be it for... a human or an agent, and then we can dive into the differences. The problem of web search, and we all know it and experience it, when we want to find something and we do not know where it is on the web, we go to a search engine like Google. and the search engine then hopefully surfaces the answer to us in the most convenient of locations. That's the base problem. Now, in order to do this, what is the search engine doing? The search engine is going and crawling the web, which is finding every URL that's out there, trying to read it. trying to organize that information in what might be called an index so that by having all of this stuff in memory in one location, you don't have to, once the query comes in, you don't have to spend time loading up pages because you already have them. You've already done pre-processing to organize them. And then when the query does come in, You quickly understand the query, you find the most relevant results, and then there are many many, because you're essentially taking hundreds of billions of pages, and narrowing it down to what? 5 or 10 or ideally 1 in terms of what someone is looking for right now. So you go through these multiple stages of retrieval and ranking
[5:00] in order to surface the most relevant. result. So that's the broad problem. One way to think about it is it's a billion to billion matching problem, right? So you have hundreds of billions of pages, Thank you. and hundreds of billions of queries over time. And you need to figure out how to match make across these two. That sounds like an enormously expensive infrastructure challenge. And I think for the longest time, basically only Google And Bing! had you know done full web-scale crawls and indices. Why did you think about, you know, you as a young company could go off and tackle that problem? It seems like a problem of the giants. So, it is expensive in the long term. So what's actually interesting is that when I was starting the company three years ago, You could... Imagine a world where One, some of the reasons it was difficult for others to compete, which was not having access to great feedback in terms of is this a better search result than this? To collect that feedback at scale, there was a problem around human ratings. There is a problem around click data. You need to access those. Now, it is, of course, expensive to crawl the entire web and index it. But as you think about what agents and the large models that we now have access to have enabled is... the ratings data, can be now created by experts way more cheaply. Our view at Parallel is that human click data He's a bug. an agent doing work with search should rely on agent feedback, not human feedback. We believe that these models are really good at compressing information and we can benefit from a lot of the research that have gone into building models. and apply it to search indexing and ranking. And so you can now make many, many... arguments and that's the arguments we made back then that actually now it's way more tractable as a problem because of the existence of agents not just as in technology but as a distinct customer. And then we figured out a way to go about building this business, which did not require us to go spend all of the money on infrastructure upfront before we could service a customer. Right? So if you can paint a path of incrementally being able to build an increasingly larger and more sophisticated index. Over time, as you solve problems for more and more customers, That's... The insight that actually convinced me that this was a viable problem. for after take on. And how do you make that happen? Because I imagine this is one of those things where... customers want full coverage day one so how do you go about making that happen when when we first launched the product right we launched in We did not launch our search product first. We launched a search agent product first. our search agent could go essentially crawl the web. after a query arrived. So if you are doing deep research You have patience to the extent of a minute and we've had products which sometimes take 10 minutes of research That's a lot of time to be able to crawl a lot of pages if only you have enough of a map to know how to prioritize crawling, right? So you can make up for shortcomings, like index is oftentimes, you can think of it as a, latency optimization. So if you give up on that dimension, if you're competing with humans, that's why our search agents were competing with the alternative being outsourcing to humans to curate amazing data. Right? So we said It seems like humans sitting on search engines are far way easier to compete with. than a search engine on day zero. So by building a product that was a search agent to do real work on top of web data, we were able to incrementally go build our index. Well, there's some examples of what people built with your search agents. In the very early days, there were search agents being built with us for doing some kinds of insurance underwriting workflows and claims processing workflows. people in sales who are doing all kinds of sales data enrichment. people in finance who would previously and historically go to build a model, collect data by sending it overnight to a set of humans who would curate data that would feed into a modeling exercise they would do, would start using us to do that instead. And so we were going initially after replacing where there was outsourced. human work on top of web data. in order essentially to collect Evals.
[10:00] to run agents, to figure out what search for agents. should look like in the first place with empirical use cases. instead of theoretical evils. I see. You're turning off the... crawl for inference time compute effectively. Yeah. You guys... were started before the term like NeoLab came into existence and you have you know, web systems product, but you also have like a bunch of AI people. From the outside, before we met for the first time, like it wasn't obvious to me how much of a web systems company or an AI company that you've built. The more time we spend together, the more clear it's like, by some definitions, this is a neolab. Do you want to talk about where... the research side of what you're doing comes in, not just the infrastructure and system side of what you're doing. so we don't categorize ourselves as a neoliberal. Well, of course you would not. We... No, because I don't think... Our output is immoral. Like I somehow... maybe my definition is broken. My definition of a new lab is an output as a model. I think our output is a complement to a model. What we build is something that multiplies on top of a model in order to... give either you can call it the model gets better or the agent built with the model gets better and has superpowers right so we've always want to be in a place where whenever someone ships a better model a neolab for example if somebody else ships a better model They have a higher hill to climb. For us, somebody ships a better model, they have now unlocked four more use cases where we can be valuable. Now... whether we need to do work that might be framed as research. that So in that sense we do have to do research but we are also not pre-training extraordinary large models. In fact our job is to compress things down into tiny ranking models, right? Like I think if you go back to my framing around like this 100 billion, 200 billion matching problem, every query is essentially Give me... 1000 tokens from a trillion web pages on the web and make sure they're the right thousand tokens. Like that's the query that we are getting effectively from to our search engine. And so now what do you have to do? And until last week we would give ourselves 3 seconds to throw a bunch of compute at read time to do it. this week, last week, we shipped a product, which now does it in 200 milliseconds, right? So you have now that much time to go figure out how to pick those, right? So you will do, We're trying to organize information in memory across the memory hierarchy in a way that we can access it fast. We're trying to figure out how to train what model Uh... to select the best 1000 tokens. And so there's a large amount of research that goes into figuring out how to take a pre-trained model of some kind, adapt its architecture for this new problem, and allocate effectively compute. in a way that produces the best output. with a limited compute/latency budget. So a lot of these use cases seem like the deep research kind of shaped use case. And when I think deep research, at least in the earlier incarnations, it was... Effectively like an agentic loop with the model reasoning and then basically just calling a search engine. calling Google or some proxy to Google. - Yeah. - Right? Why is that insufficient in your eyes versus what I'm hearing from you is agentic search is kind of a net new capability. So... Calling? Google. for every query in a deep research thing. It gets you somewhere. Right? Okay. If you use... parallel search. you will for the most part use under half the tokens in your agent. it will become more accurate and to be faster into it. And so you can think of it as... But every time, if you use only half the tokens, if your model is context limited or memory limited, you can now do More problems. You can do the same problems cheaper. or for after. So everything, to me, when you have a infinite appetite for information and relevant information for all kinds of work. It's at its core an optimization problem around quality, cost and latency. Every model advancement is about how do you squeeze out more intelligence and then how do you distill it down? into keep most of it at a tenth of the cost, right? And that applies to search as well. And every time you can produce... all of the signal with less noise in your search results to give to a model.
[15:00] you now give the model the ability to do more. And so a lot of the bet here is intelligent compute allocation. across the model layer and the agent layer down to the search layer The other interesting thing to observe is the interface actually changes. Oh. when you think about serving agents versus humans. Humans rely on keyword search. With agents we've had to innovate quite a lot on the What does an agent tell our search engine? The more we know, the better we can do. Interesting. So humans can only hold a few words in memory, basically. versus an agent. No, I think we can. We're just lazy. yeah right like we can we can have a conversation we can hold a lot of words but when you start typing We We want to tell Google like two incomplete words with a typo in there. and hope for the best or rely on some form of a drop-down autocomplete thing to avoid typing those three words in the first place. So we're fundamentally lazy. Turns out like models less so. Few typos. better specified queries, perhaps longer queries Less for the search engine to guess what the agent might want. So you get to solve a different class of problems. One other thing about humans is I feel like we know how to decipher... the pre-AI slop that populates many of the top-ranking Google results sites you know, for best product for X, Y, and Z, and you get all the affiliate advertising things. Um, And yet, obviously, they rank highly. I'm very susceptible to it. Are you? Yeah, I'm like, I feel like I have this incredible, I can see it coming a mile away. How do agents deal with things like that, right? Where these are, you know, well-trafficked pages, they have seemingly good answers, but you just know they're not. real. Perhaps with parallel agents, you have to deal a little bit less with that. Let me tell you why those... pages. exist in the first place. Let's work through a simple example. If you ask for... of public companies most late most recent financials. like just the headline revenue number. We can sit here and know that there exists an authoritative filing with the SEC. which has that number. perhaps on page 73 of a PDF. That is the authoritative number. Now imagine Google decided like I care about authority. And whenever you ask that query, That's the first result you see. Right? And then you click that, this PDF takes what? Like 3.5 seconds to load instead of the second that another page does. You're already frustrated. And then you see a... or in speech. That's the alternative. But here you have to now grab your way to page 77 to find your answer. We're lazy. we're not going to do the work. Right? So now there exists an entire class of content on the web, which is like, okay, this information is needed by a lot of people. it is worth putting it on a page that loads fast, where this information is above the fold. All of you can go there. It's, 99.99% right. So you're not like so skeptical when you go there that this is 100% wrong. And it's added real value in the process because it identified out of the 300 page page earnings report to empty bits of information that should be above the fold. And so you can call it pre-AI human slop, or you can call it catering to a lazy human and being successful at SEO. The good news is with agents, We're not making the agent click around and fumble around and crap a PDF, right? We're taking ı excerpt from the most authoritative place on the web. and trying to bring it to the agent's context window. And so we aren't forced into this We are trade-off. And this trade-off existed with humans in the first place because like with standard browsers and protocols and everything, we just didn't figure out how to have... us point exactly, consistently across everywhere on the web to the exact right, highlighted, tiny, paragraph, right? With agents we get to bring that to the agent's context. and then let it figure out what's next. Can you walk us through what actually happens when one of your developers sends a query off to your agentic search API? It's in some sense pretty standard. So we've done some models to figure out what this query is and enrich it to figure out how it will flow into the rest of our system. we have a bunch of indexes which organize different subsets of the inf of the web
[20:00] in different ways. And so the first layer will essentially craft queries for each of these different systems. Each. One of these systems perhaps is our sort of big index. One of these is perhaps our fresh index. One of these is perhaps like you can some people will describe it like a knowledge graph. Some people will describe it like a structured index. There are a bunch of these, right? So you're now deciding which ones this query needs to go to. you're figuring out what is the query rewrite for each of these. Then each of these has a big retrieval layer and then a ranking layer, and then more ranking layers. So you're going to try to boil down tens, hundreds of billions of URLs or documents. down into thousands, tens of thousands. down into specific excerpts and paragraphs in those tens of thousands with more and more bigger models running at each stage with different architectures pulling more features. to ultimately get down to here are the 1000 tokens I want to bring back to this AI. which has the highest signal. And now if you look at our various versions of our search API, They just throw... for different latency and cost constraints. different amounts of compute. at various points in this journey. to hit those limits. So in the abstract, it's Simple. Right? What's interesting is what each of these models that I described, how you curate and collect the training data for them. Right? How you build those models and optimize them. The index itself, how you use the memory hierarchy to store it to be able to hit certain cost quality latency thresholds. What's the North Star from a quality perspective? Like, you know, on Google, there's that, you know, did you get this result you wanted in the first three answers or something? What is the equivalent North Star for you? So I think of, I don't know if I'm right on this, but like my... take is that a billion to billion matching problem is a forever problem. Thank you. And... So the real question is at what point incremental optimization isn't worth the squeeze. so I don't think there is a thing as like okay We're done. on improving this thing. The question is at some point, it's going to get harder and harder to improve this thing. And it just won't be Worth it. But I'm hoping that we don't get there actually because like if you think of what we're doing with AI. we will have more intelligence that gets cheaper. every few months. and as a result of it, it will come down to having great models which are cheap. having great information. Thank you. matchmaking across a need and all of the information available to you, whether it's your own or on the web, and doing something unique and differentiated with it to produce more knowledge. And anytime you can do something 20% better. than somebody else. that might give you an edge. So why wouldn't you? So, in the super AGI-built worldview, it feels like If you can push on quality across web search and in the model layer. Thank you. Why wouldn't you? I've heard a point of view that this is so fundamental to the model companies that they're just going to own it. And in part, because as they're, collecting data for pre-training, that's a very, very expensive infrastructure exercise. That kind of is your source of truth for the crawl. What do you think of that? I don't see... Empiric data on the ground to support that view. To build a fresh web index. I don't think that crawl is particularly... useful. and let me frame y. So if you think of what we are building. We are building a complement to models. we like to crawl things that people don't like to crawl for pre-training Because like if the model already was trained on it, Like it's not useful. model companies for the training. aren't patient enough to go in a completionist way, try to wait for really slow random JavaScript to load. because... the number of tokens you get per amount of compute you throw at it Thank you. is like one order of magnitude. So two order of magnitude, too bad. And so, like, is it worth the extra... effort to get div tokens, for us it is because we are completionist. Right? For them, it's like I'll take X trillion tokens. So that's one. Now I do think this is a Core.
[25:00] part of every agent. My world view is that if you are buying LLMs. for doing work. for 9 out of 10 use cases you will want them to have access. to the web and create search infra. optimizing for agents. So it is a real adjacency. for all kinds of LLM. inference. And that supports your view that model companies could, should have the best in class infra for it. So now, they can build it or they can buy it and that's the conversation and we will see who builds and who buys and who partners and how things evolve. Are you partnering with any of the model companies that you can share? We want to, we will. Mm-hmm. I can't share anything on that. We did announce, and I don't know your definitions of model companies, we announced today actually, that we are working with Google Cloud. to be a search and grounding provider for their enterprise agent APIs. So if you think of grounding Gemini models or other models available on GCP, when you build agents on GCP or chat apps on GCP or do any other inference with LLMs on GCP, when you want to attach web search to it, uh Your options... R. Google search or parallel search and Parallel search is product integrated. The integration is optimized, we've spent time with technical teams and training teams and product teams and commercial teams to make sure that when people use Gemini models with parallel. like they get exceptional and great results. So yes, there are these partnerships now. emerging, I bet that there will be several of these. they will all look somewhat unique. That's a big deal from the search king. Congratulations. Google's the original NeoLab. I don't know how to frame Google as a model lab versus a hyperscaler. And I don't know what precise lessons to learn from this one, whether it applies to other labs or to... Hyperscalers And so we will see. The way that I use voice agents and I need to get a reservation for dinner at night, what restaurants should I go to? And then that request gets fulfilled. by the agent. When we talk to a lot of the parallel customers, there's this you know, background agent, whether the monitor product, these agents that sort of are always watching the world or watching the Web. And when something happens, then they go off and take actions and do something with it. It might be worth, because if we think about what does 1000x more mean, there's like the depth of research and then there's just like the... What is actually initiating the tasks? Is it a human initiating the search or is it an agent itself? You want to talk about that dynamic a little bit? Yeah. So, There's a bunch of dimensions here. Let's go back to for a moment on search agents, right? If you run a typical search agent and I even without doing deep research, It'll do somewhere between 5 to 20 searches, even if it answers within a few seconds. Thank you. because why not? So already if you transition from using a ChatGPT, Medium, or I don't know all the categories, but like somewhere not on the high tier, like Instant Low Medium. Every time you write a prompt to it in ChatGPT, it will do five to ten searches. As you dial it up, it will do hundreds and thousands of searches. So one interesting thing to observe is like a human action to a multiplier on number of searches that happened, right? So just by using an AI app. you're kind of multiplying your way to perhaps one order of magnitude more searches. Now, A lot of our initial takes on the product and the market were to go after bigger multipliers than even that. So we were much more interested when you said I have a Thank you. portfolio of 10,000 small businesses where I have given out credit to. for all of them, every month. I have this human process that runs. to feel out how my risk is going up or down. Now, can we... and it relies on a bunch of web data. We're trying to use agents for doing this. So here a developer is effectively the multiplier there is hundreds of thousands or a million in terms of the number of web searches that happen because a human goes
[30:00] programs that instead of now doing this process every month, We can do it every week. So, doing a lot of searches, when this agent runs every week Du. create a dashboard on the portfolio and a collection of action items that somebody needs to look at. Right? Now you can go to another example which is even more interesting. Do you use something to do meeting prep documents for you all that's an agent there's a sequoia one there's a sequoia agent yeah yeah i was i was gonna say james flynn but he's one of our great young guys So I use... Notions agent and you can build custom agents which look into all the internal data that we have a parallel plus all of the web data using Parallel's APIs. to Create meeting prep docs. One time I went and created one prompt to build this custom agent. Now it does. tens and hundreds of web searches for every meeting I have. Every time I build a new agent for a new use case, that keeps multiplying. So I think the path to these background agents doing more and more and more work. all the time for us, it's only going to be bounded by value versus spend. You know, like I don't think it's rational right now. Like I'm probably spending more on it than I should be. but it's not too much, so I don't care yet. So there'll be some rationalization in all of these agents. But I think we will deploy background agents to the extent that there is incremental value in doing that compute. And the same thing applies to searches. All of these background agents would do a bunch of searches. And so our first set of products were really obsessively focused on these. in part because we were building, growing the index and we decided that our company was based on three dimensions. quality cost latency and for the first couple of years we said Let's focus. Let's ignore latency and let's just nail the other two. Because optimizing systems, distilling to smaller models, is much more known art? than unknown research. So once we achieved the best quality search and search agent products. at every price point. we started working on latency. And that's what we shipped with a product we call Turbo now. It is the... fastest highest quality agentic web search. on the market by lot. Do you think there are more agentic queries than human queries on the web now? I don't think yet. Just given some of the multipliers you mentioned and given the background agents, it seems... I don't have to remind you, but we are early. We are very early in agent adoption. You go step outside of our bubble People haven't heard the word 'fable'. So we are very, very early. I think there are now... People like me who are probably operating at the 1000x. I don't know. What do you think? How many Google searches a day did you do three years ago before Charged GPT. 20, 30? Yeah, I would have guessed something like 20, 30. I think today, if you just look across at all of my agents, like... I bet they're doing thousand X more than that. Maybe. 100 to 1000. if you count some of the things that happen at my company which isn't like assigned to a human it might easily be more than a thousand X but I think we are the outliers rather than the So I think we're very, very early on this journey. I do think I recently saw, I think it was Cloudflare that said that in their monitoring of web traffic, the AI traffic is about the same as human traffic. in terms of page reads, which is slightly different from searches. because it includes perhaps all crawlers that are out there. and a bunch of other stuff. But I think it's... It's going to happen. So maybe this is a good segue to talk about a topic that I know you are passionate about, which is... the economics of the internet as we know them. Some of the fundamental assumptions there, human eyeballs, scarcity of attention, seems to be falling right in front of us right now. Are the economics of the internet broken now and what's going to happen? Yeah, no, I think this was perhaps... part of the thing that totally convince me that this needed to be done by me and build parallel. I know most people hate ads. I used to
[35:00] do ads and build systems for ads. I love ads. Oh wow. I love shopping. Okay. So you get good ads. I don't know if I love ads but I intellectually love ads because ads is the reason that so much amazing content and technology. is available for free. to all of us. Google search wouldn't be free without ads, Twitter wouldn't be free without ads. And these are truly useful pieces of technology. a lot of content on the web out there. that we can access for free. Wouldn't be free. if not for ads. And so ads is a very efficient monetization scheme. It's a very efficient monetization scheme. because it is exceptional at differential pricing. Right? So, Most queries. Google loses money on. Some of them make it up and it's an extraordinary business with extraordinary margins. Same with Twitter. Most users... Exactly. You're welcome. I'm subsidizing the free information you guys are getting. You are subsidizing all of us. Thank you. But I think ads is extraordinarily efficient at differential pricing and monetization on the web, which is why it has been a dominant business model. Now, the core assumptions, as you noted, going into it around... limited human attention to translate. into outcomes. If humans don't show up and their agents show up on the web, Like what does this? mean? How does the business work? and yeah I think this was the If we don't figure out a new business model, we are seeing it already right, like people are gonna say, okay I don't want my content to be accessed by an agent. because I have a business model for humans. So I actually want to go... pay someone to SEO, optimize myself so more humans show up. But then if their agent shows up, I'm going to cut it off. Which seems... confusing and disconordinate. Like, okay, ultimately this agent is acting on behalf of a human. But we haven't found business model alignment in a way that... You can't monetize that visit. You can't monetize that visit. So let's say you... And in the business, subscriptions. So, you get a thousand humans and you convert 20 of them into monthly subscriptions. Right? You don't know how that loop works yet with agents. You can't distinguish, you don't have statistics, you don't know if these will lead to subscriptions, if they'll just keep stealing your content. as nameless agents. And so there are real challenges around the old business models breaking. and us not figuring out real scalable new business models. So if you own high quality content and you currently... Put it on the web. Your one available business model pre-parallel was two. be in the head and be able to transact with the lab on some fixed fee contract. That's literally which includes some amount of training and liability and then the inference time axis. That was your one option. That option is not available to most content on the web. It's a very head phenomena and even for the head It is a broken... business model because... when AIs or inference grows, let's say 7x this year. and another 7x the next year. on this 50x. their deal size is not going 50x. None of them, after signing a two-year deal, believes that their share isn't going to decline materially at renewal. And so... These are like fixed price constructs in the world of AI infants. and so which doesn't drive for sustainability. for all of these businesses. Now, Our solution is trying to learn all the lessons from my work at ADS. on having transacted, like I sold Twitter data to OpenAI. having transacted on that side. to figure out what actually might work and be incentivized. So what might work? Efficient differential pricing. paying for differentially a lot for extraordinarily high value content. paying a lot for high value work accessing the same content? So it's differential in both dimensions, quality and value of work being done with it. and... a way of doing this scalably and not just with bespoke deals. So, those are the properties needed for any reasonable solution. And the biggest property of It all is
[40:00] incentive alignment, right? Like at what point do people want to collaborate into this enterprise. Why do the model companies need to pay anything at all? You should ask them. my understanding. is... one you want, fresh data during inference time to be able to display it in products like ChatGPT or Cloud. Do you want training data? And 3. You want some liability protection. for training that you already did. *sniff* And so the payments are some combination. of these three. Thanks. And I can't. be sure of like how they value each of these three. You said even a very simple query will go do 10 searches? And so how do you do attribution between all the different sources that, you know, boil down to one paragraph response? Yeah, at parallel we like to build models. I heard so no I think it's a it goes back to my point around incentive alignment so what are you let's before we try to build a model let's try to figure out like if you were going to try to do this intellectually theoretically how would you go do it So you have to ask the question of, okay, how much incremental value did somebody's content add. right? So you can You can run all of these simulation exercises. One piece of content out. of the corpus. And then you say, let's run the agent. Let's see if the quality of our outputs declined. How much? To Claw back that quality, perhaps if I threw a little bit more compute or a better model in some way Could I claw back that quality? Oh I could, it cost me a cent. Huh. I could get The quality I lost by not having this source My alternative was to throw more compute. a cent worth of compute. to get that same quality. It might be a different result, but as far as the end customer value is concerned, it's the same quality. And so you're like, okay, this source is worth close to a cent, feels like, right? That's intuitive. Now, the formalization of this kind of an intuition... is the core framework we use, it's called Shapley Values. yes let's go what's a Shapley value it's music's my ears it's a game theoretic you're you're a bunch of game theory yeah yes Shapley value is this very theoretical mathematical concept. It is used in sharp values and feature importances for those who are ML folks here. Let's say the three of us collaborate on something, and the whole is bigger than the sum of parts. in that moment. The theoretical question is, okay, how do I divide up this sort of bigger pie that we created by collaboration? So all three of us have incentive to collaborate, right? And Shapley values is a mathematical way of effectively answering this question. Now, that sounds amazing, right? Like you could, if you're co-founders, you could figure out how to divide equity. Unfortunately, it's not that useful. It's not that useful because in order to compute Shapley value, you need to simulate all words where some subset of the two of us collaborated, but the third one doesn't. And play out those realities to then impute back to today in terms of how we should divide the pie, which in practice you can't do. most places. In ML models, when you do feature importances, you kind of can. You can hold a feature back, Run your model and see how well it did. In web search, we can run simulations of if we did not have access to this URL or this domain or this collection of them, How would the agent perform? We can, if you're good at evals, if you're good at assessing quality, you can build that data by running various scenarios. Collect a bunch of this data. and then you can trained models to... Your favorite thing. Favorite thing. So, the challenge with Shapley values is computing Shapley values in our context. Thank you. is way more expensive than the amount of dollars... we spend on the agent, forget the amount of dollars we want to pay a publisher. Right? So to compute a content owner, to compute that a content owner gets a dollar, if I decide to do the full Shapley value computation, that might take several dollars. So it doesn't make any sense. except you can really well estimate them if you build the right kind of data and models around it. but we have confidence that our estimations are good and that This is sound theoretically that If there was perfect information symmetry, people would want to collaborate. So the same way in the old ads days, people
[45:00] Second price auctions and believed, for better or worse, that people would reveal their true bits. in an ad auction and end up paying less than that. uh Once feedback loops get established in a market, like today everything is like an autobit, right? Like most people are measuring ROI when they're doing advertising and running on autobid instead of making up bids. I think, a solid foundation based on incentive alignment that Chaplin Mad drives. will ultimately maximize participation. of content owners. into this. as well as content seekers via AI. in an optimized system. And we have some positive evidence to support it. Like we've had some interesting partnerships that we've been able to do and announce. And yeah, like imagine... sitting with content owners and explaining Shapley math. Takes a moment. But ultimately once Once you pull out the properties, right, that you participate in the value, if you have unique differentiated data. you get paid more. if a banker in an expensive job reads your data versus my retired dad reads your data. . the banker ends up paying more for that REIT. because it's a part of high value work. Thank you. and The macro math also seems to work. Like if you're going to spend a lot of money on inference on LLMs for knowledge work, If we allocated a like what 2-10% of it. to data on the web. That's way bigger... than all, Web data business models. today. outside of like Waldgarden's like. Facebook and LinkedIn. The macro math supports it. It is a scalable approach. And as... agents on the web grow an order of magnitude year on year It's like by my calculations, like we're... 12-24 months. from This Math. being able to give meaningful dollars for a very wide range of content owners on the web. That's very exciting, especially at a time when, you know, you see the traffic data, the stack overflow, plummeting, you see a lot of the human internet as we know it. going away because of incentives, that's very exciting to see how you're thinking about incentive alignments for people to keep publishing. Yeah, it's why we've tried the company. Why is this company called Parallel? the company's original land? Was Shapley Inc. Really? It was. Do you know this? I knew that, yeah. When I incorporated, I'm telling you, I was obsessing about everything to do with the problem space. So while knowing that the first set of Also one. Shaplink is a terrible name for a B2B product. It was not going to be the long-term name. So we... But I incorporated it as Shapley Inc. for lack of a better word. And Shapley.ai happened to be available. Shabli.com? is a parked pond domain. So, It was not going to be a name. I went around not talking about my company at Shapley. and my badges at all events used to call it NUCO. or stealth company? And it took us almost six, eight months to figure out what the real name of the company will be. We end up at parallel in part because it, Click. One, at the time we are doing a lot more in parallel. And two, we started visualizing this sort of a parallel web built for AIs and how its properties are different. And this metaphor that when you publish, you're now thinking of, as we all are now, of two audiences. Okay, I'm gonna create a page. I know humans will read it What should it look like to them? And then how should I make sure that agents can read it to So it feels like you're dual publishing to two audiences. And so we had this like this parallel web for agents will emerge. And so that's why we Started liking battle. Love it. I was just thinking about this recently with the... you know, things like earning transcripts, right? Like I feel Very confident that more people are consuming earnings transcripts through agents than are actually certainly listening to the audio and honestly probably reading the transcript itself So there are these very high value portions of the web that have flipped already to being agent first and obviously the communication
[50:00] has not yet flipped. Um, But I think if I were a public company CEO, today and I was doing an earnings report I'll make very clear that the thing that I'm saying will be transcribed and interpreted correctly by the agents, not just by people listening. Theoretically, yeah. Same for us when we're publishing docs for our APIs. Like, it's like our customers are... building AI solutions. They are using AIs to do it. It's there. Agents... Reading our docs. End quote. in RFD case. It's not humans fumbling around docs pages for the most part. So... In fact, for us, the primary audience is a agent and that's how we test our docs. A parallel web for agents. That's very cool. Maybe close us out. Tell us, just give us a snapshot of where Parallel is today and... If everything that you hope... To build comes true. What does parallel look like? What does the world look like? What's your role in it? I think of... three levels in this journey. Level 1 is people are building simple agents that use the web more as like a tool, like a web search tool, because it's familiar. Because the first set of agents we built, to your point, was just like model and give it the same tools, because these models have been trained. to use all the tools humans have been used to and let them do work. By and large, if you think of most work, it's there. today of our influence it's there today. We have now started seeing some subset of customers who are in this world where They're building more sophisticated, multi-agent systems which use sub-agents and have agents wake each other up or orchestrate in interesting ways, right? People are seeing that as sub-agents, most familiar one is sub-agents with encoding agent harnesses. But we see a lot more of that. Like if you're building an AI scientist, some of those systems are very interesting, very sophisticated, very long running. And like, just... throw large amounts of compute and data at a really hard problem. And I think the third layer for the web specifically is... The web goes from pull to push. So today by and large across the first two modalities I described either an agent isn't calling a tool or a subagent. But it is telling it a request saying, go find this for me. Right now. And I think where we will... end up. in a couple of years. is a variety of use cases will be The web. Parallel. Call me. If this happens, so that My agent can do some work or a human can do some work. So... I use this line with my team all the time, which is like, imagine like agents are everywhere and they can do a lot of things. Right? Thank you. Is there something you can do today? and it's worth doing. And we still have GPUs available. We'll just go do it. We won't be like, oh, let's just do this tomorrow for the sake of it. If it can be done today, do it. So what will we do tomorrow? We will do it tomorrow. work. In response, to something that circles through either another agent's work. or something changes in the world, as visible in satellite imagery, or some... customer commentary that happens, some agent finishing some compute, a human having a new insight to trigger work. But there are going to be a few feeds like this, which will drive new... agentic work tomorrow. And one of those fields, is going to be everything that changed on the web. Which... is really exciting for me because then you are framing not a point-in-time need. but a long term Here is what is actionable for me If something like this happens as evidenced by all of the information on the web, That is changing all the time. Call me. and then I'll run my agent on it. And so we get to then allocate Compute! onto the entire web, all the time on behalf of all the customers. And that's really exciting. That's awesome. Really ambitious vision. You're clearly extremely passionate about this and exciting to see you building. Thank you so much for joining us today, Parag. And thank you for joining us, Andrew. You're very welcome, Sunya. Thanks, Parag. Thank you, Andrew, for your debut. So
[55:00] Thank you.