WEBVTT

NOTE Sentence-level transcript of https://www.youtube.com/watch?v=JvKO40CFq-s

NOTE One cue per sentence. Cue ids are the line anchors on /transcripts/JvKO40CFq-s.html. A cue ends where the next begins, or 2 s after its last word.

s1
00:00:12.800 --> 00:00:14.240
Well, hello everyone.

s2
00:00:14.240 --> 00:00:15.280
Can you hear me all?

s3
00:00:15.280 --> 00:00:15.839
Okay.

s4
00:00:15.839 --> 00:00:16.720
Yes.

s5
00:00:16.720 --> 00:00:17.920
Perfect.

s6
00:00:17.920 --> 00:00:22.080
Well, welcome to our talk, our workshop actually.

s7
00:00:22.080 --> 00:00:26.240
Um, I know maybe you were expecting uh Burgett also.

s8
00:00:26.240 --> 00:00:29.760
he couldn't come but we make this workshop together for you.

s9
00:00:29.760 --> 00:00:30.720
Okay.

s10
00:00:30.720 --> 00:00:42.559
So as you see you have there a QR code you can go ahead and go there is um our page for Asian health protocol so that you have it and I don't have to spell it for you.

s11
00:00:42.559 --> 00:00:43.520
Um, okay.

s12
00:00:43.520 --> 00:00:54.160
So, my whole idea today is instead of like me telling you stuff and you do this and show you how to do stuff, I want us to take one hour

s13
00:00:54.160 --> 00:01:02.960
at least to think about Asian security, Asians because sometimes we are excited about like this new AI era, right?

s14
00:01:02.960 --> 00:01:09.280
But we never think about or maybe yes, but not as much as I wished.

s15
00:01:09.360 --> 00:01:27.119
What happens when you for example say hey agents what are my maybe my schedule for tomorrow what are send an email have you ever thought of this how many of you like raise your hand like how many of you use AI agents every day

s16
00:01:27.119 --> 00:01:39.040
okay higher don't be shy okay great how many of you give them access to your Gmail to your calendar to your personal accounts how many of you oh so much less Okay.

s17
00:01:39.040 --> 00:01:43.520
The ones that do like what do you do like you connect an MCP server?

s18
00:01:43.520 --> 00:01:43.920
Okay.

s19
00:01:43.920 --> 00:01:44.799
Yes.

s20
00:01:44.799 --> 00:01:45.920
And they have another one.

s21
00:01:45.920 --> 00:01:46.880
Good.

s22
00:01:46.880 --> 00:01:52.159
Maybe you connect like your personal token to like endpoint.

s23
00:01:52.159 --> 00:01:52.799
Okay.

s24
00:01:52.799 --> 00:01:56.159
So what happened when we do this?

s25
00:01:56.159 --> 00:02:03.439
We're actually doing like the agent is acting on behalf of us but pretending to be us.

s26
00:02:03.439 --> 00:02:07.360
So do you think that's a good idea?

s27
00:02:07.360 --> 00:02:08.479
Yes or no?

s28
00:02:08.479 --> 00:02:11.280
Who thinks it's a good idea?

s29
00:02:12.800 --> 00:02:13.680
Not a great idea.

s30
00:02:13.680 --> 00:02:15.680
Why?

s31
00:02:20.400 --> 00:02:20.959
Exactly.

s32
00:02:20.959 --> 00:02:24.879
And why we didn't thought about this like before.

s33
00:02:25.200 --> 00:02:25.520
Okay.

s34
00:02:25.520 --> 00:02:26.560
So it doesn't matter.

s35
00:02:26.560 --> 00:02:27.120
Here we are.

s36
00:02:27.120 --> 00:02:28.720
We are thinking about it.

s37
00:02:28.720 --> 00:02:36.400
I always remember uh the time like when internet came like I'm almost 40 so I remember and everybody was so happy about it.

s38
00:02:36.400 --> 00:02:49.760
But then started to question like okay everything the whole data is public it's like we are in the same moment today right like we are really excited about AI and then after we start to think about security

s39
00:02:49.760 --> 00:03:03.200
but it's good so why I put there hire your agent the analogy I want you to think about let's say you have a company or a part of a company and you hire someone

s40
00:03:03.200 --> 00:03:08.080
do you give them you need them to have access two things of the company, right?

s41
00:03:08.080 --> 00:03:13.519
So, what you do with these people when you showing or when you show, what did they give to you?

s42
00:03:13.519 --> 00:03:15.519
You have a your own email, right?

s43
00:03:15.519 --> 00:03:18.720
Your own access, your own credentials.

s44
00:03:18.959 --> 00:03:25.120
So, if you think about it in Asian world, what are we doing without agents?

s45
00:03:25.120 --> 00:03:27.920
We are it's like we are doing like the CEO credentials, right?

s46
00:03:27.920 --> 00:03:31.200
You never say like, okay, this is the credentials of CEO, go and read the email.

s47
00:03:31.200 --> 00:03:34.239
No, because everything anything could happen.

s48
00:03:34.239 --> 00:03:35.280
This is the same.

s49
00:03:35.280 --> 00:03:43.440
The idea will be hire your agent in a sense of give them your agents authority instead of your credentials.

s50
00:03:43.440 --> 00:03:45.519
Do you think it's a good idea?

s51
00:03:45.519 --> 00:03:45.920
How?

s52
00:03:45.920 --> 00:03:47.287
Yes or no?

s53
00:03:47.287 --> 00:03:48.000
[laughter]

s54
00:03:48.000 --> 00:03:48.319
Okay.

s55
00:03:48.319 --> 00:03:57.680
My idea is like I know sometimes um we could be shy but I want I think it would be nice like we can interact a bit because it's a moment

s56
00:03:57.680 --> 00:04:04.319
that thanks to a engineer and all of us being here all of your time we can get together and think about something.

s57
00:04:04.319 --> 00:04:05.680
I think it's not common, right?

s58
00:04:05.680 --> 00:04:08.000
So, make 100% off of it.

s59
00:04:08.000 --> 00:04:09.680
Um, okay, great.

s60
00:04:09.680 --> 00:04:13.840
So, did you all got the page there, the QR codes?

s61
00:04:13.840 --> 00:04:14.319
Yeah.

s62
00:04:14.319 --> 00:04:16.160
Great.

s63
00:04:16.160 --> 00:04:24.320
So, remember like my idea of saying, "Okay, agent read my emails, right?"

