Organizations & roles

On the Syntic platform, the organization is the unit that owns things. API keys, plan allowance, usage-credit wallet, spend limits, agents and the audit log all belong to one organization, and every API request is billed to the organization that issued its key.

People join an organization as members, and each member holds a role that decides what they may change. This page covers how that works and how membership changes reach your API traffic.

Organizations

• A person can belong to several organizations and switches between them in the Console. Whatever page you are on acts on the organization currently selected.
• A key always bills its home organization, whichever organization its creator has selected at the time a request is made.
• Usage, credits and limits are never pooled across paid organizations. Each one has its own plan allowance and wallet.

Want separate budgets for, say, production and experiments? Use separate organizations, or set spend limits per member or group inside one organization.

Roles

What each role can do in the Console

Custom roles

A member with the custom role gets permissions from the groups they belong to. Each group can carry a grid of administrative areas, each set to none, view or manage. The areas that matter for API work are:

Billing changes and organization-wide key management are reserved for owners and administrators. A custom-role member creates and revokes keys like a developer: only their own.

Members

Invite someone

Change a role

Administrators can move a member between administrator and developer. Changing the role of another administrator or of an owner requires an owner. The owner role itself cannot be granted through a role change.

Role changes are recorded in the audit log as member.change_role.

Suspend, restore or remove

“Stop working” means requests with those keys fail with 403 org_membership_required. The keys are not revoked, so restoring the member brings them back. Owners cannot be suspended or removed this way.

Handle membership errors in code

When a membership or organization problem blocks a key, the API answers with a 403 and a code your code can branch on. None of these will succeed on retry until someone changes the organization in the Console.

import os
import requests
 
ORG_PROBLEMS = {"org_membership_required", "account_disabled", "org_unavailable"}
 
resp = requests.post(
    "https://app.syntic.ai/v1/chat/completions",
    headers={"Authorization": f"Bearer {os.environ['SYNTIC_API_KEY']}"},
    json={
        "model": "Amara Quick",
        "stream": False,
        "messages": [{"role": "user", "content": "Summarise yesterday's deploy log."}],
    },
    timeout=60,
)
 
if resp.status_code == 403 and resp.json()["error"]["code"] in ORG_PROBLEMS:
    # Not transient: page a human instead of retrying.
    raise RuntimeError(f"Syntic key blocked: {resp.json()}")
resp.raise_for_status()
print(resp.json()["choices"][0]["message"]["content"])

const ORG_PROBLEMS = new Set(['org_membership_required', 'account_disabled', 'org_unavailable'])
 
const resp = await fetch('https://app.syntic.ai/v1/chat/completions', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.SYNTIC_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    model: 'Amara Quick',
    stream: false,
    messages: [{ role: 'user', content: "Summarise yesterday's deploy log." }],
  }),
})
 
const body = await resp.json()
if (resp.status === 403 && ORG_PROBLEMS.has(body.error?.code)) {
  // Not transient: alert someone who can fix the organization.
  throw new Error(`Syntic key blocked: ${JSON.stringify(body)}`)
}
if (!resp.ok) throw new Error(JSON.stringify(body))
console.log(body.choices[0].message.content)

A related 503 authorization_unavailable means the API could not check the credential at that moment. That one is transient; retry after a short wait.

Related

• Managing API keys
• Usage & cost
• Audit logs
• Errors