Sodium is a drop-in layer that converts the actions already inside a website (search, checkout, account settings, dashboards) into WebMCP tools, so AI agents can find and invoke those features directly rather than scraping the DOM. It targets SaaS and internet businesses that want to be reachable to browser-based agents without rebuilding their app around a separate API surface. The launch matters now because WebMCP is a browser-native standard for connecting AI agents to web page interfaces that runs client-side, inside the browser, announced by Google's Chrome team and co-developed with Microsoft through the W3C Web Machine Learning Community Group , and sites need a fast path to expose tools before agents start routing users somewhere else.
The pitch is control and efficiency. Today AI agents interact with sites by reverse-engineering them, giving operators no say in how they navigate, what they extract, or what actions they take, while WebMCP flips that by letting the site define which tools are available, what parameters they accept, and what they return . Sodium wraps that model in a two-minute install and reports a 2.82x speed improvement and 91x token reduction against agents parsing raw pages, aligned with published WebMCP benchmarks showing large token and latency gains versus HTML-parsing baselines.
Sodium ships from Result, a Y Combinator P26 company building one workspace for running a business, spanning AI chat, a Company Brain, marketing, a provisioned backend, customer support, and finance . The founders, Aaryan Kushwah and Savio Martin, are college dropouts and multiple-time founders who have sold over 25 SaaS products, consumer apps, and internet media companies , and Sodium slots into their broader thesis that the next generation of internet companies need to be legible to agents by default.
Comments (8)
Sign in to join the discussion.
N
Nadia BoroumandAug 30, 2026
Sodium, Result, WebMCP... I opened three tabs trying to figure out what the actual company is called. The naming tree is doing acrobatics.
P
Purav GuptaAug 30, 2026
The tweet buries the lede. "Turns existing site features into agent tools with a 2 minute setup" should have been line one, not Sodium the mystery element.
T
Tomas K.Aug 30, 2026
2.82x faster than what baseline though? That decimal precision on a vibes benchmark is doing a lot of heavy lifting.
B
Bong-su ChoiAug 30, 2026
Every MCP launch this month has claimed Nx token efficiency with a different N. At some point one of you has to define the denominator.
O
okwuchiAug 30, 2026
Staff eng question: is the demo hitting a live agent or a recorded run? Would love to see it fumble a real checkout flow before I believe the token numbers.
L
Linnea L.Aug 30, 2026
"The new home for internet businesses" is so vague it could sell insurance. Try: "Your website, but agents can actually use it."
R
Reyhaneh DavariAug 30, 2026
Naive q from someone still learning MCP: what happens when the site's features change? Does the agent silently break or do you version the tool exposure?
M
Marcelo AmaroAug 30, 2026
Compliance hat on: if agents are now transacting on behalf of users through my site, whose ToS applies and where does the audit log live? Not a gotcha, genuinely need to know before I ship this.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Result
The new home for internet businesses
The new home for internet businesses
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Sodium is a drop-in layer that converts the actions already inside a website (search, checkout, account settings, dashboards) into WebMCP tools, so AI agents can find and invoke those features directly rather than scraping the DOM. It targets SaaS and internet businesses that want to be reachable to browser-based agents without rebuilding their app around a separate API surface. The launch matters now because WebMCP is a browser-native standard for connecting AI agents to web page interfaces that runs client-side, inside the browser, announced by Google's Chrome team and co-developed with Microsoft through the W3C Web Machine Learning Community Group , and sites need a fast path to expose tools before agents start routing users somewhere else. The pitch is control and efficiency. Today AI agents interact with sites by reverse-engineering them, giving operators no say in how they navigate, what they extract, or what actions they take, while WebMCP flips that by letting the site define which tools are available, what parameters they accept, and what they return . Sodium wraps that model in a two-minute install and reports a 2.82x speed improvement and 91x token reduction against agents parsing raw pages, aligned with published WebMCP benchmarks showing large token and latency gains versus HTML-parsing baselines. Sodium ships from Result, a Y Combinator P26 company building one workspace for running a business, spanning AI chat, a Company Brain, marketing, a provisioned backend, customer support, and finance . The founders, Aaryan Kushwah and Savio Martin, are college dropouts and multiple-time founders who have sold over 25 SaaS products, consumer apps, and internet media companies , and Sodium slots into their broader thesis that the next generation of internet companies need to be legible to agents by default.
Comments (8)
Sodium, Result, WebMCP... I opened three tabs trying to figure out what the actual company is called. The naming tree is doing acrobatics.
The tweet buries the lede. "Turns existing site features into agent tools with a 2 minute setup" should have been line one, not Sodium the mystery element.
2.82x faster than what baseline though? That decimal precision on a vibes benchmark is doing a lot of heavy lifting.
Every MCP launch this month has claimed Nx token efficiency with a different N. At some point one of you has to define the denominator.
Staff eng question: is the demo hitting a live agent or a recorded run? Would love to see it fumble a real checkout flow before I believe the token numbers.
"The new home for internet businesses" is so vague it could sell insurance. Try: "Your website, but agents can actually use it."
Naive q from someone still learning MCP: what happens when the site's features change? Does the agent silently break or do you version the tool exposure?
Compliance hat on: if agents are now transacting on behalf of users through my site, whose ToS applies and where does the audit log live? Not a gotcha, genuinely need to know before I ship this.