s64
00:04:24.320 --> 00:04:27.600
Have you ever thought like how the agent gets to there?

s65
00:04:27.600 --> 00:04:30.560
How it gets to your email?

s66
00:04:30.880 --> 00:04:37.520
First of all, how do Asians know what they can do?

s67
00:04:39.360 --> 00:04:41.360
Huh?

s68
00:04:46.240 --> 00:04:46.880
Okay, great.

s69
00:04:46.880 --> 00:04:48.560
So, you you do it by hand, right?

s70
00:04:48.560 --> 00:04:51.280
It's not that something automatic.

s71
00:04:53.840 --> 00:04:54.960
Yes.

s72
00:04:54.960 --> 00:04:56.560
Exactly.

s73
00:04:56.560 --> 00:04:58.240
But

s74
00:04:58.240 --> 00:04:58.800
Exactly.

s75
00:04:58.800 --> 00:05:01.520
But some huh

s76
00:05:01.520 --> 00:05:03.360
exactly context window also too.

s77
00:05:03.360 --> 00:05:08.720
But you always somehow connected something to the Asian that okay this is what you can do right.

s78
00:05:08.720 --> 00:05:19.520
So what if we have like an ideal world or that can go to maybe a directory and say oh this is the whole thing I can do and this is all the things I can execute.

s79
00:05:19.520 --> 00:05:22.479
That would be a smartest idea right?

s80
00:05:22.479 --> 00:05:25.120
Have you ever used a phone book?

s81
00:05:25.120 --> 00:05:26.320
Yeah right.

s82
00:05:26.320 --> 00:05:33.039
this is safe like who I can call so I go and look in the phone book and then I have how to call it I have the number they will be the same

s83
00:05:33.039 --> 00:05:44.479
what what I want to do and how do I call it so that's is our first problem discovery how agents discover what they can do and the idea will be it will be an automatic

s84
00:05:44.479 --> 00:06:00.400
way not just us all the time telling how and connecting and stuff right then also there's another part it would be nice to tell the agents or like grant Asians

s85
00:06:00.400 --> 00:06:15.280
what they can do and we're not but really specific the ones that connected the Gmail accounts maybe they all gave them read access right just read so we can I don't know don't send or like not remove anything so it's more safe

s86
00:06:15.280 --> 00:06:25.919
okay but what if you have so many important uh information there that then if the agent something gets um wrong and somebody else can read your data it's good either.

s87
00:06:25.919 --> 00:06:28.319
It's not safe in any way.

s88
00:06:28.319 --> 00:06:40.800
So what if we can get all these what the agent can do all these tools as he mentioned and you can grant access to every tool like this yes this no this

s89
00:06:40.800 --> 00:06:56.000
reading is okay that would be a better idea right so we think about authorization to that agent not like to act behalf of me and have everything I can do then the agent can do it's like going back to the higher

s90
00:06:56.000 --> 00:07:08.479
example that a person like I just hired has all the same access that the CEO or maybe you hire have an assistant uh or a friend that do something for you like in your real life

s91
00:07:08.479 --> 00:07:22.639
you will never give your access to all your things right and if you do you change them after so this is the same thing and also okay we have an ideal world when agents can discover what they can do

s92
00:07:22.639 --> 00:07:28.560
then we can tell them what they can do or not but how do we trace them down.

s93
00:07:29.599 --> 00:07:35.360
How do we trace today what the apps do on our behalf when you authorize them?

s94
00:07:37.360 --> 00:07:39.360
Huh?

s95
00:07:39.759 --> 00:07:40.319
Exactly.

s96
00:07:40.319 --> 00:07:41.280
Audi logs.

s97
00:07:41.280 --> 00:07:50.720
So perfect audification, right?

s98
00:07:50.720 --> 00:07:54.479
Which agent did what on behalf of which user.

s99
00:07:54.479 --> 00:07:58.400
In order to do that, that comes to our main thing.

s100
00:07:58.400 --> 00:08:01.199
Give the agent's identity.

s101
00:08:01.199 --> 00:08:05.199
If we have if every agent has identity, we can trace them down.

s102
00:08:05.199 --> 00:08:09.840
We can know what agent did what when in behalf of which user.

s103
00:08:09.840 --> 00:08:13.440
It seems like it's so much so much better, right?

s104
00:08:13.440 --> 00:08:23.680
And also what else you can do when you can trace someone regarding to the whole hiring thing, you can fire them if they do something wrong.

s105
00:08:23.680 --> 00:08:29.599
You can revoke access in the same way the agent will be revoked if you know who they are.

s106
00:08:29.599 --> 00:08:33.680
If something were wrong with today's things, you have to disconnect the whole thing, right?

s107
00:08:33.680 --> 00:08:35.839
Yes or no?

s108
00:08:35.839 --> 00:08:38.000
So imagine have Oh, this same up.

s109
00:08:38.000 --> 00:08:39.039
Sorry for the word.

s110
00:08:39.039 --> 00:08:40.560
You can't remove it.

s111
00:08:40.560 --> 00:08:41.519
That's it.

s112
00:08:41.519 --> 00:08:42.800
So we have tracibility.

s113
00:08:42.800 --> 00:08:45.839
We have the whole thing.

s114
00:08:47.040 --> 00:08:47.839
Okay.

s115
00:08:47.839 --> 00:09:01.680
So as it come out as a sum up we have the discovery issue where the agent can go find the service and read the capabilities authorization what this agent can do can do scope down and

s116
00:09:01.680 --> 00:09:12.171
who is this agent are you on board with this do you think it's a good idea you have any questions like champion okay great

s117
00:09:12.171 --> 00:09:12.959
[snorts]

s118
00:09:12.959 --> 00:09:18.080
have you ever heard of a capabilities raise your hand Yes.

s119
00:09:18.080 --> 00:09:18.640
Okay.

s120
00:09:18.640 --> 00:09:21.760
Do you all know what a capability is?

s121
00:09:21.760 --> 00:09:24.000
Who doesn't know?

s122
00:09:24.000 --> 00:09:24.480
Okay.

s123
00:09:24.480 --> 00:09:25.519
Almost the whole room.

s124
00:09:25.519 --> 00:09:26.720
Okay.

s125
00:09:26.720 --> 00:09:34.720
So the idea of using capabilities is instead of using scopes, you know, like scope is like a big thing.

