Stilla · Authentication Profile

Stilla Authentication

Authentication

Stilla secures its APIs with oauth2 and openIdConnect across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, deviceCode, and refreshToken flow(s).

CompanyArtificial IntelligenceAI AgentsAgenticProductivityCollaborationMCPAutomationDeveloper ToolsEnterprise

Methods: oauth2, openIdConnect Schemes: 2 OAuth flows: authorizationCode, deviceCode, refreshToken API key in:

Security Schemes

OAuth2 oauth2

OpenIDConnect openIdConnect

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://api.stilla.ai/.well-known/oauth-authorization-server
docs: https://stilla.ai/docs/integrations/stilla-mcp
summary:
  types: [oauth2, openIdConnect]
  api_key_in: []
  oauth2_flows: [authorizationCode, deviceCode, refreshToken]
  provider: WorkOS AuthKit (login.stilla.ai)
schemes:
  - name: OAuth2
    type: oauth2
    issuer: https://login.stilla.ai
    authorization_endpoint: https://login.stilla.ai/oauth2/authorize
    token_endpoint: https://login.stilla.ai/oauth2/token
    device_authorization_endpoint: https://login.stilla.ai/oauth2/device_authorization
    introspection_endpoint: https://login.stilla.ai/oauth2/introspection
    jwks_uri: https://login.stilla.ai/oauth2/jwks
    registration_endpoint: https://login.stilla.ai/oauth2/register   # RFC 7591 dynamic client registration
    grant_types_supported: [authorization_code, refresh_token, "urn:ietf:params:oauth:grant-type:device_code"]
    code_challenge_methods_supported: [S256]                          # PKCE required
    token_endpoint_auth_methods_supported: [none, client_secret_post, client_secret_basic]
    client_id_metadata_document_supported: true
    scopes_supported: [openid, profile, email, offline_access]
  - name: OpenIDConnect
    type: openIdConnect
    openIdConnectUrl: https://login.stilla.ai/.well-known/openid-configuration
enterprise:
  # From https://stilla.ai/security
  sso: SAML
  provisioning: SCIM
  access_control: role-based permissions + full audit logs
notes: >-
  The Stilla REST API (api.stilla.ai) and the MCP server are protected by OAuth 2.0 /
  OIDC via WorkOS AuthKit. Bearer tokens are passed in the Authorization header. PKCE
  (S256) is mandatory, and clients may register dynamically. Enterprise tenants add
  SAML SSO and SCIM provisioning. The OpenAPI document at api.stilla.ai/openapi.json is
  gated behind login and not publicly retrievable.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/stilla-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.