Merge's Universal Context Layer is an enterprise feature inside Merge for Workforce that gives every AI tool or agent employees use a shared, permissioned view of company knowledge. It syncs and vectorizes data from company systems ahead of time so an agent queries a pre-indexed knowledge base instead of firing a live API call for every question, with connectors for file storage, ticketing, and HRIS at launch . The result is that a marketing hire opening Claude, or an analyst opening a different assistant, arrives with the same institutional context a colleague already taught into a separate tool, without re-uploading files or re-explaining internal systems.
The launch matters because token spend has become a real budget line and most of it is wasted rediscovering things the company already knows. Merge frames runaway token cost as a symptom of a broader problem, where employees spend as much of their day setting up AI tools with the right context as they do actually using them to get work done . Because the context layer knows which tools and skills fit a task, an agent reaches for the right ones instead of probing tool after tool, and each request runs under the employee's own permissions so an agent sees only what that person would see . The layer follows a team to whatever AI tool or agent they adopt next, running with the same data access as the employee using it .
Merge was founded in 2020 by Shensi Ding and Gil Feig , and is best known for its unified API for customer-facing integrations. This release extends that integration DNA inward, positioning Merge alongside its Unified, Agent Handler, and Gateway products as infrastructure for production AI covering context, tools, and models . For operators evaluating how to govern internal AI usage across a growing stack of assistants, it is a concrete alternative to per-tool prompt libraries and one-off retrieval setups.
Comments (14)
Sign in to join the discussion.
P
Priya RaghavanSep 10, 2026
The jump cut at 0:14 where you show the marketing deck reusing the design tokens is chef's kiss. Whoever edited this understood the assignment, but the voiceover levels dip hard in the second half.
T
Tomasz BielinskiSep 10, 2026
A context layer is just institutional memory with better marketing. Still, most companies can't even keep their Notion tidy, so good luck.
L
Linh PhamSep 10, 2026
Cool, but what's the API surface look like? Asking specifically about rate limits and whether context writes are idempotent when two agents update the same key.
M
Miho TanakaSep 10, 2026
Docs or it didn't ship. Where do I POST my first context blob?
A
Amara OkaforSep 10, 2026
Been telling portfolio founders this exact thesis for months. Every AI wrapper is one context layer away from being actually useful.
B
Bastien RouaultSep 10, 2026
The wordmark tracking in the hero shot is loose enough to drive a truck through. Otherwise the palette actually slaps.
N
Nizar El-AminSep 10, 2026
Happy to chat off the record about the design partners you're working with. No pressure, just curious about the enterprise angle.
R
Rohan D.Sep 10, 2026
'Substantially decreases token cost' is doing a lot of work in that sentence. What's the eval setup and which model family are we talking about?
Y
Yolanda MeyerSep 10, 2026
Cute demo but who owns the context when the designer quits? The governance story is where MLOps tools go to die.
W
Wiktor NowakSep 10, 2026
Every hire teaching the model from scratch is the org chart equivalent of goldfish memory. This framing is genuinely sharp.
C
Chidera NwosuSep 10, 2026
Third context layer launch this quarter. The category is heating up and honestly the tweet copy here is the strongest of the bunch.
R
Rajat BhattacharyaSep 10, 2026
12k views and the reply ratio is unusually high for a Tuesday infra launch. Something about the 'every company uses AI wrong' hook is doing numbers.
K
Kenji AlvaradoSep 10, 2026
Universal context layer sounds a lot like a shared knowledge graph and shared knowledge graphs sound a lot like something that wants to be onchain. Just saying.
C
Cassia FontaineSep 10, 2026
Who's leading eng here and are you hiring forward deployed? Got a candidate coming off a Ramp tour who eats context problems for breakfast.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Merge
The connectivity layer for AI
The connectivity layer for AI
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Merge's Universal Context Layer is an enterprise feature inside Merge for Workforce that gives every AI tool or agent employees use a shared, permissioned view of company knowledge. It syncs and vectorizes data from company systems ahead of time so an agent queries a pre-indexed knowledge base instead of firing a live API call for every question, with connectors for file storage, ticketing, and HRIS at launch . The result is that a marketing hire opening Claude, or an analyst opening a different assistant, arrives with the same institutional context a colleague already taught into a separate tool, without re-uploading files or re-explaining internal systems. The launch matters because token spend has become a real budget line and most of it is wasted rediscovering things the company already knows. Merge frames runaway token cost as a symptom of a broader problem, where employees spend as much of their day setting up AI tools with the right context as they do actually using them to get work done . Because the context layer knows which tools and skills fit a task, an agent reaches for the right ones instead of probing tool after tool, and each request runs under the employee's own permissions so an agent sees only what that person would see . The layer follows a team to whatever AI tool or agent they adopt next, running with the same data access as the employee using it . Merge was founded in 2020 by Shensi Ding and Gil Feig , and is best known for its unified API for customer-facing integrations. This release extends that integration DNA inward, positioning Merge alongside its Unified, Agent Handler, and Gateway products as infrastructure for production AI covering context, tools, and models . For operators evaluating how to govern internal AI usage across a growing stack of assistants, it is a concrete alternative to per-tool prompt libraries and one-off retrieval setups.
Comments (14)
The jump cut at 0:14 where you show the marketing deck reusing the design tokens is chef's kiss. Whoever edited this understood the assignment, but the voiceover levels dip hard in the second half.
A context layer is just institutional memory with better marketing. Still, most companies can't even keep their Notion tidy, so good luck.
Cool, but what's the API surface look like? Asking specifically about rate limits and whether context writes are idempotent when two agents update the same key.
Docs or it didn't ship. Where do I POST my first context blob?
Been telling portfolio founders this exact thesis for months. Every AI wrapper is one context layer away from being actually useful.
The wordmark tracking in the hero shot is loose enough to drive a truck through. Otherwise the palette actually slaps.
Happy to chat off the record about the design partners you're working with. No pressure, just curious about the enterprise angle.
'Substantially decreases token cost' is doing a lot of work in that sentence. What's the eval setup and which model family are we talking about?
Cute demo but who owns the context when the designer quits? The governance story is where MLOps tools go to die.
Every hire teaching the model from scratch is the org chart equivalent of goldfish memory. This framing is genuinely sharp.
Third context layer launch this quarter. The category is heating up and honestly the tweet copy here is the strongest of the bunch.
12k views and the reply ratio is unusually high for a Tuesday infra launch. Something about the 'every company uses AI wrong' hook is doing numbers.
Universal context layer sounds a lot like a shared knowledge graph and shared knowledge graphs sound a lot like something that wants to be onchain. Just saying.
Who's leading eng here and are you hiring forward deployed? Got a candidate coming off a Ramp tour who eats context problems for breakfast.