AYA Developers

Calm API, MCP, install, and console surfaces for working with AYA’s digital twin system.

Home Docs Guides Install Console

Developer Platform

Guides

Public view

Guides

Guides for the real integration work

Use guides when you want a clearer path through setup decisions, operator behavior, and the practical edges around API, MCP, ChatGPT Apps, and legacy Actions installs.

See install options Go to docs

Guide index

Quickstart Guide

Go from zero to a real concept-test request, async polling, and completion handling.

Open guide

Claude MCP Guide

Understand the narrow public tool surface, connector behavior, and install flow.

Open guide

ChatGPT Apps Guide

Set up ChatGPT Apps/MCP and teach the model when AYA should run.

Open guide

OAuth and Workspace Setup

Map users, workspaces, and installations without exposing raw API keys.

Open guide

Webhook Setup

Configure, verify, and test signed delivery endpoints from the console.

Open guide

Examples and Prompting

Use prompt and integration patterns that give models a clean decision boundary.

Open guide

For API teams

Create a workspace-scoped client and issue an API key.

Submit a concept test or quick pulse and wire up job polling.

Add a signed webhook once you need automated completion handling.

For Claude installs

Confirm the workspace that should own the install before approval.

Keep prompts specific about audience, concept, and decision context.

Use the public MCP toolset only when audience evidence could change the answer.

For ChatGPT Apps

Use the Apps/MCP path first so setup follows the current ChatGPT integration model.

Keep the legacy Actions schema as a fallback only when that is the surface your team is shipping.

Treat AYA as a narrow evidence layer, not a generic action for every prompt.