Silmaril · Authentication Profile

Silmaril Authentication

Authentication

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

CompanyAI SecurityAI FirewallPrompt InjectionAgent SecurityRuntime SecurityGuardrailsMCPLLM SecurityDeveloper Tools
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode API key in: header

Security Schemes

FirewallApiKey apiKey
· in: header ()
McpOAuth oauth2

Source

Authentication Profile

silmaril-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://silmaril.dev/docs
docs: https://silmaril.dev/docs
summary:
  types: [apiKey, oauth2]
  api_key_in: [header]
  oauth2_flows: [authorizationCode]
schemes:
- name: FirewallApiKey
  type: apiKey
  in: header
  applies_to: Firewall classify API (SDKs) and LiteLLM guardrail endpoint
  detail: >-
    A Silmaril-issued API key is supplied to the Firewall client (SDK apiKey /
    api_key + tenant classify apiUrl) and passed as the `x-api-key` header when
    configuring the LiteLLM guardrail (SILMARIL_API_KEY + SILMARIL_GUARDRAIL_URL).
    Credentials are provisioned by Silmaril; the product is not self-serve yet.
- name: McpOAuth
  type: oauth2
  flow: authorizationCode
  provider: Auth0
  applies_to: Silmaril Firewall MCP evidence server (firewall-mcp.silmaril.dev)
  detail: >-
    The hosted MCP server uses OAuth via the customer's Auth0 organization with
    hosted OAuth discovery; the signed-in user's access is forwarded to the
    read-only evidence API. Access is scope-gated (aggregate/search tools need
    less access than full payload/trace tools).
notes: >-
  No OpenAPI is published, so this profile is searched from the developer docs
  and the MCP server repo rather than derived from a spec.