Ximilar · Authentication Profile

Ximilar Authentication

Authentication

Ximilar uses a single long-lived API token issued per account in the Ximilar App. There is no OAuth 2.0, no OpenID Connect, no mTLS and no scope system; every request on every service carries the same token. Derived from the provider's own Quickstart page, not from a specification — Ximilar publishes no OpenAPI, so there are no securitySchemes to aggregate.

Ximilar secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

Computer-VisionImage RecognitionVisual SearchImage TaggingMachine-LearningArtificial IntelligenceOCRCollectiblesFashionE-CommerceMCPImage Processing
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

ximilarToken apiKey
· in: header ()

Source

Authentication Profile

ximilar-authentication.yml Raw ↑
generated: '2026-08-28'
method: searched
source: https://docs.ximilar.com/quickstart
docs: https://docs.ximilar.com/quickstart
provider: Ximilar
providerId: ximilar
description: >-
  Ximilar uses a single long-lived API token issued per account in the Ximilar App. There
  is no OAuth 2.0, no OpenID Connect, no mTLS and no scope system; every request on every
  service carries the same token. Derived from the provider's own Quickstart page, not
  from a specification — Ximilar publishes no OpenAPI, so there are no securitySchemes to
  aggregate.
summary:
  types: [apiKey]
  api_key_in: [header]
  oauth2_flows: []
  openid_connect: false
  mutual_tls: false
  scopes: none
schemes:
  - name: ximilarToken
    type: apiKey
    in: header
    parameter_name: Authorization
    value_format: 'Token <API_TOKEN>'
    applies_to: all api.ximilar.com services
    sources: [https://docs.ximilar.com/quickstart]
    note: >-
      "All requests to the Ximilar API must include your API token in the request headers.
      This applies to all HTTP methods: GET, POST, PUT, and DELETE." Content-Type must be
      application/json.
token_management:
  issue_url: https://app.ximilar.com/my-plan/settings
  signup_url: https://app.ximilar.com/register
  rotation_documented: false
  expiry_documented: false
  scope_model: none — one account token grants every service the active plan includes
additional_request_identity:
  - header: collection-id
    applies_to: Visual Search / similarity services
    description: >-
      Search and similarity operations address a specific image collection via a
      collection-id request header rather than a path parameter. Collections must be
      created by Ximilar administrators before use.
    source: https://docs.ximilar.com/visual-search/overview
  - field: workspace
    applies_to: Computer Vision Platform, VLM, async requests
    description: Workspace UUID; defaults to the account's default workspace when omitted.
mcp_auth:
  type: api-key
  env: XIMILAR_API_KEY
  note: The local MCP server takes the same account token via an environment variable.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com

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/ximilar-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 email required.

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