The Syntic Console
The Syntic Console is the web app behind your API account. Your code talks to the Syntic API with a key, and everything that key depends on is managed in the Console: the organization it bills, the people who can make more keys, the plan allowance it draws from, the credit wallet that covers overflow, and the record of who changed what.
This section explains each of those areas from a developer’s point of view: what the setting does to your API traffic, who is allowed to change it, and which error your code sees when it gets in the way.
What you manage here, and what you don’t
| You manage in the Console | Your code controls through the API |
|---|---|
| Organizations, members and roles | Which model a request uses |
| Creating, restricting and revoking API keys | Message content, tools and max_tokens |
| Plan, usage credits, spend limits and auto-reload | Whether a response is streamed |
| Audit log review and export | How it retries on 402 and 429 |
There is no separate management API for these settings. Every Console action runs under a signed-in user session, so an API key can call the model but cannot, for example, create another key or raise a spend limit.
Find your way around
Developer settings live under Settings in the Console. The groups you will use most:
| Settings group | Page | What it is for | Docs |
|---|---|---|---|
| Workspace | Members | Invite people, change roles, suspend or remove members | Organizations & roles |
| Workspace | Billing | Plan, usage credits, spend limit, auto-reload, top-ups | Billing & credits |
| Workspace | Usage | Plan windows, credit spend, per-member and per-group spend limits | Usage & cost |
| Workspace | API Keys | Private and public keys, origin restrictions, revocation | Managing API keys |
| Workspace | API Access | This month’s token use, credit balance, signed-in Syntic Code sessions and a ready-to-run test request | Managing API keys |
| Security | Audit Logs | A filterable, exportable record of administrative actions | Audit logs |
Agents, their executions and their tools sit in the Console’s main navigation rather than under Settings. They are covered in Agents.
Some pages only appear for certain roles. For example, Audit Logs is shown to members whose role lets them read it. If a page described here is missing for you, ask an owner or administrator of your organization; see Organizations & roles.
Set up an organization for API use
If you are starting from scratch, this is the order that avoids surprises later.
Sign in and pick the organization
Sign in at platform.syntic.ai/login, or with Sign in at the top of this site. If you belong to more than one organization, switch to the one that should pay for the traffic. Keys, usage and billing all belong to a single organization.
Invite the people who will build with the API
Under Settings → Members, invite teammates as Developer if they only need their own keys, or Administrator if they should manage keys, billing and members for everyone. See Organizations & roles.
Decide what happens when the plan runs out
Under Settings → Billing, choose whether usage credits should take over once the plan allowance is used, and set a monthly spend limit you are comfortable with. Without credits, requests stop with 402 quota_exhausted until the plan window resets. See Billing & credits.
Create a private key per service
Under Settings → API Keys, create one private key for each service or environment. Store each in that service’s secret store. See Managing API keys.
Send a test request
Confirm the key works and see which wallet paid for the call:
curl -sS -D - https://app.syntic.ai/v1/chat/completions \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "Amara Quick", "stream": false,
"messages": [{"role": "user", "content": "Reply with the word ready."}]}' \
| grep -i -E '^x-syntic-|"content"'The x-syntic-billing-source header reads subscription while the plan covers you, and api_credit once usage credits are paying.
Signing in and multi-factor authentication
Your organization may require multi-factor authentication for every member. Even where it is optional, the Console asks you to confirm your second factor again before sensitive actions such as creating an API key, so expect a prompt part-way through that flow if you have a factor enrolled.
Console sessions and API keys are separate credentials. Signing out of the Console does not revoke any key, and revoking a key does not sign anyone out.
In this section
- Managing API keys: create, restrict, rotate and revoke the keys your code uses.
- Organizations & roles: members, roles and how membership changes affect keys.
- Usage & cost: the three plan windows, how a request’s cost is worked out, and per-member limits.
- Billing & credits: plans, usage credits, top-ups, auto-reload and spend limits.
- Audit logs: who did what, when, and how to export it.