s126
00:09:34.720 --> 00:09:37.040
For example, we have the read scope.

s127
00:09:37.040 --> 00:09:41.600
So it what what does mean it's like nothing so specific.

s128
00:09:41.600 --> 00:09:46.399
The other capability is what can do, but it's more cap down.

s129
00:09:46.399 --> 00:09:51.040
So I can actually determine what an action agent can do.

s130
00:09:51.040 --> 00:09:58.560
So the idea is going back to the example I put in the beginning.

s131
00:09:58.560 --> 00:10:06.399
Let's say you talk to the AI in the chat and you say, "Okay, give me my emails from the last week."

s132
00:10:06.399 --> 00:10:10.640
So the agent has an intent to do something, right?

s133
00:10:10.640 --> 00:10:18.000
It has to be a way that that intent has to be mapped to a tool or maybe several tools.

s134
00:10:18.000 --> 00:10:19.279
So that's kind of the idea.

s135
00:10:19.279 --> 00:10:23.279
The tools will be like capabilities and an intent will be matched to that.

s136
00:10:23.279 --> 00:10:26.480
So that's what we're solving with discoverability.

s137
00:10:27.120 --> 00:10:40.320
If you ever read the the protocol that we are proposing or maybe read it later, you will see um our idea of a well-known Asian configuration endpoint.

s138
00:10:40.320 --> 00:10:44.240
If you know about a little bit about identity, you remember OIDC, right?

s139
00:10:44.240 --> 00:10:55.200
connect these are the same well known and the idea is like to a nation have like a public place to know how they can interact with a service like everything the kind of encryption

s140
00:10:55.200 --> 00:11:05.200
uh etc. So it will be something like this and also a place to list capabilities and stuff.

s141
00:11:06.160 --> 00:11:16.880
But what happened for example in a world like today that we still I hope I hope in the future we adopt this but in the meantime all the services they're still working just with O.

s142
00:11:16.880 --> 00:11:21.600
So how do we do it in the meantime?

s143
00:11:21.600 --> 00:11:27.839
What do we need to agents to be able to know which what they can use from each service?

s144
00:11:27.839 --> 00:11:30.720
Let's say Gmail.

s145
00:11:32.079 --> 00:11:35.760
We can build something like a directory.

s146
00:11:35.760 --> 00:11:43.120
So the idea is um to have something I'm going to see it here.

s147
00:11:43.120 --> 00:11:50.399
So let's say most of the you're familiar for open API open API spec.

s148
00:11:50.399 --> 00:11:51.360
Yes.

s149
00:11:51.360 --> 00:11:52.079
Okay.

s150
00:11:52.079 --> 00:11:58.320
So most of the common services we use they all implement open API.

s151
00:11:58.320 --> 00:12:05.279
So we have like a kind of a place to we as a developers or engineers we can say okay what this service can do.

s152
00:12:05.279 --> 00:12:10.480
So the idea is to use that and convert the two capabilities.

s153
00:12:10.480 --> 00:12:14.880
So at the beginning until we every service is speak.

s154
00:12:14.880 --> 00:12:24.800
So let's say for example do you guys use I don't know tell me a service you use ah

s155
00:12:24.800 --> 00:12:40.959
open AI okay Gmail we have it there but let's say for example let's see if it works open AI open APIJSON and sometimes they have public they have the publics

s156
00:12:40.959 --> 00:12:47.519
but we need like a JSON Uh, I don't see it.

s157
00:12:47.519 --> 00:12:49.040
API opening.

s158
00:12:49.040 --> 00:12:51.120
Okay, I do know.

s159
00:12:51.120 --> 00:12:53.760
I think it's this one.

s160
00:12:53.760 --> 00:12:56.480
No. Well, you know what?

s161
00:12:56.480 --> 00:12:58.079
That were wrong.

s162
00:12:58.079 --> 00:12:58.480
Notion.

s163
00:12:58.480 --> 00:12:59.519
Not has a really good one.

s164
00:12:59.519 --> 00:13:04.880
I wanted to use another one from you guys, but the notion is more reachable.

s165
00:13:04.880 --> 00:13:22.160
So here you see so if you have for example not every service has but the open API JSON what we doing with the protocol is translating this oh I already register it.

s166
00:13:22.160 --> 00:13:25.920
So, I'm going to show you guys.

s167
00:13:26.160 --> 00:13:26.800
Yeah.

s168
00:13:26.800 --> 00:13:29.279
Where is this one?

s169
00:13:29.279 --> 00:13:31.279
Sorry.

s170
00:13:34.800 --> 00:13:37.440
Don't see it here.

s171
00:13:39.120 --> 00:13:40.320
Okay.

s172
00:13:40.320 --> 00:13:41.839
It will form something like this.

s173
00:13:41.839 --> 00:13:44.720
This is like an example, but it's like the same.

s174
00:13:44.720 --> 00:13:49.519
So, you will get all the capabilities from the endpoints.

s175
00:13:49.519 --> 00:13:52.880
You see sometimes you see like a delete again.

s176
00:13:52.880 --> 00:13:58.560
So it would kind of be idea to approach like a middleware to this point.

s177
00:13:58.560 --> 00:14:00.560
Yes.

s178
00:14:01.440 --> 00:14:02.639
Oh, sorry guys.

s179
00:14:02.639 --> 00:14:03.760
Thank you for telling me.

s180
00:14:03.760 --> 00:14:09.199
And okay, here is better.

s181
00:14:09.199 --> 00:14:10.800
Oh, thank you.

s182
00:14:10.800 --> 00:14:12.480
Sorry guys.

s183
00:14:12.480 --> 00:14:13.360
Okay.

s184
00:14:13.360 --> 00:14:19.920
So the idea is to see here it's like you can translate the endpoints to capabilities.

s185
00:14:19.920 --> 00:14:31.120
So because we are still this is just because we still we don't have so much services or let's say none like implementation stuff but the idea is like in the meantime we have something

s186
00:14:31.120 --> 00:14:32.240
that translate this.

s187
00:14:32.240 --> 00:14:34.000
So what this mean?

s188
00:14:34.000 --> 00:14:37.680
It means like let me check.

s189
00:14:39.760 --> 00:14:54.320
It means like you will have something for example do you have there in the agent of protocol you see do you have a directory this directory we have for example

s190
00:14:54.320 --> 00:14:57.920
the Gmail one that we did the same.

s191
00:14:57.920 --> 00:15:02.240
So you see you have for example 20 list of capabilities.

