Setup Guide

Overview

SDCStudio is a cloud-based SaaS platform: there is nothing to install. This guide walks you through creating your account and configuring your settings.

Creating Your Account

  1. Visit SDCStudio: Navigate to https://sdcstudio.axius-sdc.com
  2. Sign Up: Click "Sign Up" and fill in the form: email, password, and password confirmation (at least 8 characters), with optional full name, first and last name, organization, and expected usage. Tick the Terms of Service checkbox and click Create Account. To use a Google account instead, click Continue with Google on the sign-in page
  3. Verify Email: You are returned to the sign-in page with a message to check your email; click the verification link in that message
  4. Sign In: Log in to access the dashboard
  5. Fund Your Wallet: A new account is taken to /app/welcome and must fund its wallet before anything else in the app opens: click Fund $10 & Start and pay $10 (10,000 credits) through Stripe; larger packs are sold afterwards in Settings > Wallet. The credits are yours and are spent per operation; nothing is charged by time. The gate applies to accounts created on or after 1 August 2026 and releases for good the first time the wallet holds a positive balance. Until then the rest of the app is not reachable; the public catalog API and the practitioner directory need no account.

Settings Overview

All account configuration is in the Settings page. Open the user menu (your name, top right), click Settings, or go directly to /app/settings.

Settings is organized into six tabs:

  • Profile: your identity and password
  • Preferences: display, language, modeler defaults, and ontology configuration
  • Teams Management: team membership and collaboration
  • Wallet: billing, credits, and transaction history
  • Practitioner: your practitioner credential and exam status
  • API Keys: programmatic access tokens

Ontologies are not a Settings tab. They are uploaded and managed on their own page, /app/ontologies, reached from Preferences > Modeler Information > Manage Ontologies or directly.


Profile

The Profile tab manages your account identity.

User Information

Field Required Description
Email Address Yes Your login email
Full Name No Display name across the platform
First Name No Used in greetings and notifications
Last Name No Used in greetings and notifications
Organization No Your company or institution
Intended Usage No Brief description of how you use SDCStudio

Your account type is shown as a read-only badge: User, Staff, or Superuser.

Click Save Changes to update your profile.

Changing Your Password

  1. Click Change Password to expand the password form
  2. Enter your Current Password
  3. Enter a New Password (minimum 8 characters)
  4. Enter it again under Confirm New Password
  5. Click Change Password

Preferences

The Preferences tab controls display settings, modeler identity, and ontology configuration.

Display Preferences

Theme: Choose between Light and Dark mode. The change takes effect immediately.

Language: Select your preferred UI language: - English - Español - Português Brasileiro - Français

Items Per Page: Control default pagination for lists and tables. Options: 10, 25 (default), 50, or 100.

Notifications: two checkboxes, Email notifications and Model publication alerts. Both are disabled and marked "coming soon"; nothing is sent yet.

Modeler Information

These fields are embedded in generated schemas and outputs:

Field Required Description
Modeler Name Yes Your name as it appears in generated models
Modeler Email Yes Your contact email in generated models
Default Project No The project the assembly API builds in when none is named; every account starts with one, named after you and private (choose another here, or No default project)
Preferred Ontology Service No Custom ontology service URL for semantic discovery

Preferred Ontologies

A dual-pane transfer list lets you select which ontologies are prioritized during semantic discovery:

  • Available Ontologies (left pane): all ontologies not yet selected
  • Selected Ontologies (right pane): your preferred ontologies

Use the arrow buttons to move ontologies between panes. Click Manage Ontologies to open the Ontologies page (/app/ontologies), where Upload Ontology accepts a .ttl, .owl, .rdf, .n3, or .nt file up to 10 MB with a namespace abbreviation (at most 15 characters), a namespace URI, a description, an organization, and an access level (Private, Team, Corporate, or Public).

Ontology Weight Multipliers

Fine-tune how strongly different ontology sources are weighted during semantic discovery:

Weight Range Default Purpose
Preferred Ontology Weight 0.1 - 5.0 1.5 Boost for your selected preferred ontologies
Standard Ontology Weight 0.1 - 5.0 1.0 Baseline weight for standard ontologies
External Source Weight 0.1 - 5.0 0.8 Weight for external ontology sources

Project Filter

Enable Filter components by project to restrict component lists to only the currently selected project. When unchecked, components from all your projects are shown.

Click Save Modeler Settings to apply changes.


Teams

