Chemaxon · Authentication Profile

Chemaxon Authentication

Authentication

Chemaxon declares 4 security scheme(s) across its OpenAPI definitions.

CompanyCheminformaticsChemistryDrug DiscoveryLife SciencesMolecular ModelingSoftware Development Kits
Methods: Schemes: 4 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic
trustedClient http
scheme: basic
bearerToken http
scheme: bearer
none (self-hosted JChem Microservices) none

Source

Authentication Profile

Raw ↑
generated: '2026-11-03'
method: searched
source: https://docs.chemaxon.com/latest/compound-registration_api-authentication.html
docs: https://docs.chemaxon.com/latest/compound-registration_api-authentication.html
note: None of the nine saved OpenAPI documents declares securitySchemes (derive-authentication.py found 0). Compound Registration documents three methods; JChem Microservices ships without authentication (FAQ - "How to add authentication to JChem Microservices? It is supported through external beans").
schemes:
- name: basicAuth
  type: http
  scheme: basic
  applies_to: Compound Registration REST API (/RegistryCxn/rest)
  description: Authorization header with the base64 encoded username:password pair.
- name: trustedClient
  type: http
  scheme: basic
  applies_to: Compound Registration REST API
  description: 'Authentication for trusted 3rd party clients: base64 client:secret in Authorization plus headers "Grant-Type: client_credentials" and "Reg-User: <username>" (the impersonated Compound Registration user whose permissions apply).'
  headers: [Authorization, Grant-Type, Reg-User]
- name: bearerToken
  type: http
  scheme: bearer
  applies_to: SaaS Compound Registration on Chemaxon Cloud
  description: Bearer token obtained in the browser from https://<client>.cloud.chemaxon.com/resources/apikey after login via Chemaxon Cloud IAM; usable "for a limited time".
- name: none (self-hosted JChem Microservices)
  type: none
  applies_to: JChem Microservices
  docs: https://docs.chemaxon.com/latest/jchem-microservices_faq-and-known-issues.html
  description: No built-in authentication; operators add it through external Spring beans (filter/endpoint).

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/chemaxon-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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