{
  "summary": "CiteLoop's API reflects the same workflow model as Engage: stories and POVs, participants, invitations, replies, assets, and render jobs.",
  "domains": [
    {
      "name": "Stories and POVs",
      "description": "Create stories, attach POVs, update angle definitions, and work with story-level context.",
      "paths": [
        "/stories",
        "/povs",
        "/stories/{id}/povs"
      ]
    },
    {
      "name": "Participants and contributor operations",
      "description": "Manage participant records, settings, consent, groups, and POV linkages.",
      "paths": [
        "/participants",
        "/participants/groups",
        "/povs/{id}/participants"
      ]
    },
    {
      "name": "Invitations and outreach",
      "description": "Issue participant invitations, manage open invitation flows, and preview or send messaging workflows.",
      "paths": [
        "/participants/{participant_id}/invitations",
        "/open-invitations",
        "/messages/preview",
        "/messages/send"
      ]
    },
    {
      "name": "Replies, assets, and rendering",
      "description": "Handle collected responses, process assets, and create asynchronous render jobs.",
      "paths": [
        "/jobs/render",
        "/assets",
        "/objects"
      ]
    }
  ],
  "integration_notes": [
    "API access is arranged through onboarding, not open self-serve signup.",
    "Your deployment may include a subset of the domains and paths above, depending on contract and use case.",
    "Path examples reflect the Engage workflow model. Scopes, credentials, and allowed endpoints are agreed during onboarding."
  ]
}
