Users and developers setting up AYA inside assistant environments.
Provide a crawlable install hub for AYA connectors.
Supported assistants
AYA works in ChatGPT as a custom app, in Claude on the web, desktop and mobile as a custom connector, and in Claude Code as a plugin from github.com/Ask-Your-Audience/askyouraudience. Each install signs in with your existing AYA account.
Trust and control
Connecting and preparing studies are free. Every study shows its brief, participants and token cost and runs only after you approve it.
Developer evaluation path
Technical buyers should use the developer pages to understand the public integration surface, authentication model, connector routes, API concepts, and documentation map before building against AYA. Private consoles and account-specific tools remain outside the crawlable marketing surface.
AI agent context
These pages are written so coding assistants and retrieval agents can distinguish AYA APIs, MCP connectors, ChatGPT Actions, install guides, and reference material from the general product marketing pages.
Implementation boundary
A useful developer journey starts with the public docs, then moves into authenticated workspace setup only when the buyer is ready. Public documentation should explain what an integration can do, which workflows are available, how authentication is approached, how job status is handled, and where examples or reference material sit. It should not expose private customer data, secret tokens, or account-specific console routes to search engines.