s192
00:15:02.639 --> 00:15:14.720
So the idea is like you grab what the service can do, what is exposing maybe through open or maybe you do it yourself because uh for example maybe you want to automate a workflow.

s193
00:15:14.720 --> 00:15:17.360
So the idea is like everything get list here.

s194
00:15:17.360 --> 00:15:21.040
So the directory will be like a phone directory for the agent.

s195
00:15:21.040 --> 00:15:22.560
Are you following me?

s196
00:15:22.560 --> 00:15:24.560
Yeah.

s197
00:15:27.360 --> 00:15:27.839
The what?

s198
00:15:27.839 --> 00:15:29.440
Sorry.

s199
00:15:29.440 --> 00:15:29.760
Yes.

s200
00:15:29.760 --> 00:15:31.120
I mean it's a good point.

s201
00:15:31.120 --> 00:15:32.240
Did you hear?

s202
00:15:32.240 --> 00:15:33.040
Did you hear him?

s203
00:15:33.040 --> 00:15:34.560
Like fine grain out.

s204
00:15:34.560 --> 00:15:35.040
Okay.

s205
00:15:35.040 --> 00:15:47.199
So the idea is yes in a sense of having the most scope thing as possible but still fine out is still goes like minting a token to the user.

s206
00:15:47.199 --> 00:15:49.199
We want to meet a token for the agent.

s207
00:15:49.199 --> 00:15:51.600
So what we are switching is the principle.

s208
00:15:51.600 --> 00:15:55.040
We now want that the agents are a principal actor.

s209
00:15:55.040 --> 00:15:56.079
But it's a really good thing.

s210
00:15:56.079 --> 00:15:58.000
That's why we inspire on that.

s211
00:15:58.000 --> 00:16:01.600
I think it's one of the best things we can do.

s212
00:16:01.600 --> 00:16:02.399
Okay, great.

s213
00:16:02.399 --> 00:16:19.040
Um so going back to the capabilities the idea is what I just said like having this scope once you have like the readings or like maybe uh just the gets or the deletes or the post like everything is

s214
00:16:19.040 --> 00:16:28.560
quite discerned so you can decide whe you have any questions.

s215
00:16:28.560 --> 00:16:30.560
Yes.

s216
00:16:34.399 --> 00:16:34.800
Yeah.

s217
00:16:34.800 --> 00:16:35.040
Yeah.

s218
00:16:35.040 --> 00:16:36.560
That's that really sucks.

s219
00:16:36.560 --> 00:16:40.399
Uh the idea is you can do it manually.

s220
00:16:40.399 --> 00:16:45.759
You can actually declare everything so in the directory or in the future the agent know how to do.

s221
00:16:45.759 --> 00:16:47.680
It's like less common.

s222
00:16:47.680 --> 00:16:49.920
But yeah, it could happen.

s223
00:16:49.920 --> 00:16:56.480
But the idea is like in in the meantime we do this until services implement these sessions out.

s224
00:16:56.480 --> 00:16:59.191
But yeah, it's a good question.

s225
00:16:59.191 --> 00:17:00.240
[snorts]

s226
00:17:00.240 --> 00:17:12.319
Um okay so remember like our problems right so now we we are trying to get a solution for how like the agents the agents know what they do with the directory

s227
00:17:12.480 --> 00:17:26.720
then we have a way to authorize them through the capabilities and now if you remember we said it was a good idea to get them identity right so what we come

s228
00:17:26.880 --> 00:17:32.400
is giving agents like a private key like famous private key.

s229
00:17:32.400 --> 00:17:38.320
So each agent will have its own and that will be attached to the identity.

s230
00:17:38.320 --> 00:17:44.080
Um so in that sense because every agent has its own identity.

s231
00:17:44.080 --> 00:17:49.440
Now if you I see you want me to put this on light mode too.

s232
00:17:49.440 --> 00:17:52.240
Uh what did you say that before?

s233
00:17:52.240 --> 00:17:55.440
Okay, let's go back to this there.

s234
00:17:55.440 --> 00:17:56.720
That's better.

s235
00:17:56.720 --> 00:17:58.720
Great.

s236
00:17:59.679 --> 00:18:00.880
zoom in.

s237
00:18:00.880 --> 00:18:04.480
Okay, there.

s238
00:18:05.280 --> 00:18:17.360
So now that the agent will have like a access to its own private key, they can sign tokens, they can have like their own metered tokens and everything is encrypted with the private key.

s239
00:18:17.360 --> 00:18:30.080
So what this means like for now on instead of like a service let's say Gmail seeing like a user interacted with the service we can have a log that we actually say

s240
00:18:30.080 --> 00:18:40.400
okay this agent is doing something on my behalf that is connected to the user but it's actually for example agent from cursor or an agent from cloud or an agent from whatever.

s241
00:18:40.400 --> 00:18:42.400
So we are changing the paradigm.

s242
00:18:42.400 --> 00:18:51.200
We stop seeing as an agent is like hiding behind the user and now the agent is there as a principal acting.

s243
00:18:51.200 --> 00:18:56.320
So is is for me was really exciting.

s244
00:18:56.320 --> 00:19:02.640
So do you have any concerns about this private key private key public policy key things?

s245
00:19:02.640 --> 00:19:04.640
Yeah.

s246
00:19:09.360 --> 00:19:10.960
Exactly.

s247
00:19:10.960 --> 00:19:12.080
That's beautiful, right?

s248
00:19:12.080 --> 00:19:17.760
You can say, "Oh, this is not doing what I supposed to be doing, and I go and I revoke it."

s249
00:19:17.760 --> 00:19:18.400
So, it's cool.

s250
00:19:18.400 --> 00:19:25.760
And maybe you can think of like, okay, the the I revoke it, but the access token is still there.

s251
00:19:25.760 --> 00:19:28.160
So, what you can do is like deleting with the GDI.

s252
00:19:28.160 --> 00:19:29.760
So, bye.

s253
00:19:29.760 --> 00:19:31.760
Yes.

s254
00:19:38.160 --> 00:19:39.600
Mhm.

s255
00:19:39.600 --> 00:19:43.919
Always the token always the agents they always have a user they are reporting to you.

s256
00:19:43.919 --> 00:19:45.679
They are never detached.

s257
00:19:45.679 --> 00:19:50.320
So always the the agent is like with a user.

s258
00:19:51.760 --> 00:19:53.760
Yeah.

s259
00:20:01.120 --> 00:20:02.000
Yes.

s260
00:20:02.000 --> 00:20:02.720
Yes.

s261
00:20:02.720 --> 00:20:03.200
Exactly.

s262
00:20:03.200 --> 00:20:18.000
you have like all the information the agent also the host we are in introducing a new thing that is called host that is like the place when you are like creating this agent from so you actually can also delete the host you can say okay this host is not authorized

s263
00:20:18.000 --> 00:20:32.720
so you can see the host you can see the agent ID you can see the user you can see everything okay great more questions okay don't be shy like we are here for this

s264
00:20:32.720 --> 00:20:34.720
Yes.

s265
00:20:39.600 --> 00:20:42.559
Can you speak a little bit higher?

s266
00:20:55.440 --> 00:20:57.039
Yeah, that's a great question.

s267
00:20:57.039 --> 00:21:00.799
Um, actually it's more like an enterprise focus, right?

s268
00:21:00.799 --> 00:21:06.400
So because we did this in February, the things changed so much until now.

s269
00:21:06.400 --> 00:21:08.320
Like for example, Asians are not so ephemeral.

s270
00:21:08.320 --> 00:21:10.880
Maybe you have a forever long Asians, right?

s271
00:21:10.880 --> 00:21:16.159
Or maybe you have two Asians or maybe you have Asian design of a company and they have policies.

s272
00:21:16.159 --> 00:21:20.480
So we are working on that in a new draft and we are addressing that too.

s273
00:21:20.480 --> 00:21:24.480
Um because it's something quite um important to address.

s274
00:21:24.480 --> 00:21:30.960
So yes, I was about to say that in the end, but yeah, we're about to release a new draft with uh if you have this is an open source.

s275
00:21:30.960 --> 00:21:33.919
It's a project that we want to all of us own.

s276
00:21:33.919 --> 00:21:38.799
So if you have some ideas like you reach out like like that one for example, it's really good.

s277
00:21:38.799 --> 00:21:42.080
So we can improve it's good for ourselves and good for everyone.

s278
00:21:42.080 --> 00:21:47.840
And I don't want this to be just like for enterprise just to all of us that use AI that be safe.

s279
00:21:47.840 --> 00:21:50.559
So thank you.

s280
00:21:50.559 --> 00:21:51.679
Okay.

s281
00:21:51.679 --> 00:21:56.720
So that was that was just discussing about the V1 to V2.

s282
00:21:56.720 --> 00:21:58.400
Um great.

s283
00:21:58.400 --> 00:22:04.240
So three layers then one protocol.

s284
00:22:04.240 --> 00:22:05.919
Why we say this?

s285
00:22:05.919 --> 00:22:15.440
Because if you go and in the searching the website you will see we publish like a first version just like a draft or a ancient plugin inside of a draft.

s286
00:22:15.440 --> 00:22:20.000
The idea is you can use this and play around and see what you come up with.

s287
00:22:20.000 --> 00:22:34.000
So in the agent plug-in you can uh use it like on the server side so a server can verify an agent or issue grants or force whatever constraint that you have been doing with that

s288
00:22:34.000 --> 00:22:44.880
also on the SDK side uh we ship it with an MCP so you can connect it to your cloud to try it out you connect it to your whatever you're using course or whatever you're using with MCPS

s289
00:22:44.880 --> 00:22:55.120
and also the other layer is the directory it's just a place like a phone book like where the intent match what the action.

s290
00:22:55.120 --> 00:22:59.120
So intent will be matching the capabilities.

s291
00:22:59.600 --> 00:23:06.799
Um so the idea is that we can see it in action.

s292
00:23:07.200 --> 00:23:15.919
So what we will do if you want you can go to what I shared in the QR code.

s293
00:23:15.919 --> 00:23:19.280
Let's go to the page.

s294
00:23:19.360 --> 00:23:23.039
Okay, you will see a directory there.

s295
00:23:23.039 --> 00:23:25.600
Did you all find the directory button?

s296
00:23:25.600 --> 00:23:29.600
You will you will come into this and you will see a connect button.

s297
00:23:29.600 --> 00:23:31.760
So you have to login first for sure.

s298
00:23:31.760 --> 00:23:36.000
And you will see a connect and then you will see the MCP.

s299
00:23:36.080 --> 00:23:38.240
So you can connect that for example to the cloud.

s300
00:23:38.240 --> 00:23:39.520
I have it here.

s301
00:23:39.520 --> 00:23:44.960
I wanted to to show you guys a bit what we were talking about.

s302
00:23:44.960 --> 00:23:50.880
So let's say we say I'm going to ask for emails.

s303
00:23:50.880 --> 00:23:56.400
Okay, I just did a bunch of demo emails, but I'm going to show it to you guys so I don't show like personal information.

s304
00:23:56.400 --> 00:23:59.440
But for example, I have my NCP connected.

s305
00:23:59.440 --> 00:24:05.840
So you will see something like this uh connectors customize.

s306
00:24:05.840 --> 00:24:10.240
Here you see Asia D. You will see something like this.

s307
00:24:10.240 --> 00:24:23.440
Then you can approve, disapprove, always deny just the Asian D. um MCP and if it's that my idea is like you try it out just with MTP of Asian D. So the agent doesn't have access to other tools.

s308
00:24:23.440 --> 00:24:28.159
So it's like the principal one to see how it interact and how it gets the identity.

s309
00:24:28.159 --> 00:24:37.520
Our whole idea is like when you use this MCP the agent will have an identity we request you for capabilities and we'll try to execute it and you we will see the logs and everything

s310
00:24:37.520 --> 00:24:39.440
um uh running.

s311
00:24:39.440 --> 00:24:41.120
Okay.

s312
00:24:41.120 --> 00:24:48.640
So let's see for example um hey bring me my last email.

s313
00:24:49.279 --> 00:24:56.400
Oh sorry it's going to use the H&L connectors.

s314
00:24:56.400 --> 00:24:59.360
Can you see it's too small?

s315
00:24:59.360 --> 00:25:01.120
It's okay.

s316
00:25:01.120 --> 00:25:03.120
Okay.

s317
00:25:05.440 --> 00:25:05.760
Okay.

s318
00:25:05.760 --> 00:25:16.159
you see is using the because it has the NCP is using the directory to see from my intent of like bring me my last email which capabilities are out there

