Settings
Settings is where you look after your own account: who you are, how you sign in, how the hub looks to you, what you are told about, what you have used and what you pay for.
You open it at /settings, or under your own workspace at /<workspace>/settings.
Topics
- The topics: each section of Settings, and what it holds.
- Usage: what you have done this period, and what it cost.
- Assistants: the personas that may act as you, and the approvals waiting for you.
Everything a Settings section shows, a program can read and change over the API. Each section draws on one family of routes.
Account and Profile read and write who you are under the auth tag. Tokens are the token routes under the same tag.
Security is the multi-factor routes, and Contacts the contact routes, both under account.
Addresses and Social are the address and social-link routes under content.
Appearance and Preferences are your settings rows, kept as appearance and workspace settings.
Notifications is the notification preferences routes under notifications.
Assistants reads the personas that may act for you from the access routes, and the approval queue from the persona approval routes.
Archived is the archived workspaces route under workspaces.
Usage is one summary call under usage. Subscription is the billing context call under billing.
The full list of routes, with each one's parameters, body and responses, is the REST reference on the help site. The tools an agent gets are listed in the MCP reference.
One settings page, two addresses. The page at /settings and the one under your workspace are the same sections, so a deep link works from either side and nothing is written twice.
Approvals live with the person, not the persona. The queue is answered where the person is, because the person is the one whose authority the persona is spending.
Cost is in money. Tokens measure work. Only money measures cost, and work whose price is unknown is charged at the ceiling.