Skip to main content

Control customer agent and flow availability

Platform defaults give every stamped agent and flow a fleet-wide baseline. A customer override can narrow or widen one customer's setting without changing the release or any other customer.

Read resolved standing​

GET /api/partner/v1/organizations/{orgId}/entitlements
Authorization: Bearer ykp_00000000-0000-4000-8000-000000000001.AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

The credential is an obviously fake, structurally valid example.

Each agent or flow reports defaultEnabled, nullable overrideEnabled, resolvedEnabled, and provenance (default or override). Use resolvedEnabled as the effective answer.

Set or clear an override​

PATCH /api/partner/v1/organizations/{orgId}/automations/{automationId}/entitlement
Content-Type: application/json

{ "enabled": false }

Clearing is a separate operation:

DELETE /api/partner/v1/organizations/{orgId}/automations/{automationId}/entitlement

Delete means “inherit the platform default,” not “enable.” Writes are race-safe and customer-scoped.

Disable semantics​

Disabled means inert across manual, API, trigger, draft, and test entry paths. Disabling also cancels queued executions and requests cooperative cancellation for already-running work. A side effect already executing in a remote system cannot be recalled, so use ordinary reconciliation for ambiguous external outcomes.