IDENTITY BOUNDARY

MASIDYN ACCESS

Local ownership. Verified hosted identity.

The production path is user → MasiDyn Limited → authenticate → authenticated user → MasiDyn. Authentication creates a MasiDyn Free account and unlocks persistent chat, tenant-private memory, explicit tool grants, and orchestration. MasiDyn is always the router.

You never paste an API key here or go to another company for one. MasiDyn Free is the default engine and works with nothing configured.

LOCAL / PERSONAL

Your machine remains yours.

A loopback MasiDyn runtime remains local and does not depend on a MasiDyn cloud account. Its operating-system boundary is separate from hosted multi-user authentication.

localbase_url
base_url = "http://127.0.0.1:11435"

HOSTED / MULTI-USER

Authenticate before personalization.

Anonymous users receive MasiDyn Limited. Only a server-verified OAuth session can resolve a real user and unlock full MasiDyn.

THIRD-PARTY SITES / OIDC 1.0

“Sign in with MasiDyn” button kit.

Any website, SaaS product, or CLI can offer Sign in with MasiDyn via standard OAuth 2.0 + OpenID Connect 1.0 with mandatory PKCE S256. Register your exact callback URI in /dashboard/apps and drop in the accessible HTML/CSS button below.

ACCESSIBLE BUTTON PREVIEW

Zero third-party scripts, keyboard focusable, WCAG AA contrast.

Sign in with MasiDyn
html + csssign-in-with-masidyn.html
<!-- Sign in with MasiDyn — Accessible OAuth 2.0 + OIDC 1.0 Button Kit -->
<style>
  .masidyn-signin-btn {
    display: inline-flex;
    align-items: center;
    gap: 10px;
    padding: 11px 18px;
    border-radius: 8px;
    border: 1px solid rgba(6, 182, 212, 0.45);
    background: linear-gradient(135deg, #0b1120 0%, #111827 100%);
    color: #f8fafc;
    font: 600 14px/1.2 -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
    text-decoration: none;
    cursor: pointer;
    transition: border-color 0.16s ease, box-shadow 0.16s ease;
  }
  .masidyn-signin-btn:hover {
    border-color: #06b6d4;
    box-shadow: 0 4px 16px rgba(6, 182, 212, 0.22);
  }
  .masidyn-signin-btn:focus-visible {
    outline: 2px solid #06b6d4;
    outline-offset: 2px;
  }
  .masidyn-signin-glyph {
    width: 18px;
    height: 18px;
    border-radius: 5px;
    background: linear-gradient(135deg, #06b6d4, #2563eb);
    display: inline-block;
  }
</style>

<a
  class="masidyn-signin-btn"
  href="https://account.masidyn.dev/oauth/authorize?response_type=code&amp;client_id=YOUR_CLIENT_ID&amp;redirect_uri=https%3A%2F%2Fyour-site.example%2Fauth%2Fcallback&amp;scope=openid+profile+email&amp;code_challenge=YOUR_S256_CODE_CHALLENGE&amp;code_challenge_method=S256&amp;state=RANDOM_CSRF_STATE"
  aria-label="Sign in with MasiDyn"
>
  <span class="masidyn-signin-glyph" aria-hidden="true"></span>
  <span>Sign in with MasiDyn</span>
</a>

OpenID Connect 1.0 Provider Configuration

SettingValue
Issuerhttps://account.masidyn.dev
Discovery URLhttps://account.masidyn.dev/.well-known/openid-configuration
Authorization Endpointhttps://account.masidyn.dev/oauth/authorize
Token Endpointhttps://account.masidyn.dev/oauth/token
UserInfo Endpointhttps://account.masidyn.dev/oauth/userinfo
JWKS Public Keys URIhttps://account.masidyn.dev/oauth/jwks
Response / Grant Typeresponse_type=code · grant_type=authorization_code (implicit rejected)
PKCE RequirementRequired · code_challenge_method=S256 (>= 43 base64url chars)
ID Token SigningRS256 with kid rotation
Scopes Supportedopenid, profile, email, masidyn.workspace.read

OPTIONAL / CONNECTORS

MasiDyn connectors.

If you want MasiDyn to reach an additional AI provider, link it as a MasiDyn connector from your MasiDyn account. The connection is made by signing in with MasiDyn, not by pasting a key, and MasiDyn still routes every request. Nothing requires a connector: without one, MasiDyn Free handles the work.