01 / The setup
You’ve already done the work.
You’ve given your agent instructions, connected tools and refined how it works. Perhaps it prepares your morning briefing or helps you research a subject. Someone else wants an agent that can do the same.
An Agent Passport brings the setup into one readable file: what the agent is for, what it needs and examples of how it should work.
02 / The passport
A clear account of what you’re sharing.
- Instructions and purpose
- The job the agent does, the information it needs and the way it should respond.
- Tools and access
- The capabilities it needs, so the recipient knows which tools and accounts to connect.
- Examples and limits
- Examples of useful output, and an account of what cannot be recreated.
Passwords, API keys and login sessions do not belong in a passport. Review the file before sharing it, including any examples or information you want to keep private.
03 / On the other side
Their own agent, with their own accounts.
The recipient opens the passport and follows the setup instructions with their assistant. They connect their own tools and accounts, and decide which access to allow.
Their setup may differ from yours. A tool might be missing, a source might need a subscription, or their assistant might work differently. The installation records those differences in a losses table, including when there is nothing to report.
The current version supports reading information and delivering results in chat. Actions such as sending email or changing records can be described, but are not installed.
Try it
Start with an agent you know.
Create a passport for an agent you’ve built and share its setup with someone else.