s319
00:25:16.159 --> 00:25:18.799
and he's asking for approval.

s320
00:25:18.799 --> 00:25:21.840
We are using here device uh device flow.

s321
00:25:21.840 --> 00:25:22.880
Do you know the device flow?

s322
00:25:22.880 --> 00:25:24.000
Are you familiar?

s323
00:25:24.000 --> 00:25:26.000
It's just like it's like connecting a device.

s324
00:25:26.000 --> 00:25:29.919
So we are acting like is a if the agent is another device.

s325
00:25:29.919 --> 00:25:34.400
So you can see uh the agent called is called email reader is that's for default.

s326
00:25:34.400 --> 00:25:36.799
You can change later if you want to.

s327
00:25:36.799 --> 00:25:40.880
It's requesting me to read at least my emails.

s328
00:25:40.880 --> 00:25:43.279
We're going to approve.

s329
00:25:44.480 --> 00:25:48.400
And I'm going to show you that guys later.

s330
00:25:51.200 --> 00:26:01.520
So the idea here um is that the agent will connect we get the identity it uh will have the last email.

s331
00:26:01.520 --> 00:26:03.520
Okay.

s332
00:26:04.480 --> 00:26:05.200
Okay.

s333
00:26:05.200 --> 00:26:06.960
We have a nice email.

s334
00:26:06.960 --> 00:26:09.760
So we know agents can read emails.

s335
00:26:09.760 --> 00:26:11.679
That's not the demo.

s336
00:26:11.679 --> 00:26:13.120
The demo is what what happens.

s337
00:26:13.120 --> 00:26:17.600
So remember we at the beginning we say if we gave identity we can have logs.

s338
00:26:17.600 --> 00:26:19.279
So let's see what the agent did.

s339
00:26:19.279 --> 00:26:22.000
So I know I have an active agent.

s340
00:26:22.000 --> 00:26:24.640
There's an email reader that has this agent ID.

s341
00:26:24.640 --> 00:26:27.039
He's in a local device.

s342
00:26:27.039 --> 00:26:34.480
It has these things and also I can see here this agent with this user ID.

s343
00:26:34.480 --> 00:26:39.679
Okay, I see the agent here just is the email reader and he got these results.

s344
00:26:39.679 --> 00:26:45.760
So I'm actually tracking down what the agent did, right?

s345
00:26:46.080 --> 00:26:58.799
So now let's say I want the agent to I don't know send an email by default what we are proposing is like all the hosts like for example clo

s346
00:26:58.799 --> 00:27:13.679
has reading capabilities by default so then it wouldn't mess up youration with your inbox right so let's see uh let's send an email who has like a really short email that I can put in there

s347
00:27:13.679 --> 00:27:20.793
hello really but no but actual one

s348
00:27:20.793 --> 00:27:22.793
[laughter]

s349
00:27:23.840 --> 00:27:24.880
who has like a good email.

s350
00:27:24.880 --> 00:27:39.360
If not I can put like my own but if you want to show okay so I gonna put mine you see I to myself saying I'm gonna use hello world.

s351
00:27:39.360 --> 00:27:42.409
I thought that your email was hello world was so cool.

s352
00:27:42.409 --> 00:27:44.159
[laughter]

s353
00:27:44.159 --> 00:27:56.240
Okay, so the idea here is if you as you just saw like the agent just have like the reading capabilities.

s354
00:27:56.240 --> 00:28:02.159
Ideally, it will never could send the email without me granting it.

s355
00:28:03.760 --> 00:28:12.240
So for example we can see it here right the only capabilities it has is two of these two.

s356
00:28:12.240 --> 00:28:17.120
So it will try to see it here.

s357
00:28:17.120 --> 00:28:23.919
We can also we also did like this extension for us to actually watch it better what the aation was doing.

s358
00:28:24.080 --> 00:28:25.919
Okay.

s359
00:28:25.919 --> 00:28:26.320
Okay.

s360
00:28:26.320 --> 00:28:29.919
Authorize patch with security verification.

s361
00:28:31.520 --> 00:28:32.399
Okay.

s362
00:28:32.399 --> 00:28:47.440
So you see this um the agent now is using CA like asyn like it's client back channel authorization instead of like just showing me like a redirect and see a device that I approve

s363
00:28:47.440 --> 00:28:49.679
I could approve from here.

s364
00:28:49.679 --> 00:28:56.799
So for the demo I just going to approve and now that the agent has approved.

s365
00:28:56.799 --> 00:28:59.520
I approve it.

s366
00:29:00.720 --> 00:29:04.640
It will be actually sending the email.

s367
00:29:04.640 --> 00:29:20.720
So you will see in the capabilities here that now you can send the capabilities of uh send emails and actually we can see here he just it just send the email right

s368
00:29:20.720 --> 00:29:37.520
so what do we want to try this we're going to see if you see no no okay here is the email okay so what we want to try now let's say this something went wrong with the agent Somebody was trying to access my Gmail trying to propector

s369
00:29:37.520 --> 00:29:38.960
whatever.

s370
00:29:38.960 --> 00:29:49.600
So the idea of this whole thing is to have the trustability we just saw is on the logs right and what if we want to revoke it let's try you let's try to revoke it and try to

s371
00:29:49.600 --> 00:29:51.440
for example read my emails.

s372
00:29:51.440 --> 00:29:57.440
So we're going to revoke it first so it cannot see a thing.

s373
00:30:00.080 --> 00:30:03.235
Oh I lost the page here.

s374
00:30:03.235 --> 00:30:03.440
[snorts]

s375
00:30:03.440 --> 00:30:07.520
So in agents we can revoke the agent.

s376
00:30:07.520 --> 00:30:09.279
So bye-bye.

s377
00:30:09.279 --> 00:30:16.559
And now we can say read that last email you just sent.

s378
00:30:18.559 --> 00:30:20.559
Okay.

s379
00:30:26.640 --> 00:30:30.640
You see the connection got revoked.

s380
00:30:30.880 --> 00:30:33.039
So what happened now?

s381
00:30:33.039 --> 00:30:36.159
Why it can't read it anyway?

s382
00:30:36.320 --> 00:30:51.039
Because what we did is like he created another agent an identity because I revoked the one before but this is just happening because the get the list is a default capability in our host because for us it's safe.

s383
00:30:51.039 --> 00:31:03.200
What if now I wanted to say um send an email saying hello to myself.

