Apaleo Agent Hub: Developer Kit

<aside>

</aside>

Welcome to the Agent Hub Ecosystem!

Welcome to the Apaleo Agent Hub! We're excited to have you join our community of developers building cutting-edge AI solutions for the hospitality industry.

The Agent Hub comprises:

Agents that hospitality businesses and developers can search for and connect to their Apaleo accounts; and
a Developer Network, where the developers who built the agents can feature their profile and indicate their openness to be contacted for agent deployment and custom builds.

Expand the points below to get a preview of how these will look! 👇🏽

Sneak Peek: Agents
Sneak Peek: Developer Network

<aside> 🗨️

Ready to build, or already have an agent ready to integrate, but want to talk to us first? Book a call with our Apaleo Founder and CTO Stephan:

</aside>

Agent Development Overview

Agent use cases

In order to be listed on the Agent Hub, agents must cover a hospitality use case, must be connected to Apaleo, and must pass our certification process.

Types of agents: blackbox and whitebox

There are two options for listing your agent:

Blackbox: this is like a mini AI app, where end users will not see the inner workings and decision making processes of your agent. They will simply “click and connect” to your agent via the Agent Hub in order to connect the app to their Apaleo account. In order to publish a blackbox agent on the Agent Hub, you need to build an Authorization Code Flow.
Whitebox: the blueprint and decision making processes of the agent are fully readable and downloadable so that anyone can deploy it and further customize it. In order to publish a whitebox agent on the Agent Hub, you need to make the blueprint/code available as a Github repository.

Permissions and security considerations

Both blackbox and whitebox agents must have defined scopes. For blackbox agents, scopes will be explained to the end user as “What permissions does this agent have in my Apaleo Account?” For whitebox agents, the scopes will be indicated on the agent page in the hub but can of course be changed by the person who deploys the agent.