Michael Grinich, founder and CEO of WorkOS, presents auth.md, an open spec built on OAuth standards that lets AI agents autonomously register for software services. He argues that as agents choose tools on their own, traditional signup flows—forms, CAPTCHAs, API-key copying—block legitimate agents, and that MCP auth still requires a human in the loop. A live demo shows an agent discovering Cloudflare's auth.md, proving its identity with ID-JAG, obtaining a temporary account, and deploying an app without human signup. Topics also include what an auth.md file declares, why payment should follow usage rather than precede signup, and the shift from human-in-the-loop to autonomous workflows. Recorded at the AI Engineer World's Fair 2026 in San Francisco. # Video Identity Observations ## Source **Title:** *Auth for Agents: Let AI Sign Up for Your Product with auth.md — Michael Grinich, WorkOS* The material is a conference-style talk (Moscone venue referenced) delivered by **Michael Grinich**, self-identified in the transcript: > "My name is Michael Greenwich. I am the founder of work OS" *(Note: the auto-transcript renders "Grinich" as "Greenwich" and "auth.md"/"a.md"/"OMD"/"AMD" inconsistently throughout; the title supplies the canonical product name.)* ## Intended Audience Evidence points to a **developer / SaaS builder / startup audience**, not end consumers: - Direct address to engineers and product builders: *"if you're a service provider, if you're building APIs or services, this allows you to become a customer of those systems."* - Calls to action framed for businesses: *"you should be building for agents as well as people," "go out and build with AMD."* - Assumes familiarity with developer ecosystems: Y Combinator ("Make something people want"), MCP, Wrangler/Cloudflare, PLG ("Just like with PLG or Premium before that"), SSO, CAPTCHAs, "harness engineering." - Closing frames the audience as peers in a platform shift: *"I think together we can build for this next exciting era of software."* ## Claimed Scope - **Industry-level thesis:** agents are a platform shift — *"Agents are the next big thing," "agents are the next big wave,"* compared explicitly to the iPhone launch (2007). - **Specific problem claim:** agent registration is a missing primitive — *"the first step of an agent actually signing up for a service is actually missing. It hasn't been solved and it's a huge blocker."* - **Deliberately narrow product scope:** *"We're not solving the whole problem around agent identity... We're just trying to solve this narrow one around registration."* - **Growth/business framing:** *"this is the way to grow your business and get more customers," "an immediate growth boom for your products."* ## Self-Description Evidence - **Founder-led vendor presentation:** Grinich presents WorkOS's own proposal (auth.md) with a live demo and a Cloudflare collaboration — *"We actually have this working as a live demo. We did some collaboration with Cloudflare on this too."* - **Positioning as open, not proprietary:** *"It's an open spec. WorkOS doesn't control it... no single vendor owns this. It's one click enabled if you use our stuff, but you can build it on whatever platform you want."* - **Ecosystem affiliation claims:** *"Probably more than anybody, I'm a big MCP fan. We've done a bunch of events in San Francisco around MCP."* ## Distinguishing Claims vs. Demonstration - **Creator claims** (not independently demonstrated here): agents as "the next consumer class," "There will be more agents in the future than people, maybe even today," Salesforce quote *"Our API is the UI"* (attributed to Marc Benioff). - **Observable presentation pattern:** the talk demonstrates a single-vendor pitch wrapped in open-standard rhetoric — an inherent tension the material itself acknowledges but does not resolve. - This is one video; no channel-wide conclusions (publishing cadence, content mix) can be drawn from it alone. # Delivery Observations — Michael Grinich, "Auth for Agents" ## Overall Style Conversational, high-energy conference keynote. Combines industry framing, analogy-heavy teaching, a demo walkthrough, and a closing historical appeal. Pacing is quick, with frequent rhetorical questions addressed to the audience. ## Recurring Vocabulary & Phrases - **"Agents"** saturates the talk — used dozens of times, almost every paragraph. - **"In the loop" / "human in the loop"** — repeated framing device: > "you as a human are in the loop. There might be cruise control, but you're still in the loop." > "authentication through MCP requires your human to still be in the loop." - **"Agent native"** — a signature coinage: "agent native registration," "agent native signup experience," "not really agent native." - **"The door is not open" / "open the door for agents"** — recurring metaphor for registration access. - **"Boom"** as a demo beat: > "Get the identity assertion. Boom, boom, boom. Go through." > "receives back the access token... and then boom it's it's done" - **"Huge" / "big wave / next big thing"**: > "Agents are the next big thing." > "I think agents are this agents are the next big wave." ## Teaching Habits - **Extended analogies**: cars/autonomous vehicles (deleting the interface), an LLM as "a V8 engine" needing a chassis and drivetrain ("the harness"), and a "smartest person you know" dropped into a company where they "can't really get anything done." - **Enumerated lists**: the five things agents need (runtime, tools, context, feedback, human review); the agent-registration requirements (discoverability, capability declaration, intent, risk, identity verification, org identity, entitlements, auditability). - **Historical/industry framing**: Y Combinator's "make something people want" revised to "making something that agents want"; iPhone launch in 2007 as a platform-moment parallel; Benioff/Salesforce quote used as social proof. - **Rhetorical questions to the room**: > "Does anybody prompt their agents like this? It's just like yes, yes, do it, please." > "What do agents need to be successful?" ## Persona & Audience Relations - Self-positioning as an insider and enthusiast: "Probably more than anybody, I'm a big MCP fan... Love MCP." - Direct audience address: "Shout out to those of you in the front row"; offers his email: "that's actually my email if you want to email me." - Self-deprecating casualness about the demo: "It's not exactly rocket science." ## Structural Pattern Classic pitch arc: **trend context → problem framing ("Your business probably isn't open for agents today") → named gap ("There's a missing primitive") → solution (auth.md) → demo → business payoff ("immediate growth boom") → historical call to action ("build for the agentic revolution")**. ## Uncertainty / Isolated Moments - The self-aware joke "because markdown files are the future, right?" appears once; unclear whether such humor recurs across his talks. - "Boom" and "in the loop" repetition is clearly observable within this talk, but whether these are stable habits across other presentations cannot be established from this single transcript. - Transcript has gaps and garbles (e.g., "[731] often do you can answer what does the service do"; "o.md"/"A&D"/"AMD" inconsistency), so some quoted phrasing should be treated as approximate to the audio. # Observation Record: "Auth for Agents: Let AI Sign Up for Your Product with auth.md" — Michael Grinich, WorkOS ## Speaker Identification The only speaker identified in the transcript is **Michael Grinich** ("My name is Michael Greenwich [as transcribed]... I am the founder of WorkOS"). All positions below are his unless otherwise noted. --- ## Positions on the Shift to Agentic Software Engineering - **Coding workflows have transformed.** He describes an evolution from human-in-the-loop prompting, to "Ralph loops" automation, to today's pattern where "you write a single prompt and then the agent can spit out a lot of code," sometimes running "for not minutes but... hours and hours or even days and days." - **The human bottleneck has moved.** "The limiting factor here, really the bottleneck is your brain" — how much parallel agent work a person can supervise at once. - **He no longer writes code by hand:** "I don't write code by hand anymore. Probably you don't as well." - **Agentic workflows will spread beyond engineering.** He claims what happened in software engineering "is going to come to a lot of different categories" and "Agents are the next big thing." - **Autonomy analogy:** He uses autonomous vehicles to argue that interfaces get deleted for humans — citing his own Waymo experience ("after about 3 seconds, I pulled out my phone and started scrolling X"). ## Positions on What Agents Need Grinich lists five requirements for agent execution: 1. A **runtime/sandbox** ("safe, secure, performant") 2. **Tools** to act in the world 3. **Context** (compared to "the smartest person you know" dropped into an unfamiliar company) 4. **Feedback** mechanisms to validate work 5. **Human review** (code review, evals) - He frames the LLM as an **engine** needing a "harness" (chassis, transmission, etc.), and asserts "harness engineering is this new domain" — "if the models get better but you don't have a good harness, it's not going to be very effective." ## Positions on Agents as Consumers - **Agents are already choosing vendors:** "today actually it might be more important to build for agents than to build for people. Agents are kind of this new consumer class." - He proposes updating the Y Combinator slogan: "I think it's time to maybe edit this a little bit... we also need to think about making something that agents want." - **Speculative but stated with hedging:** "There will be more agents in the future than people, maybe even today." ## Core Problem Claim: Missing Agent Registration - **"Your business probably isn't open for agents today... The door is not open."** He identifies "agent registration" as "a missing primitive" — "that first step of an agent actually signing up for a service is... a huge blocker to getting adoption." - **The web is structurally hostile to agents.** "For the last like 20 years, maybe 30 years, automated traffic on the web has been bad. We've tried to block all of it." He notes the login box is hardened against agentic registration "not intentionally, but just because of the legacy systems." - He observes the irony of browser-execution environments selling CAPTCHA-breaking as a feature: "which is pretty wild. You know, we're trying to go backwards." - **Signup flows assume humans:** reading landing pages, filling forms, solving CAPTCHAs, verifying email, choosing plans, copying API keys, using dashboards. "It's kind of a human interface, not an agent interface." - **Agents need:** native discoverability, capability declaration, registration intent, risk assessment, identity verification (with or without a user's identity attached), organizational identity, entitlements, credential issuance, auditability. ## Position on MCP - **"I'm sorry to say MCP is not enough."** He qualifies this heavily: "Probably more than anybody, I'm a big MCP fan," noting WorkOS runs MCP events. - His reasoning: "MCP is great for connecting, for providing tools, skills, context, but it doesn't solve the registration step. Today, authentication through MCP requires your human to still be in the loop." ## The auth.md Proposal - **Definition:** "OMD tells agents how they can become legitimate users... this is what you need to do to sign up and be considered legit." - **Deliberately scoped narrow:** "We're not solving the whole problem around agent identity, you know, permissions, long duration... We're just trying to solve this narrow one around registration... Let's start small and grow from there." - **Built on existing standards:** "built on existing standards instead of inventing a crazy new religion." He references **ID Jag** ("the identity JSON access grant... essentially a signed credential that represents the user"). - **What it communicates to agents:** what the service does, how to register, accepted identity proofs, OAuth/SSO/MFA flows, scopes and entitlements, free-tier constraints, and "how does the human get involved later? A human or an organization claiming it afterwards." - **Flexible, not one-size-fits-all:** "One size does not fit all... If you're building something that's like a database service... you might want to give away a little bit of traffic for free. But if you're building something maybe like an email service or... if you access the physical world, you maybe don't want to give anything away for free." - **Scope limitation preserved:** "OMD is just for the registration step. Your normal API keeps working. The rest of your docs don't have to change." - Demonstrated (with Cloudflare collaboration) an agent signing up and deploying end-to-end with the human only approving: "there's nothing actually that I was doing through prompting it other than just approving, approving, approving." ## Positions on Payments and Growth - **Usage-first, payment-downstream:** "Where there's usage, we believe there's also intent to pay... We don't want payments to be upfront. We don't want to have to force your agent to sign up with a credit card. That seems backwards. We moved away from that in the world of SAS." - He acknowledges uncertainty: "I'm not saying everything that agents are going to build will be useful. Maybe not everything they build will go into production or last that long, but some things will." - Compares agent-driven growth to PLG and premium models as a growth channel. ## Cited Supporting Evidence - **Marc Benioff / Salesforce** (quoted): "Our API is the UI. Entire Salesforce and Agentforce, Slack platforms are now exposed as API, MCP, and CLI." Grinich uses this to argue even "legacy SaaS" vendors are going agent-first. - **Steve Jobs / iPhone (2007)** as the last comparable new software platform: "there hasn't really been a moment like this since... I think agents are this. Agents are the next big wave." ## Openness / Non-Ownership Claim - "It's an open spec. WorkOS doesn't control it. We have a version of it that we host, but you can build it yourself... I think this is so important that no single vendor owns this." --- ## Unresolved Tensions Preserved - He asserts agents may outnumber people "maybe even today" while hedging ("I'm not saying everything that agents are going to build will be useful"). - He criticizes the agent-economy risk while still urging adoption ("If you don't build for the agent economy, your product might not win") without resolving how to reliably distinguish good from bad agents beyond "risk assessment" and "identity verification." - MCP's insufficiency is framed as a scope gap, not a flaw — the human-in-the-loop consent remains for MCP auth as he describes it. # Speaker & Provenance Record ## Video Overview - **Title:** *Auth for Agents: Let AI Sign Up for Your Product with auth.md — Michael Grinich, WorkOS* - **Video ID:** 01a15ca6-785c-7d6a-a31a-d35547c4c973 ## Speakers & Roles | Speaker | Role | Basis | |---|---|---| | **Michael Grinich** (transcript spelling: "Michael Greenwich") | **Creator / Presenter — Founder of WorkOS** | Self-identified: "My name is Michael Greenwich. I am the founder of work OS." | | Steve Jobs (referenced) | Third-party figure, not a speaker | Cited only as historical anecdote (2007 iPhone introduction); no audio of him in transcript. | | Marc Benioff (transcript: "Mark Beni off") | Third-party quoted figure | Quoted via slide/quote: "Our API is the UI" — described as CEO and founder of Salesforce. | No guests, narrators, or interviewers appear; the video is a **single-speaker conference talk**. ## Referenced Sources & Third-Party Claims - **Y Combinator / Paul Graham** — cited for the phrase "Make something people want," which the speaker proposes extending to "making something that agents want." - **Salesforce / Marc Benioff** — quoted as believing agents are the future; claim that Salesforce platforms are "exposed as API, MCP, and CLI." - **Cloudflare** — named as a **collaboration partner** for the live demo of agent registration; also named in the flow diagram. - **Fire (transcript: "fire call")** — mentioned as another service the registration flow works with. - **Named tools/products:** Whimo (Waymo), Wrangler, Claude/"clot", Pi harness, "open claw", PostHog, MCP, X42 (crypto payment protocol, transcript spelling), ID Jag / "identity JSON access grant" (transcript spellings). - **Historical reference:** Steve Jobs' iPhone introduction, January 2007, Moscone — framed as an analogy for agents as "the next big wave." ## Promotional Segments — Flagged - **Promo flag:** The talk is substantially promotional for **auth.md (transcribed as "o.md"/"A&D"/"OMD")**, a spec proposed by the speaker's company WorkOS. Claims of "immediate growth boom" and "this should be huge" are the speaker's own marketing framing. - **Promo flag:** Speaker encourages adoption: "If you want to use this, this is available today. We have open spec for it. There's a GitHub repo." - Claim that "WorkOS doesn't control it" / "no single vendor owns this" is the speaker's own characterization and unverifiable from the transcript. ## Cited Sources & Evidence Availability - **Referenced but not provided in-transcript:** - A **live demo** (Cloudflare collaboration) shown visually; only described verbally. - A **GitHub repo** and **open spec** for auth.md — named but no URL given. - Slides/graphics of the registration flow — referenced ("here's a little kind of cartoon demo"), not present in text. - **Comment availability:** No information about comments, Q&A, or audience interaction availability is present. - **Transcript quality note:** Several proper nouns are phonetically garbled (e.g., "Michael Greenwich" vs. Grinich per title; "o.md"/"A&D"/"OMD" inconsistently for auth.md; "Whimo"; "fire call"; "X42"; "ID Jag"). Identity of exact spellings rests on the title metadata, not the transcript. ## Uncertainty Notes - Speaker's surname spelling: transcript says "Greenwich," title says "Grinich" — **title metadata treated as authoritative**. - Products/services referenced (Cloudflare, Fire, PostHog) are named as integrations/demonstrations; the depth of those relationships beyond the stated Cloudflare collaboration is not specified. Hello everyone. Good morning. My name is Michael Greenwich. I am the founder of work OS and I'm here to talk with you today about agents and specifically about how we can make agents more autonomous and allow them to access more services on the web. So let's jump in and get started. Shout out to those of you in the front row also. I see you out here. So about a year ago, software engineers were writing code like this. We were using AI, but we would prompt it and then we would write a little bit of code and then prompt it again and it would write some more code. And you would continue to do this human in the loop interactive software engineering. Later in the year, we had things like Ralph loops, if any of you remember those, where we kind of automated this. More or less this is the way that we were working. It was this human agent human agent back and forth. However, as the models got better and better, they were able to write more and more code and run for longer periods of time. And so today, a lot of software engineering looks like this. You write a single prompt and then the agent can spit out a lot of code. And sometimes it can actually build a whole feature, maybe even a whole product and maybe run for not minutes but uh hours and hours or even days and days. This has really transformed the way that we all write code. I don't write code by hand anymore. Probably you don't as well. And it's not just this one thread. You can actually parallelize this. So there's many different tools out there including, you know, the major code coding harnesses from the labs that allow you to run many of these in parallel. The limiting factor here, really the bottleneck is your brain. How much context do you can keep in your mind to keep all of these going at once? And this has transformed software engineering. People can be more productive. I think we've all seen in the industry how much faster things are moving. At the root of all of this is actually agentic engineering agents going from these token prediction language models to reasoning and now longunning processes that can actually do things autonomously for us. And what I think we've seen in software engineering here around agentic workflows is going to come to a lot of different categories. It won't just be engineers that have this way of working. It'll be people in many different fields. Agents are the next big thing. I think a good reference for this, a way to think about it is actually what's been happening with vehicles. So, you know, this looks like a pretty modern car. It has a, you know, digital display on it. This is probably what you would have bought in the last, you know, 5 to 10 years. But if you live in San Francisco or one of the cities with these autonomous vehicles, you've probably seen that we're starting to delete the interface. No longer do you get inside of the car and actually, you know, pull up your phone and get maps where you as a human are in the loop. There might be cruise control, but you're still in the loop. Instead, these are autonomous systems. You just say where you want to go, you get in the car, you don't even say anything, and it just takes off and takes you to your destination. I remember the first time I got into a Whimo, I was blown away, mind totally blown. And then after about 3 seconds, I pulled out my phone and started scrolling X. It became common place. And I think we've seen this already happen with engineering. The power of agents allows us actually to work and think at a higher level for us to, you know, exercise more of our executive function versus just planning and execution. There's a question here of what do agents need to be successful? Actually, when they execute, what do they need? Well, first they need a runtime, a sandbox. They need somewhere that they can run that needs to be safe, secure, performant. They also need tools. They have to be able to go do stuff in the world. An agent's not very useful if it can't take actions. So, it needs tools. Third, it needs context. You know, these new models with the power of the intelligence in them, it's kind of like taking the smartest person you know and dropping them into a company or a project or a team where they don't know anything, they can't really get anything done. They need to have context, information about the system, information about the goals. They need feedback. So a way that they can actually run and validate that they can check that their work is correct and if it's not correct keep going. And last but not least of course they still need human review. This might be code re review. This might be other forms of evals. This might be forms of checking their work to make sure that these agents are sort of aligned with your goals. The LLM the intelligence engine this new technology we've created in the last last few years you can think of as like an engine. It's like a really high performance. You know, I think this is a a V8 engine. You know, puts out a lot of horsepower. It can convert fuel into, you know, output. But an engine by itself isn't very useful for a car. You need to drop this into the actual car itself. You need the chassis, you need the transmission, you need the drivetrain, you need the wheels. And only with all of that is it going to be effective to take you places. And this is what a lot of people refer to as the harness. Harness engineering is this new domain where if the models get better but you don't have a good harness you know it's not going to be very effective so as the models improve we change our harnesses we adapt them to it and those things that I mentioned earlier are sort of a form of a harness so agents execute within these harnesses to get stuff done and they they need all those elements to actually be effective and when they drive they drive really really fast so say you have one of these agents that's going off you prompt it to go build something for So, you know, it spins for a while. It says, "Okay, I'm going to need this feature and this feature and I'm going to need a database and I'm going to need, you know, this editing uh, you know, system to deploy and I'm going to need, you know, maybe this thing for image resizing or video transcoding or sending email or whatever." And your agent can actually go do all this research and build all these systems. And today, what's happening with agents is they're actually selecting vendors. You've probably seen the rise of some of these systems where you know like the CEOs will tweet about their growth graph and it really takes off and it's because agents are picking them. They're picking their systems for sending email or deploying code. Their systems for storing data today actually it might be more important to build for agents than to build for people. Agents are kind of this new consumer class. I'll talk about that in a bit. There's this uh kind of popular thing that people say in San Francisco Silicon Valley. Make something people want. This comes from Y Cominator, you know, the startup factory from Paul Graham. And I think it's time to maybe edit this a little bit. And going forward, we also need to think about making something that agents want. There will be more agents in the future than people, maybe even today. They'll be faster to spin up. They'll do things quicker. They'll be making decisions on our behalfs. And so, if you want to build for the next era of consumers, you should be building for agents as well as people. But there's a problem today. You can access the web. You can access mobile. But agents themselves can't really access systems. Your business probably isn't open for agents today. Even though there's a lot of them out there, they can spawn very quickly. The door is not open. And we think this is because there's a missing primitive. Agentic registration, agent registration. There's a lot of great stuff around agents connecting and bringing context to systems and different open source frameworks, but that first step of an agent actually signing up for a service is actually missing. It hasn't been solved and it's a huge blocker to getting adoption. For the last like 20 years, maybe 30 years, automated traffic on the web has been bad. We've tried to block all of it. And so there's all these systems that we've put in place to detect automated actors and stop them in their tracks. DOS prevention, credential stuffing, and attacks. The login box, for example, is very hardened against agentic registration today. Not intentionally, but just because of the legacy systems of what we built. And it's very hard to distinguish between what's a good automated user versus a bad automated user. If any of you have used any of these like cloud-based uh browser execution environments, one of the selling features they often have is to break captures, which is pretty wild. You know, we're trying to go backwards. The capture today though is is still kind of dead. There's rampant abuse. There's lots of token fraud. And so, we need to find a better way to allow the good agents in and then block the bad agents, right? Because like I said earlier, if you don't build for the agent economy, your product might not win. It might not be successful. Today's signup flows assume that a human can read the landing page, that they can fill out a form, you know, put their email address, their password in it, that they can solve a capture, that they can verify their email, not just put it in, but go click something somewhere. Remember, an agent probably doesn't have an email address. If it's signing up for a service, it needs to have a, you know, a human can choose a plan to pay for it. You know, human can copy the API key out, paste it somewhere, use it somewhere else, and really even a dashboard. Think of a dashboard experience. It's not really agent native. All this stuff is built for people. It's kind of a human interface, not an agent interface. Agents need something else. They need native discoverability. Can they register for a system? Are the doors open for agents or not? Capability declaration. What can it do? Registration intent. Why are you registering? What are you trying to do within this? Or the intent to actually just sign up. There's a lot of stuff around risk here. So for an agent native registration, maybe you want to you're not sure if the agent signing up is going to be good or bad. So you need to actually do a risk assessment of that. There might be different forms of identity verification for an agent. If something like claude is going and signing up, maybe it can bring the user's identity with it or if you have a you know open claw or like your pi harness or something else, maybe it doesn't bring the user's identity and gets verified out of band. There's the whole thing around organizations doing this. So if I'm building something within a company, how does my company identity come in? You know, my organization, entitlements, permissions, credential issuance, auditability, the list goes on. There's so many things that need to be changed. In fact, probably most things need to be changed going from, you know, human registration to agent registration, agent native systems. I'm sorry to say MCP is not enough. Probably more than anybody, I'm a big MCP fan. We've done a bunch of events in San Francisco around MCP. I see somebody wearing one of our run MCP shirts up here that we made. Love MCP. MCP is great for connecting, for providing tools, skills, context, but it doesn't solve the registration step. Today, authentication through MCP requires your human to still be in the loop. You give consent. You add an MCP server, say for Post Hog to Claude, you sign in with your Post Hog credentials. What we're talking about here for agent native registration needs to happen without the human involved or at least not involved initially. So we've been working on this for a while and our proposal. This is a new spec we have called o.md because markdown files are the future right? Well, how does this actually work? What is o.md? Well, the idea here is that OMD tells agents how they can become legitimate users. It's a set of instructions that tells an agent registering for a service, this is what you need to do to sign up and be considered legit and for me to give you access. And the goal here is to give these service providers, you know, people that are building building services an agent native signup experience, but it's built on existing standards instead of inventing a crazy new religion or something really complicated. With OMD, we're not solving the whole problem around agent identity, you know, permissions, long duration, you know, connective services. We're just trying to solve this narrow one around registration because I think it's a huge blocker. Let's start small and grow from there. This is built on open standards. It's built on a bunch of work that's already been done across the OS specifically tailored to that registration step. often do you can answer what does the service do tell agents how to register it can tell them what identity proofs are accepted how to how how an agent or user is proving their identity what offflows are supported can you sign up with SSO or email address or MFA what scopes and entitlements can exist kind of what capabilities are here what free tier constraints apply you might have a system where you want to give an agent a little bit of free capacity but not too much until they verify or pay in some Okay. And then of course, how does the human get involved later? A human or an organization claiming it afterwards. So an agent can sign up, but you want the human to have custody later on. This is what A&D is designed to solve. These are the main questions around the registration step. So how does this actually work? Well, here's a little uh kind of cartoon demo that I'll show you. And all this works, by the way, you can go try it after this. So say I'm here in u whatever coding harness or system I'm using pi or clot or something and it says welcome back Michael at work OS that's actually my email if you want to email me do you want to keep working on your spelled app like yeah sure I'd like to share this with my friends but they can't access it and the agent's like oh well local host only works on your machine so your friends won't be able to hit it of course to share it I need to deploy it somewhere real some providers actually let me handle the sign up so you know you wouldn't have to sign up and do this you want me to look Yes, please agent look for services that advertise through author here does have an OMD and so the agent here can say ah Cloudflare that's the one cloudflare is a winner because I can go sign up for it I can access the service I can actually use it so I can do the whole thing you want to go with it yeah Let's do it. This is the registration step. This is kind of where the magic happens. What my agent is actually doing is minting an identity assertion and giving that to Cloudflare. And then Cloudflare is able to verify that or not. Cloudflare can choose actually to verify out of band. AMD is very flexible. There's different ways you can dial it in depending on the behavior that you're looking for. One size does not fit all. Every application is different. Constraints are totally different. If you're building something that's like a database service where there's going to be very little amount of information, you might want to give away a little bit of traffic for free. But if you're building something maybe like an email service or something certainly if you access the physical world, you you maybe don't want to give anything away for free. It's very application specific. So here Cloudflare says, "Okay, we're willing to let you deploy maybe for 72 hours or something like that. Get the identity assertion. Boom, boom, boom. Go through. It's called ID Jag is what the standard is." And then it returns back and says you're set up with a Cloudflare account. Now in this experience, my you know human I didn't go click anywhere. I didn't sign up anywhere. It just it just got the token. I can make a couple small tweaks. It knows how to use Wrangler. Want me to make those changes? Go ahead. Does anybody prompt their agents like this? It's just like yes, yes, do it, please. Not really saying much. It's able to write the Wrangler, get the thing set up, go through the full deployment process, and then boom, it's live. We actually have this working as a live demo. We did some collaboration with Cloudflare on this too. It's pretty cool. And you can tell the prompting that I was giving through this not exactly rocket science. The agent could just run through the whole thing. Actually, there's nothing actually that I was doing through prompting it other than just approving, approving, approving. It should be able to do this one shot. This is what it looks like graphically. So agent registration with OMD, you have your agent harness pi for example. within that is your LLM, maybe your memory, different, you know, context layers. It connects to your backing identity service. So this is the user identity. And when that agent goes and registers, it sends the discovery call to Cloudflare. It looks for that aund or whatever service. We also have this working with fire call. It's pretty cool. It sends that ID Jag, the identity JSON access grant. It's essentially a signed credential that represents the user says this is an identity receives back the access token actual API token and then boom it's it's done you can make normal API requests you can call MCP everything else still works so you can see that OMD is just for the registration step your normal API keeps working the rest of your docs don't have to change it's just that registration step for agents but with the simplicity comes actually an enormous amount of power because suddenly it lets agents do things end to end. I hate the planning step. When I write something, I just want the agent to go do it. Usually it kind of knows what I'm trying to get at and I want to come back to actually a running prototype and not like, hey, here's my long plan. Here's a bunch of services to sign up for. If I'm building new prototypes, especially, I would prefer it just to get deployed on something for free so I can see it and click around and not put me through the burden of going sign up for all these different vendors. And that's what OMD allows for. And if you're a service provider, if you're building APIs or services, this allows you to become a customer of those systems and you can think about it increasing your growth funnel starting from, you know, maybe just humans and adding the whole world of agents on top. Pretty great. We think this is going to be huge. Your door will be open for agents to actually sign up, register, use your services. This should be an immediate growth boom for your products. And I'm not saying everything that agents are going to build will be useful. Maybe not everything they build will go into production or last that long, but some things will. Just like with PLG or Premium before that, this is the way to grow your business and get more customers and actually become, you know, larger and more successful. And where there's usage, we believe there's also intent to pay. There's a lot of interesting work being done for agents to actually pay for stuff. There's crypto-based protocols like X42. There's other things that the payment providers are building, but we think that should be downstream. We don't want payments to be upfront. We don't want to have to force your agent to sign up with a credit card. That seems backwards. We moved away from that in the world of SAS. With OMD, agents can sign up, they can register, they can start using it and then downstream choose to pay on your terms based on your own pricing, based on your own model. If you don't believe me or on the headless type of products, this is Mark Beni off. He's the CEO and founder of Salesforce, the guys at the big building here in town. They believe in agents more than anything. Our API is the UI. Entire Salesforce and agent force Slack platforms are now exposed as API, MCP, and CLI. Talk about going agent fork first. A company that many people consider to be sort of a legacy SAS vendor really invented the category of software as a service. They're getting rid of their dashboard and UI. I mean, they're not getting rid of it, but they believe that agents are the future. So, if you're not thinking about this, I definitely encourage you to start building some prototypes, talking to users, because you don't want to miss miss this. If you want to use this, this is available today. We have open spec for it. There's a GitHub repo. You can actually have your agent go implement it. I know it's kind of meta. It's an open spec. Work OS doesn't control it. We have a version of it that we host, but you can build it yourself. You can run it yourself in your existing systems. I think this is so important that no single vendor owns this. It's one click enabled if you use our stuff, but you can build it on whatever platform you want instead. Last thing I'll close with, this actually happened almost 20 years ago, I think actually here at Moscone, which is pretty awesome. in uh January of 20 uh 2007 I believe Steve Jobs introduces iPhone and I was in college and I remember or yeah like first year of college I remember this super super clearly. It was the next great software platform that got built. So many companies got started because they could build on top of these devices. smartphone revolution and there hasn't really been a moment like this since I think in the the era of technology at least for me the stuff we did around B2B SAS and cloud and all that is great but this was a totally new paradigm a new software platform and I think agents are this agents are the next big wave and so what I would say to all of you is go out and build with AMD we're hoping to unlock this for you unlock this for your business and for your growth but we want to hear from you here the places you get stuck and I think together we can build for this next exciting era of software and build for the agentic revolution. Thank you so much