Developer Platform
Home
Developer Platform
Add audience intelligence to anything you build.
Test concepts, interview digital twins, and analyze creative — from your own apps, AI agents, and automation workflows. AYA works best when audience evidence could change the decision, especially across configured markets like the UK, Europe, and North America.
Why build with AYA
Audience research that fits how you already work
Whether you're shipping a product, building an AI agent, or embedding research into a platform — AYA gives you structured audience intelligence through digital twins matched to a defined audience context.
Twin coverage
Multi-market
Built for UK, European, North American, and other configured audience contexts without pretending to be a live census feed.
Audience types
B2B + consumer
Marketers, founders, buyers, parents, operators, and category-specific decision makers can all be framed as target audiences.
Delivery surfaces
API, MCP, jobs, webhooks
REST, remote MCP, async job handling, and signed completion callbacks all sit on the same execution path.
Public phase-1 scope
6 narrow capabilities
panel_resolve, quick_pulse, concept_test, interview, focus_group, and job_status keep the external surface focused and model-friendly.
Validate ideas before you build
Run a concept test from your CI pipeline, Slack bot, or product dashboard. Get structured feedback from digital twins matched to your target audience and market context — in minutes, not weeks.
Give your AI agent audience awareness
Connect AYA as a tool via MCP or REST. Your agent can decide when audience validation is needed, run a focused check, and factor in those signals before making recommendations.
Embed research in your product
Add audience testing as a feature inside your SaaS. Let users validate messaging, creative, or positioning for buyer groups, parent segments, operators, or market-specific audiences.
Coverage examples
AYA is strongest for directional validation and prioritization. It should not be treated as a substitute for live research when the stakes or uncertainty demand direct market evidence.
Get started in minutes
Four steps to your first API call
No SDK required. Pick your language, authenticate with your workspace API key, and start running research tied to the same workspace you already use in AYA.
01
1
Create API client
Open the developer console and create a client for your workspace.
02
2
Issue a key
Generate an API key. Copy it immediately — it’s only shown once.
03
3
Make your first call
Send a concept test request and get a job ID back in seconds.
04
4
Get results
Poll the job endpoint or set up a webhook to receive results automatically.
Platform architecture
One engine powers every integration
Whether you call AYA through the REST API, an MCP tool, or a future ChatGPT action — your request hits the same research engine. Same quality, same data, same workspace.
AYA App
Live
REST API
Live
MCP Server
Beta
ChatGPT
Planned
Canva
Planned
Enterprise
Planned
Execution Engine
Twin Engine Backend
One workspace · One billing spine · One identity
Auth & Sessions
Async Jobs
Webhooks
Usage Metering
Platform capabilities
Everything you need to integrate audience research
A complete platform for embedding concept testing, audience resolution, async execution, and install-safe operational tooling into your products and workflows.
Live
REST API
Clean /v1/* endpoints with idempotent requests, structured errors, and async job tracking. The public phase-1 surface stays intentionally narrow and centered on real research runs.
Beta
Remote MCP Server
Connect Claude or another MCP-compatible agent directly to AYA. The tool metadata stays narrow so models use AYA for audience validation instead of general-purpose work.
Live
Async Job Engine
Submit research runs and get results via polling or webhooks. Concept tests, interviews, and asset analysis all follow the same pattern.
Live
Signed Webhooks
Receive HMAC-signed events when jobs complete or fail. Create, test, and monitor webhook endpoints from the developer console without building a second delivery layer.
Live
Workspace-Scoped Access
No separate developer account. Your existing AYA workspace supports API keys, webhooks, MCP connections, and usage tracking.
Live
One Account, One Bill
API usage and browser research stay under the same billing record. Everything resolves back to the same workspace, installs, and operational context.
Quickstart
Test a concept in a few lines of code
Pick your language. You'll get back a job ID within seconds — then poll or set up a webhook to receive the results.
bash
curl https://api.askyouraudience.ai/v1/concept-tests \ -H "X-Api-Key: <YOUR_AYA_API_KEY>" \ -H "Idempotency-Key: concept-demo-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" }'
You get back a job ID
Every research run is async. Poll the job endpoint or configure a webhook — AYA notifies you when results are ready.
json
{ "job_id": "2d6c...", "status": "accepted", "linked_resource": { "type": "concept_test_job", "id": "b473..." }}
MCP Beta — Live Now
Connect your AI agents to AYA
AYA exposes a remote MCP endpoint backed by the same execution engine as the REST API. Add it to Claude, Cursor, or any MCP-compatible client with a workspace API key.
json
{ "mcpServers": { "aya": { "transport": "http", "url": "https://mcp.askyouraudience.ai", "headers": { "Authorization": "Bearer <workspace-api-key>" } } }}
These tools are available today. OAuth install and registry listing are coming next.
What is MCP?
Model Context Protocol lets AI agents discover and call external tools natively. Instead of writing API wrappers, your agent just asks AYA to test a concept — and it does.
What can I do with it today?
Resolve audience panels, run quick pulses, launch concept tests, start automated interviews, run focus groups, and poll job status. The MCP server supports workspace API keys for manual clients and OAuth tokens for managed installs.
What’s coming next?
Provider submission, official registry listing, stronger smoke-test evidence, and selective coverage for additional workflows such as asset analysis.
No extra accounts
Your workspace is already set up.
If you have an AYA account, you already have everything you need. Create API keys, connect MCP clients, and manage usage right from your existing workspace. No new signups, no separate billing.
Your research
Your API keys
Your MCP connections
One invoice
Roadmap
What's live and what's next
The API and MCP beta are available now. ChatGPT, Canva, and enterprise integrations follow — each built on the same foundation.
Phase 1
API Foundation
- Gateway & control plane
- Versioned REST contract
- Developer console & key management
Phase 2
Portal, Webhooks & MCP
- Public docs & quickstarts
- Webhook management & delivery logs
- Remote MCP server beta
Phase 3
Dogfood & Partner Beta
- Canary workspaces on staging
- Authenticated MCP testing
- Partner API access
Phase 4
Distribution
- ChatGPT connector
- Canva app
- MCP OAuth & registry listing
Phase 5
Enterprise
- Managed ingestion
- Private twin overlays
- Custom refresh cadences
Ready to integrate?
Create your first API key and start testing concepts from your own code in minutes.