14 March 2025

· Identity
· Protocol
Let us do a deeper dive on each of these aspects.
Today AI Agents are being built for use within enterprises and being built in such a manner that they are simply extensions of robotic process automation scripts. This is a major flaw. AI Agents have to have Permanent IDs because without identity there is no traceability or accountability as to who or what performed a particular task. This accountability and traceability is there with Human operators because everyone has an Employee ID within an organization. AI Agents have to accounted for from a security standpoint at the same level as humans and not as RPA scripts.
The identity of an AI Agent within an organization can be tied to the Identity and Access Management system (IAM) of that enterprise which may Okta or Microsoft Active Directory etc. In the real world this is tantamount to a Driver’s License for movement throughout America even for Domestic Air travel.
Now, if we extend the AI Agent’s reach outside of an Enterprise and need it to communicate with other AI Agents outside of the Enterprise, this crosses the Trust Boundaries governed by the IAM. So, how can trust be established between two AI Agents across Enterprise or trust boundaries?
A complex and unscalable approach would be the federation of IAMs between any two peering enterprises. This is cumbersome and not scalable because it becomes a N(N-1)/2 problem.
Now, if we use a Decentralized Identity Access Management system (Registry) and a Decentralized ID then any Agent can discover, and authenticate any other Agent. This is a scalable and inexpensive solution to a complex problem. In the real world, this is tantamount to having to carry a Passport for International air travel. This approach can also be used within an organization if an enterprise chooses to do so.
Each AI Agent whether operating internally within a trust boundary or between trust boundaries needs a receptacle to carry its identity. In the real world, this is similar to how human’s carry a wallet with their Driver’s License, cash, credit cards, medical cards and more. So a Wallet is needed to hold the identity of an Agent.
Once an AI Agent is equipped with a Decentralized ID, Wallet and is registered in a Registry, it is ready to communicate with other AI Agents. But in order to do that, one needs a protocol – i.e. a way of communicating.
This protocol needs two aspects –
· To authenticate the other agent(s)
· A vocabulary for communicating.
The authentication is common to any interaction as this is not context specific.
The communication vocabulary is however context specific.
For instance,
· if two agents are trading with one another in the stock exchange, they are communicating about buying and selling equities at a given price.
Whereas,
· if two agents are communicating on the topic of health insurance, they may be discussing ICD-10 and CPT codes appropriate for Medical billing.
Identity Management and Authentication are key building blocks in establishing trust between AI Agents. As described earlier, one needs to have a decentralized ID, a Registry and a Protocol for communication to occur between any two AI Agents.
Now, the first half of that communication is to authenticate the other agent. Say Agent A wishes to authenticate Agent B. A number of trust factors would have to be established when each of these agents are initially registered on the Registry.
a. Provenance:
Which entity created this agent ? Are they legitimate? An example of this is during App registration on the Apple App store, where Apple administers a rigorous background check on the entities attempting to submit a mobile application for listing. Similar checks need to be done as part of the submission to the Registry.
b. KYA:
To prove the legitimacy of an Agent, there needs to be a Know-Your-Agent (KYA) process established. There will be background checks (police, Interpol, FBI and several other checks) similar to KYC/AML.
c. Secure Execution Environment:
To avoid a legitimate agent being infected by malicious code that makes it behave in an improper manner, it is paramount that agents operate within a secure execution environment.
There are many use cases for Agent to Agent communication that would improve efficiency and cost. Let us describe a common one in Healthcare.
In a typical scenario when a patient arrives at a clinic for a health checkup, the patient presents their Health Insurance ID to the admin person. The admin person then calls the Health Insurance company to verify the legitimacy of the Health Insurance ID. This process is still done manually in most cases. Upon completion of this check, the patient is admitted for consultation. Upon completion, the notes are summarized, the Medical billing codes are then negotiated with the Health Insurance company.
If we decompose this example into a workflow, we can identity very easily the steps that can be solved by agents.
In Healthcare and Finance there are compliance measures such as HIPAA and SOC2. AI Agent communications are in fact safer than Human in the loop in many cases because AI Agents do not do the following:
Further measures include:
Ethical considerations are an important consideration when agents are used in workflows. The state of the art AI Agents are still not at the maturity level industry wide to make ethical or moral decisions in our opinion.
To resolve this, when there are moral and ethical dilemmas, it is best to include Humans in the Loop as part of the decision making process. If there are decisions that can be automated without such considerations, is when Agents can autonomously make decisions.
In Autonomous agents, examples of such junction points where are ethical considerations can happen:
Businesses can ensure AI Agents and Humans align on decision making by designing workflows with Human in the Loop. This will ensure that there is oversight, traceability, accountability, observability and governance in all workflows.
As mentioned on the section on Identity and Access Management, Decentralized Architectures are key for establishing communication between Agents.
Over time, we foresee all humans having their own Digital Twins. These Digital Twins will operate on behalf of humans and carry out tasks such as shopping, searching, booking reservations, and more.
For this reason, unlike all other AI Agents, AI Agents made by Synergetics are NFTs from the ground up with Wallets and Identity- ready to navigate the vast resources of the world wide web.
In many enterprises, knowledge on work processes is buried with the staff working at these organizations. We call this “Tribal Knowledge”.
In order for enterprises to transition from AI Agent assisted human workflows to AI Agents operating workflows autonomously, it is necessary for enterprises to bring this tribal knowledge to the surface.
Once these workflows are are clearly understood, one can identify workflows that can be automated and run autonomously by AI Agents and those requiring human intervention.
In this early stage, we are seeing a lot of companies claiming to have AI Agents but most are simply thin veneers on top of an LLM.
To have true AI Agents, one needs to consider:
These early AI Agents are simple Prototypes with very little thought given to long term considerations. Hence, enterprises can learn from these experiences and evolve to more industrial-strength AI Agents which are more capable with sound engineering principles behind them.
Several common misconceptions are: