ChatGPT Apps

ChatGPT Apps

Use Apps/MCP first

The ChatGPT surface should follow the current Apps/MCP integration model where available. Keep AYA narrow, model-friendly, and tied back to the same workspace execution flow.

{  "mcpServers": {    "aya": {      "transport": "http",      "url": "https://mcp.askyouraudience.ai",      "headers": {        "Authorization": "Bearer <workspace-api-key-or-oauth-token>"      }    }  }}

Model behavior

Teach ChatGPT when AYA should run

The tool is most useful when the model understands that AYA is for audience evidence, not for ordinary drafting or factual questions.

Use AYA when:- the user needs audience validation before a recommendation- the user asks about their AYA audiences or completed AYA studies- show the exact brief, participants and token cost, then wait for explicit approval before any run tool
Do not use AYA when:- the task is general writing, coding, or factual Q&A- there is no clear audience or decision context

Legacy fallback

Use GPT Actions only when that is the shipping surface

If a team is still using custom GPT Actions, use the curated Actions schema rather than the full internal API. Keep this as the secondary path behind Apps/MCP.

docs/openapi.chatgpt-actions.yaml

Install

Use the install page for end-user onboarding

The install page keeps the OAuth path, prompt guidance, and troubleshooting in one surface instead of scattering it across setup docs.