s384
00:31:03.200 --> 00:31:04.080
It will do the same.

s385
00:31:04.080 --> 00:31:05.039
It will ask for it.

s386
00:31:05.039 --> 00:31:07.360
So actually it's working right.

s387
00:31:07.360 --> 00:31:08.559
I can actually revoke it.

s388
00:31:08.559 --> 00:31:09.600
I can see the logs.

s389
00:31:09.600 --> 00:31:12.799
I can say what the agent can do or not.

s390
00:31:12.799 --> 00:31:16.000
Don't you think it's a it's kind of nice to have this kind of workflow?

s391
00:31:16.000 --> 00:31:18.480
It's more controlled.

s392
00:31:18.799 --> 00:31:19.279
Yeah.

s393
00:31:19.279 --> 00:31:20.799
You have any questions about this?

s394
00:31:20.799 --> 00:31:22.240
How something that pops in your mind?

s395
00:31:22.240 --> 00:31:24.240
Yeah.

s396
00:31:25.440 --> 00:31:26.159
Yes.

s397
00:31:26.159 --> 00:31:27.279
Yes.

s398
00:31:27.279 --> 00:31:28.960
Yeah.

s399
00:31:28.960 --> 00:31:35.120
Every constraint that you want to be careful about, you can put in the capabilities.

s400
00:31:35.120 --> 00:31:37.600
So, it's good.

s401
00:31:43.120 --> 00:31:45.120
Yeah.

s402
00:31:45.440 --> 00:31:47.440
Yes.

s403
00:31:49.360 --> 00:31:50.159
Yes, exactly.

s404
00:31:50.159 --> 00:31:53.840
You can say maximum maximum time of executing.

s405
00:31:53.840 --> 00:31:55.120
You can say the time.

s406
00:31:55.120 --> 00:31:56.880
You can say everything.

s407
00:31:56.880 --> 00:31:58.320
Yeah, it is.

s408
00:31:58.320 --> 00:32:01.360
Thanks there.

s409
00:32:11.360 --> 00:32:13.360
Mhm.

s410
00:32:19.200 --> 00:32:21.279
Well, you can have both.

s411
00:32:21.279 --> 00:32:24.720
Our idea is like to be safe but not to be annoying.

s412
00:32:24.720 --> 00:32:26.640
Imagine every time you had to read something.

s413
00:32:26.640 --> 00:32:27.840
Oh, I had to approve every time.

s414
00:32:27.840 --> 00:32:29.519
You're going to hate us, you know.

s415
00:32:29.519 --> 00:32:47.039
So the idea is like a host for example or inclus sorry I spoke in Spanish include um or like maybe a host like someone specific you want like for example let's say co can do everything and then like are recently joined just have like this specific access

s416
00:32:47.039 --> 00:32:52.399
so you can do it like by user policies as I was talking about or you can do it like host policies.

s417
00:32:52.399 --> 00:33:00.799
So you have to be like in the middle I think of like good UX uh the good user experience but also secure enough

s418
00:33:00.799 --> 00:33:02.960
but ultimately

s419
00:33:04.799 --> 00:33:23.200
yeah is the ser yeah yeah yeah because uh agent what we're doing like as I said you can try it out uh with the server part is the one going to verify the agent like back with the users going to verify the policies we're going to verify has access or not so yeah all the time verifying so

s420
00:33:24.559 --> 00:33:25.200
Great.

s421
00:33:25.200 --> 00:33:30.080
Um, so the whole idea was to show you this.

s422
00:33:30.080 --> 00:33:33.120
Uh, I was trying to ask the to send.

s423
00:33:33.120 --> 00:33:34.880
Um, I need to confirm.

s424
00:33:34.880 --> 00:33:37.919
So you see, so I here I have the request.

s425
00:33:37.919 --> 00:33:39.200
I didn't accept it.

s426
00:33:39.200 --> 00:33:40.880
So let's say I deny it.

s427
00:33:40.880 --> 00:33:42.640
It will be like the same.

s428
00:33:42.640 --> 00:33:45.279
I just did.

s429
00:33:45.279 --> 00:33:48.399
So ideally he wouldn't.

s430
00:33:50.480 --> 00:33:51.519
You see that's red.

s431
00:33:51.519 --> 00:33:51.840
Okay.

s432
00:33:51.840 --> 00:33:53.440
So it's working good.

s433
00:33:53.440 --> 00:34:00.480
So he wants me to allow it and I'm going to I'm going to So can you tell me agent status?

s434
00:34:00.480 --> 00:34:07.760
So you can have all the time like track down what agent is doing if it's revoked or not.

s435
00:34:07.760 --> 00:34:09.760
Yeah.

s436
00:34:24.879 --> 00:34:31.679
Oh, are you saying if you have for example a skill that is saying to use the MCP server differently

s437
00:34:32.800 --> 00:34:34.399
directly?

s438
00:34:34.399 --> 00:34:34.960
Yeah.

s439
00:34:34.960 --> 00:34:46.240
Well, actually what we are doing is we are infor in this just an example for you to see how the protocol is doing just like a demo but you can enforce for example that the agent the only thing that can use

s440
00:34:46.240 --> 00:34:57.200
um is the MCP tools in this case that's what we did with the plug-in but yeah you have like for our next protocol it's going to be like more

s441
00:34:57.200 --> 00:35:06.240
uh more cap down so the only way the agent can go out and ask for services is through the agent out protocol so it's a good really good question.

s442
00:35:06.240 --> 00:35:08.240
Yeah.

s443
00:35:09.520 --> 00:35:10.079
The what?

s444
00:35:10.079 --> 00:35:12.000
Sorry.

s445
00:35:12.000 --> 00:35:14.240
The proxy

s446
00:35:16.640 --> 00:35:18.640
here.

s447
00:35:24.400 --> 00:35:24.720
Yes.

s448
00:35:24.720 --> 00:35:27.280
Uh you have this in the directory.

s449
00:35:27.280 --> 00:35:32.000
Now you can use it like when you log into for example you are connecting a lot of services in the directory.

s450
00:35:32.000 --> 00:35:36.800
So the agent when it connects to the MCP can know all the capabilities that it can do.

s451
00:35:36.800 --> 00:35:42.880
So inside of the MC the proxy you can see for example the Gmail you can see all the capabilities that agent can do.

s452
00:35:42.880 --> 00:35:46.240
You can see like the agents doing stuff the logs and everything.

