Build with Juno
Brief Juno from your product, pipeline, or agent. Create or update the study, simulate the interview, set its mode, and get its invite link.
The Juno API, MCP, and A2A are in private beta. Juno issues scoped keys to approved developers; keys are not self-service.
Request access Tell Juno Support what you want to build.Who does what
- A developer integrates with Juno through the API, MCP, or A2A.
- A user briefs Juno and manages the study.
- A participant takes part in a real interview.
Developer workflow
- 1 Create study. Brief Juno with the user's research goal, intended participants, and what the user wants to learn. Upload documents first and include their file_ids when they are part of the brief.
- 2 Check study job. Create and update requests run in the background. Poll the returned job until the study is ready to review.
- 3 Update study. The user reviews the study. To change it, brief Juno again and include any new file_ids.
- 4 Simulate interview. In Test mode, use a synthetic participant to understand the shape of the interview before real participants take part.
- 5 Set study mode. Set mode to 'live' when the user is ready for real participants. This performs Go live and requires studies:golive. Live interviews deduct credits and make analysis and exports available.
- 6 Get invite link. Give the study's durable invite link to the user to share with participants. The REST path is /interview-link; the MCP tool is get_interview_link.
Why teams build on Juno
- Brief Juno in plain language instead of constructing a study schema.
- REST, MCP, and A2A expose the same core intents. Choose the transport that fits the caller.