ComOS · Authentication Profile

ComOS Authentication

Authentication

ComOS declares 3 security scheme(s) across its OpenAPI definitions.

CompanyCommerceAI AgentsOperating SystemFederationPaymentsLedgerSelf-HostedE-CommerceMCP
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

anonymous none
ComOS OAuth 2.1 oauth2
node signature signature

Source

Authentication Profile

Raw ↑
generated: '2026-11-04'
method: searched
source:
- https://comos-portal.com/.well-known/oauth-authorization-server
- https://comos-portal.com/.well-known/oauth-protected-resource
- https://comos-portal.com/.well-known/mcp/server-card.json
- https://comos-portal.com/security
- https://comos-portal.com/ai.txt
docs: https://comos-portal.com/security
summary: Discovery, shopping and read-only introspection tools need no token; privileged writes use OAuth 2.1 + PKCE with per-tool scopes, and tokenless writes deny (llms.txt / ai.txt). The OpenAPI itself declares no securitySchemes.
schemes:
- type: none
  name: anonymous
  description: Discovery, shopping, and read-only introspection need no token.
- type: oauth2
  name: ComOS OAuth 2.1
  issuer: https://mcp.comos-federation.com
  authorizationUrl: https://comos-portal.com/oauth/authorize
  tokenUrl: https://comos-portal.com/oauth/token
  grant_types:
  - authorization_code
  - refresh_token
  - client_credentials
  pkce:
  - S256
  token_endpoint_auth_methods:
  - none
  - client_secret_basic
  metadata: https://comos-portal.com/.well-known/oauth-authorization-server
  protected_resource_metadata: https://comos-portal.com/.well-known/oauth-protected-resource
  scopes_ref: scopes/comos-portal-com-scopes.yml
- type: signature
  name: node signature
  description: 'Self-hosted node calls (e.g. federation_node_report_in) are NODE-SIGNED rather than operator-token''d: the node signs the canonical envelope { node_id, nonce, timestamp, route } (OpenAPI description).'
sso: Enterprise SSO via OIDC (Okta, Azure AD, any provider) — stated on https://comos-portal.com/security

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/comos-portal-com-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.