Vijil · Authentication Profile

Vijil Authentication

Authentication

Vijil secures its APIs with http and cookie across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyArtificial IntelligenceAI AgentsAgent SecurityAI SafetyTrustRed TeamingGuardrailsLLM SecurityEvaluationObservabilityMCP
Methods: http, cookie Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer
jwtCookie cookie

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://docs.vijil.ai/developer-guide/agentic/quickstart
docs: https://docs.vijil.ai/developer-guide/cli/setup
note: >-
  The published OpenAPI (openapi/vijil-openapi-original.json) declares no
  components.securitySchemes, so this profile is captured from the Vijil docs
  (Quickstart, CLI Setup, Manage API Keys) rather than derived from the spec.
summary:
  types: [http, cookie]
  http_schemes: [bearer]
  bearer_format: JWT
  api_key_in: []
  oauth2_flows: []
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    bearerFormat: JWT
    description: >-
      Primary authentication for the REST API. Exchange email + password at
      POST /v1/auth/jwt/login for a JWT access token, then send it as
      `Authorization: Bearer <token>` on every request. Tokens expire; a 401
      means the token must be refreshed (POST /v1/auth/jwt/refresh) or re-issued.
      Team scope is derived from the token; most operations act on the active team.
    login_operation: openapi/vijil-openapi-original.json#jwt_login_v1_auth_jwt_login_post
    refresh_operation: openapi/vijil-openapi-original.json#jwt_refresh_v1_auth_jwt_refresh_post
    sources: [https://docs.vijil.ai/developer-guide/agentic/quickstart]
  - name: jwtCookie
    type: cookie
    cookie_auth: true
    description: >-
      Browser/console flow — POST /v1/auth/jwt/login can set the JWT in an
      httpOnly cookie; POST /v1/auth/jwt/logout clears it. Used by the Vijil
      Console web UI.
    sources: [https://docs.vijil.ai/api-reference/teams/jwt-login]
model_hub_keys:
  description: >-
    Separate from platform auth: Vijil stores per-team "model hub" API keys
    (OpenAI, Together, custom hubs, Vertex AI, DigitalOcean) used to query the
    model under evaluation. Managed via the Console UI (Keys), the Python client
    (client.api_keys.list/create/delete/modify/rename), and supplied inline when
    registering an Agent (agent_url + api_key).
  docs: https://docs.vijil.ai/legacy/tutorials/manage-api-keys
cli_auth:
  init: vijil auth init --url https://<console-gateway>
  login: vijil auth login
  storage: ~/.vijil/config.yaml
  docs: https://docs.vijil.ai/developer-guide/cli/setup

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/vijil-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.