Every project has one team, created with the project (for the default project made with your account, at the first team action, such as an invitation). The Teams Management tab is the view across your projects: Your Teams lists every team you are on, with the team's name and member count; select one to see its members, each with name, email and role, and an invitation not yet accepted marked Pending Invitation.

Owners and admins invite, remove and rename from the tab; roles are changed on the project's own page, in its Members section: invite by email with a role of Member or Admin (the invitation link is valid for seven days), change a member's role, or remove a member. Owners and admins manage members; the owner's row is fixed.

Roles

Role Build in the project Edit any component Publish and retire Manage members Delete the project
Owner Yes Yes Yes Yes Yes
Admin Yes Yes Yes Yes No
Member Yes Own unpublished only No No No

Members see everything in the project, including drafts and uploaded data sources, and each person pays for their own work from their own wallet. See Teams.

Wallet

The Wallet tab manages your credit balance for pay-as-you-go billing. Credits are sold at 1,000 per US dollar: purchases are in dollars, balances and costs are in credits.

Balance

Your current balance is displayed with color-coded status:

  • Green (> 25,000 credits): plenty of balance
  • Yellow (10,000 - 25,000 credits): consider buying more
  • Red (< 10,000 credits): buy more soon

Adding Funds

  1. Click Add Funds
  2. Select a purchase amount: $10 (10,000 credits), $25 (25,000), $50 (50,000), $100 (100,000), or $250 (250,000)
  3. Click Pay to open Stripe Checkout
  4. Complete payment; your balance updates within seconds

Per-Operation Costs

Operation Cost
Mint component 100 credits
Assemble model 500 credits
Download app (the first download of each model; later ones free) 1,500 credits
Settlement receipt 1,000 credits

These four are the only charges. Editing, publishing, generating a package and uploading spend nothing.

Auto-Reload

Auto-reload is on by default (the checkbox Automatically reload when balance drops below threshold); clear it to turn it off. Its fields:

  • Reload below (credits): the credit balance that triggers a purchase (default: 10,000 credits)
  • Purchase amount (USD): how much to charge your card each time (default: $50.00)

Click Save Settings to apply. Auto-reload uses the payment method saved from your most recent Stripe Checkout.

Transaction History

View all wallet activity in the transaction table. Filter by type (Reload, Mint Component, Assemble Model, Validate, Sign, Migration, Adjustment) and click Export CSV to download it.

For full details, see the Wallet & Billing Guide.


API Keys

The API Keys tab lets you create named keys for the tools that call SDCStudio: SDCBench, the Obsidian template, Form2SDCTemplate, SDC Agents, sdcmodeler, or your own scripts.

Creating a Key

  1. Enter a Name that says what will hold the key (for example, "SDCBench on my laptop"); the name is required
  2. Choose its Scopes: Read (every GET) is always on; Build lets it write without spending; Spend lets it charge your wallet (minting, assembling, downloading an app, settling)
  3. Optionally set a Spending limit (credits) (blank means no limit) and Expires in (days) (blank means never)
  4. Click Create key
  5. Copy the key immediately: it is shown only once and cannot be retrieved later
  6. Click Done and store the key securely

A key handed to an agent should carry a limit. You can have up to 25 active keys. The table lists each key's name, prefix, creation date, last use, scopes, spending against its limit, and status (Active, Expired or Revoked); revoked keys are hidden until you click Show N revoked. A key without Build is refused writes, and one without Spend, or past its limit, is refused charges, both with 403 before anything is built; see API Keys.

Using Your Key

A key is sdcs_ followed by 48 hexadecimal characters. Send it in the Authorization header with the Token scheme:

Authorization: Token sdcs_your_api_key_here

The key works with the SDCStudio APIs, including the public catalog endpoints /api/v1/catalog/components/ and /api/v1/catalog/dms/.

Rotating and Revoking

Each key is rotated or revoked on its own row:

  • Rotate Key: after you click Confirm, issues a replacement with the same scopes, limit and expiry and a fresh spending count; the current key stops working at once, so update the tool that holds it
  • Revoke Key: after you click Confirm, disables that key permanently; other keys are unaffected, and you can create a new one later

Next Steps

Now that your account is configured:

  1. Quick Start Guide: create your first data model
  2. System Overview: understand the platform architecture
  3. User Guides: learn workflows and advanced features

Getting Help


Ready to start? Continue with the Quick Start Guide to create your first data model.