Building a survey and reading what people answered are different sensitivities — the second is respondent data. Having them as separate scopes means an agent that drafts questionnaires need never see a response. Add resource indicators on top, and this is one of the more carefully specified authorisation setups in the directory. The AI-draft mode is convenient; the working-draft model is what keeps it from publishing something half-written.
Empirio's endpoint for their survey platform. Sixteen tools covering the lifecycle: list what exists, read the full design, create a draft manually or with AI, and edit it before it goes out.
- survey_list — surveys you own or that are shared with you
- survey_get — the full design: questions, settings and layout
- survey_create — a new draft, manual or AI-generated
- survey_edit — change the working draft
- And the remaining tools, covering responses and the rest of the lifecycle
OAuth 2.1 with PKCE, dynamic client registration and resource indicators, with scopes split into surveys and responses. Bearer keys beginning sk_live_ are also accepted for REST use.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen