Calm API, MCP, install, and console surfaces for working with AYA’s digital twin system.
Developer Platform
Getting Started
Docs
Getting Started
Quickstart, first request, environments, and model-facing usage guidance.
Getting Started
Start with one concept-test request
The cleanest path into AYA is still the same: create a workspace client, issue a key, submit a concept test, and then either poll or subscribe for completion.
bash
curl https://api.askyouraudience.ai/v1/concept-tests \ -H "X-Api-Key: aya_test_..." \ -H "Idempotency-Key: ct-001" \ -H "Content-Type: application/json" \ -d '{ "brief": "UK fintech app for first-time investors", "concept": "An investing app that explains every decision in plain English" }'
Setup
How the developer platform is organized
Docs are public, install guides are public, and the console is authenticated. That separation keeps browsing and account management from bleeding into each other.
Docs explain the public API, MCP, Actions, auth, webhooks, and examples.
Install pages are the trust-building surfaces for Claude and ChatGPT users.
The console is where workspace owners manage keys, usage, connectors, logs, and settings.
Environments
Use clean domains in production and staging
The production mental model is developers.askyouraudience.ai for docs and console, api.askyouraudience.ai for REST, and mcp.askyouraudience.ai for MCP. In staging, developers-staging, api-staging, and mcp-staging mirror that split.
http
POST https://api-staging.askyouraudience.ai/v1/concept-testsX-Api-Key: aya_test_...Content-Type: application/json
On this page