#2. Platform
The original goal for concierge was to build an agent for myself. But I think it’s more rewarding to have public utility.
I now think of concierge as an agent platform. A fleet of specialised AI agents that live on websites to help people do stuff.
Profiles
An agent’s profile is its identity. It determines what the agent knows and what it can do. Here’s an example:
{
"host": "concierge.opemipo.com",
"name": "concierge",
"description": "You are concierge, a chatbot designed to answer questions...",
"brand": {
"background": "#011b33",
"highlight": "D9FFD9",
"typeface": "Inter",
"avatar": "image.png",
"tone": "Keep all responses simple, concise and to the point"
},
"sources": [{
"source_type": "json",
"source_url": "bio.json",
"source_description": "Use this information to answer questions about the person...",
"authentication": null
}, {
"source_type": "json",
"source_url": "bookmarks.json",
"source_description": "Use this information to answer questions about links...",
"authentication": "user"
}],
"interfaces": [],
"tools": [{
"tool_id": "uuid",
"tool_name": "searchBookmarks",
"tool_description": "Return a list of bookmarks based on the query",
...
}]
}
With profiles, we can configure new agents as needed.
Interfaces
Interfaces are input-output systems optimised for a specific goal.
concierge will start with three:
- chat: for conversations
- form: for written queries
- voice: translates audio to text
Next
We need to refactor the codebase to support this platform vision. After this, we can start building our next agent.
