Developer Platform
Overview
Install
Install AYA in the surface your team actually uses
Install pages explain when AYA should run, how workspace auth works, and what to do if a connector needs to reconnect later.
Install choices
Claude
Public remote MCP install with workspace-scoped OAuth and a deliberately narrow tool surface.
Open guideChatGPT
ChatGPT Apps/MCP setup first, with legacy GPT Actions kept as a secondary path for teams that still need it.
Open guideShared install model
The install experience is shared on purpose. Claude and ChatGPT differ at the connector layer, but both should land in the same workspace-aware auth model so reconnects, revocations, and support paths stay manageable.
AYA ties public installs back to a signed-in user, a selected workspace, and a canonical installation record.
The public tool surface stays intentionally narrow so models have a clearer decision boundary.
Privacy, support, and troubleshooting links live directly on the install pages instead of being buried in reference docs.