s453
00:35:46.240 --> 00:35:50.560
So every log is like cut down by provider.

s454
00:35:50.800 --> 00:35:52.800
Okay.

s455
00:35:53.119 --> 00:35:53.440
Okay.

s456
00:35:53.440 --> 00:35:58.240
Um and about that um our actually proxy is just a directory.

s457
00:35:58.240 --> 00:36:01.520
It's not a real proxy for us like proxy is a really bad idea.

s458
00:36:01.520 --> 00:36:04.240
It's not scalable because proxy uses data.

s459
00:36:04.240 --> 00:36:10.720
So in this case it's just like a directory matching intent with capabilities.

s460
00:36:11.280 --> 00:36:11.839
Okay.

s461
00:36:11.839 --> 00:36:27.200
Um so so back again if you want to try it you can like live you can use like the plugin the SDK.

s462
00:36:27.200 --> 00:36:36.640
It's really nice because we started like from the problems and now actually the solutions right like the discovery authorization and identity.

s463
00:36:36.640 --> 00:36:42.400
Um this is kind of a what I will show you guys like MCP how to connect it.

s464
00:36:42.400 --> 00:36:53.200
Um the SDK side with the MCP is the one that is creating the the the keys and assign it to the to the agents and the server side is like verifying

s465
00:36:53.200 --> 00:37:00.640
authorizing grant um giving the grants that are authorized by the user and and so on.

s466
00:37:00.880 --> 00:37:19.839
So for me the most interesting thing of all is we need to stop giving credentials our credentials to our agents we need to give them authority this should we stop saying like pretend to be me

s467
00:37:19.839 --> 00:37:24.960
instead of saying like act for me within these limits.

s468
00:37:26.160 --> 00:37:29.520
So we are almost in the end.

s469
00:37:29.520 --> 00:37:36.320
If you have any questions, something that pop into your mind or it could be also an addition of what I'm saying.

s470
00:37:36.320 --> 00:37:37.680
I don't know if you ever thought of this.

s471
00:37:37.680 --> 00:37:40.320
Do you think it's a good idea that we implement something like this?

s472
00:37:40.320 --> 00:37:42.720
I'm not saying this one, but maybe.

s473
00:37:42.720 --> 00:37:44.640
Yeah.

s474
00:37:44.640 --> 00:37:45.119
Okay.

s475
00:37:45.119 --> 00:37:47.839
The idea is that this is open for everyone.

s476
00:37:47.839 --> 00:38:00.400
So I would love you guys to join us on Discord or you can send me a message, send me an email, be in the channel like be active because if we improve this for all it's going to be good for all of us.

s477
00:38:00.400 --> 00:38:02.400
Yes.

s478
00:38:06.720 --> 00:38:08.720
Yes.

s479
00:38:12.400 --> 00:38:12.960
Yes.

s480
00:38:12.960 --> 00:38:13.680
Yes, please.

s481
00:38:13.680 --> 00:38:14.960
And please do.

s482
00:38:14.960 --> 00:38:17.119
Yes, please do.

s483
00:38:17.119 --> 00:38:19.119
Sure.

s484
00:38:25.280 --> 00:38:27.760
No, it's totally diagnostic.

s485
00:38:27.760 --> 00:38:29.760
Yes,

s486
00:38:32.000 --> 00:38:32.480
exactly.

s487
00:38:32.480 --> 00:38:34.960
That's the idea.

s488
00:38:42.720 --> 00:38:44.720
Yes.

s489
00:38:47.040 --> 00:38:50.640
Yeah, that's on our B2 and that's our prime focus now.

s490
00:38:50.640 --> 00:38:52.880
So, yeah, that's a great idea.

s491
00:38:52.880 --> 00:38:54.079
Great.

s492
00:38:54.079 --> 00:38:55.119
Any anyone else?

s493
00:38:55.119 --> 00:38:57.119
Yes.

s494
00:39:00.720 --> 00:39:02.640
No, it's different.

s495
00:39:02.640 --> 00:39:03.760
Yeah.

s496
00:39:03.760 --> 00:39:09.359
No, we also I mean we have like as an inspiration like everything that's out there, but it's not the same.

s497
00:39:09.359 --> 00:39:10.320
It's different.

s498
00:39:10.320 --> 00:39:11.040
Yeah.

s499
00:39:11.040 --> 00:39:14.640
Because they are not still treating ancient as a principle.

s500
00:39:14.640 --> 00:39:16.079
We are treating nations as a principle.

s501
00:39:16.079 --> 00:39:17.119
They have their own identity.

s502
00:39:17.119 --> 00:39:21.119
So from that it's different in that way.

s503
00:39:26.320 --> 00:39:26.880
I don't know.

s504
00:39:26.880 --> 00:39:30.000
We don't I don't have that information.

s505
00:39:30.079 --> 00:39:32.079
Yes.

s506
00:39:35.200 --> 00:39:35.599
Sorry.

s507
00:39:35.599 --> 00:39:37.599
What?

s508
00:39:40.160 --> 00:39:42.560
Oh yeah.

s509
00:39:42.560 --> 00:39:55.760
You see I it's connected because of the discovery but it's still the same like for me the most important part is like the Asian B principles have their own identity AI gateway

s510
00:39:55.760 --> 00:40:06.400
doesn't have doesn't do that yet I hope it does but the whole idea is to have like traceability have the whole life cycle and to be able to track down and

s511
00:40:06.400 --> 00:40:12.000
hunt if you want an agent so that you only have if you have identity on on each agent.

s512
00:40:12.000 --> 00:40:15.920
and AI gateway is not providing that.

s513
00:40:16.000 --> 00:40:17.200
Sure.

s514
00:40:17.200 --> 00:40:19.920
Is there any more questions?

s515
00:40:21.440 --> 00:40:22.000
Okay.

s516
00:40:22.000 --> 00:40:29.119
Well, you can reach me in the that's my email if you want to email you want to contribute together would be nice.

s517
00:40:29.119 --> 00:40:34.400
Uh that's my link in and the discord channel from the whole Asian protocol.

s518
00:40:34.400 --> 00:40:34.800
Okay.

s519
00:40:34.800 --> 00:40:35.440
Thank you so much.

s520
00:40:35.440 --> 00:40:37.938
It's been a nice one.

s521
00:40:37.938 --> 00:40:39.938
[applause]

s522
00:40:51.693 --> 00:40:53.693
[music]