Juno

Build with Juno

Brief Juno from your product, pipeline, or agent. Create or update the study, simulate the interview, set its mode, hand out its invite link, and read the interviews back.

You can start building today. Create an API key yourself in the Juno app, or connect your app with OAuth and let the person who owns the workspace approve it. REST and MCP accept either credential. A2A accepts an API key.

An API key belongs to an organisation and carries a fixed set of permissions. An OAuth connection belongs to one person in one workspace and carries only the permissions they approved. Use a key for your own backend. Use OAuth when other people connect your app to their own Juno workspace.

Get a credential

Every request carries a bearer token. That is either an API key, which belongs to an organisation, or an OAuth access token, which belongs to one person in one workspace. A key's data environment is separate from a study's Test mode or Live mode.

API key For your own backend. Create one in the Juno app and store the secret. OAuth For apps other people connect to their own workspace. They approve it; you never hold their key.

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. 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. 2 Check study job. Create and update requests run in the background. Poll the returned job until the study is ready to review.
  3. 3 Update study. The user reviews the study. To change it, brief Juno again and include any new file_ids.
  4. 4 Simulate interview. In Test mode, use a synthetic participant to understand the shape of the interview before real participants take part.
  5. 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. 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.
  7. 7 See the interviews. Read the interviews back as they finish. Filter by study and by status, and use the context you attached to the invite link to match each one to your own record.
  8. 8 Export interviews. Export the Live-mode interviews as CSV when you want the transcripts and answers themselves, which the interview list does not carry.
Everything slow is a job Authoring, simulations, and exports never block the request. They return a job you poll. Treat the job handle as the source of truth for progress, not a fixed wait.

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.

Choose a transport

REST Use REST when backend code, an internal tool, or a pipeline should call Juno directly. MCP Use MCP when an AI assistant should call Juno through tools. A2A Use A2A when your own agent should give Juno plain-language instructions over JSON-RPC.
Next API keys