aevatar-schedulerlisted

# Schedule an Aevatar service on a cron ## Route to the right resource FIRST — three paths, not one "Run it on a schedule" is three different resources with three different owners, credentials, and APIs. Pick before you call anything; using the wrong one is not a shortcut, it is the wrong resource. | The user wants to schedule… | Resource owner | Canonical entry | Credential | |---|---|---|---| | An already-bound **Studio Team member** workflow | `scope → team → member` | `aevatar_schedule_member_workflow`, or REST `/api/scopes/{scopeId}/teams/{teamId}/members/{memberId}/automations` | **Dedicated Agent Key** | | An independent **scheduled Ornn skill agent** or a **one-shot reminder** | Scheduled agent / catalog actors | `scheduled_agent_creator`, then `agent_builder` — see `aevatar-automation` | **Dedicated Agent Key** | | A typed **service invocation** | Generic platform schedule actor | Generic `/api/schedules` — the rest of this skill | Typed source; may be a NyxID binding exchange | **If the owner is a Team member, the canonical path is the member automation route — not generic `/api/schedules`.** Generic `/api/schedules` is a platform-level resource for typed service invocations. It is supported, but it is *not* a fallback for Team member automation, and reaching for it because you already know its shape is the most common mistake here. Never convert between identities by route position, prefix, equality, or a familiar-looking string: `memberId`, draft `workflowId`