ComOS

ComOS is an AI-native operating system for commerce run by ComOS Federation, Inc. (a Delaware corporation). It describes itself as a federation of federations: every business on it runs a complete world of its own (catalog, customers and agents) while the network holds one economy with one mint, one ledger and one settlement rail. Businesses can install a ComOS node on a machine they own or start free in the ComOS cloud, paying only when money moves. The site publishes machine-readable surfaces for agents, including /llms.txt, /.well-known/comos-vendor.json and /openapi.json. The canonical brand site is comos-federation.com; comos-portal.com serves the same ComOS pages.

ComOS publishes 1 API contract indexed on the APIs.io network: Federation Gateway. Tagged areas include Company, Commerce, AI Agents, Operating System, and Federation.

The ComOS catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

ComOS’s developer surface includes changelog, authentication, support, documentation, engineering blog, pricing, and 33 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.3/100 developing Agent 53/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessSelf serve

1 published contract 1 MCP Servers 3 Agent Skills

Company Commerce AI Agents Operating System Federation Payments Ledger Self-Hosted E-Commerce MCP

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 51.3/100 · developing

Contract Quality 8.6 / 19

Developer Ergonomics 7.4 / 15

Access Clarity 8.9 / 15

Operational Transparency 2.3 / 10

Contract Governance 3.2 / 9

Discoverability 6.1 / 8

Regulatory Posture 6.2 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 53/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 8 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/comos-portal-com/"><img src="https://apis.io/badge/comos-portal-com/card.svg" alt="ComOS on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter Ask about this →
Consent & Bot Identity +3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures Ask about this →

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 45.7 — up to +13.6 composite points Ask about this →
Developer Ergonomics scores 49.4 — up to +10.1 composite points Ask about this →
Operational Transparency scores 23.8 — up to +9.9 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/comos-portal-com/apis.yml: open an issue on github.com/api-evangelist/comos-portal-com to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent2Agent

measured — observed by APIs.io (flavored)

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

ComOS Federation Gateway

The ComOS commerce network gateway, fronting every merchant tenant. Each operation is a federation tool exposed as POST /tools/{tool_name}; pass tenant_id to scope a call to a m...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

ComOS Federation Gateway MCP Server

Official hosted MCP server for the ComOS commerce network. One federated, stateless Streamable HTTP endpoint fronts every merchant tenant; pass tenant_id to scope a call. initia...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

become-a-vendor

AGENT SKILL

shop-the-network

AGENT SKILL

verify-the-network

AGENT SKILL

ComOS API pricing

Prices published by ComOS.

Plan	Price
ComOS (single flat rate)	No subscription. No rent.

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

ComOS Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

ComOS Rate Limits

0 limits

RATE LIMITS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Comos Portal Com Context

1 classes · 5 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

ComOS API Rules

39 rules · 36 error-severity 2 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

ComOS Openapi Overlay

24 actions · update · comos-portal-com-openapi.yml

DERIVED

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

ToolCallResult

5 properties

JSON SCHEMA

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

ComOS Authentication

3 schemes

SECURITY

ComOS Domain Security

TLSv1.3 · DMARC

SECURITY

ComOS Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

ComOS Scopes

72 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

ComOS Agentic Access

128 operations · 128 acting · 2 human-in-the-loop

128 operations · 128 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 6

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgentSkill

LLMsTxt

MCPServer

WellKnown

LLMsTxt

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Idempotency

Conventions

Lifecycle

Conformance

Scroll for all 8

Build 4

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

IntegrationEdges

SDKs

Packages

Access & Security 8

Authentication, authorization, and security posture

Authentication

OAuthScopes

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

TrustCenter

TrustCenter

Security

Security

Scroll for all 8

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

Overlay

Overlay

AgentCard

AgentCard

Hosts

Hosts

Source (apis.yml)

aid: comos-portal-com
name: ComOS
description: 'ComOS is an AI-native operating system for commerce run by ComOS Federation, Inc. (a Delaware corporation).
  It describes itself as a federation of federations: every business on it runs a complete world of its own (catalog, customers
  and agents) while the network holds one economy with one mint, one ledger and one settlement rail. Businesses can install
  a ComOS node on a machine they own or start free in the ComOS cloud, paying only when money moves. The site publishes machine-readable
  surfaces for agents, including /llms.txt, /.well-known/comos-vendor.json and /openapi.json. The canonical brand site is
  comos-federation.com; comos-portal.com serves the same ComOS pages.'
url: https://artifacts.apis.io/comos-portal-com/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-04 (modular-v1; was harvest)
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: high
  probe_state: covered
  source:
  - plans
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-04'
modified: '2026-11-04'
tags:
- Company
- Commerce
- AI Agents
- Operating System
- Federation
- Payments
- Ledger
- Self-Hosted
- E-Commerce
- MCP
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
image: https://comos-portal.com/comos-logo.svg
common:
- type: AgenticAccess
  url: agentic-access/comos-portal-com-agentic-access.yml
- type: Plans
  url: plans/comos-portal-com-plans-pricing.yml
- type: Spectral
  url: rules/comos-portal-com-rules.yml
- type: JSONLD
  url: json-ld/comos-portal-com-context.jsonld
- type: Vocabulary
  url: vocabulary/comos-portal-com-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/comos-portal-com-data-model.yml
- type: ChangeLog
  url: changelog/comos-portal-com-changelog.yml
- type: Idempotency
  url: conventions/comos-portal-com-conventions.yml
- type: Conventions
  url: conventions/comos-portal-com-conventions.yml
- type: Authentication
  url: authentication/comos-portal-com-authentication.yml
- type: OAuthScopes
  url: scopes/comos-portal-com-scopes.yml
- type: Lifecycle
  url: lifecycle/comos-portal-com-lifecycle.yml
- type: Conformance
  url: conformance/comos-portal-com-conformance.yml
- type: Overlay
  url: overlays/comos-portal-com-openapi-overlay.yaml
- type: LLMsTxt
  url: llms/comos-portal-com-llms.txt
- type: AgentCard
  url: a2a/comos-portal-com-a2a.yml
- type: ToolCrosswalk
  url: mcp/comos-portal-com-tool-crosswalk.yml
- type: MCPServer
  url: mcp/comos-portal-com-mcp.yml
- type: SecurityTxt
  url: well-known/comos-portal-com-security.txt
- type: SecurityTxt
  url: well-known/comos-portal-com-mcp-security.txt
- type: WellKnown
  url: well-known/comos-portal-com-well-known.yml
- type: Hosts
  url: hosts/comos-portal-com-hosts.yml
- type: IntegrationEdges
  url: integrations/comos-portal-com-integration-edges.yml
- type: SDKs
  url: packages/comos-portal-com-packages.yml
- type: Packages
  url: packages/comos-portal-com-packages.yml
- type: Support
  url: https://comos-portal.com/support
- type: Login
  url: https://comos-portal.com/login
- type: VulnerabilityDisclosure
  url: security/comos-portal-com-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/comos-portal-com-domain-security.yml
- type: Website
  url: https://comos-portal.com/
- type: Documentation
  url: https://comos-portal.com/docs
- type: Blog
  url: https://comos-portal.com/blog
- type: Pricing
  url: https://comos-portal.com/pricing
- type: TermsOfService
  url: https://comos-portal.com/terms
- type: PrivacyPolicy
  url: https://comos-portal.com/privacy
- type: TrustCenter
  url: https://comos-portal.com/trust
- type: Security
  url: https://comos-portal.com/security
- type: LLMsTxt
  url: https://comos-portal.com/llms.txt
apis:
- aid: comos-portal-com:comos-federation-gateway
  name: ComOS Federation Gateway
  description: The ComOS commerce network gateway, fronting every merchant tenant. Each operation is a federation tool exposed
    as POST /tools/{tool_name}; pass tenant_id to scope a call to a merchant. The provider states the OpenAPI is generated
    from the gateway's own live tool surface, the same tools served over its federated MCP endpoint (https://comos-portal.com/mcp,
    Streamable HTTP; discovery and read-only tools need no token, privileged writes use OAuth 2.1 + PKCE with per-tool scopes).
    The spec is served identically at comos-portal.com/openapi.json and comos-federation.com/openapi.json, and its servers[]
    names mcp.comos-federation.com, the canonical ComOS Federation brand domain.
  humanURL: https://comos-portal.com/docs
  baseURL: https://mcp.comos-federation.com
  tags:
  - Commerce
  - Federation
  - MCP
  - AI Agents
  properties:
  - type: OpenAPI
    url: openapi/comos-portal-com-openapi.yml
  - type: OpenAPI
    name: OpenAPI (provider-hosted)
    url: https://comos-portal.com/openapi.json
  - type: Documentation
    url: https://comos-portal.com/docs
  - type: GettingStarted
    url: https://comos-portal.com/get-started
  - type: JSONSchema
    url: json-schema/comos-portal-com-tool-call-result-schema.json
x-coverage:
  state: covered
  reason: identity-verified
  detail: Name ComOS from <title>/og:site_name; legal entity ComOS Federation, Inc. from /terms (schema.org Organization,
    url comos-federation.com). /get-started, /support and /start return the identical homepage SPA shell (soft fallback) so
    were not recorded; /login and /register were not fetched (probe-safety rule 3) and not recorded.
  evidence:
  - url: https://comos-portal.com/
    status: 200
  - url: https://comos-portal.com/docs
    status: 200
  - url: https://comos-portal.com/blog
    status: 200
  - url: https://comos-portal.com/pricing
    status: 200
  - url: https://comos-portal.com/terms
    status: 200
  - url: https://comos-portal.com/privacy
    status: 200
  - url: https://comos-portal.com/trust
    status: 200
  - url: https://comos-portal.com/security
    status: 200
  - url: https://comos-portal.com/llms.txt
    status: 200
  - url: https://comos-portal.com/comos-logo.svg
    status: 200
  - url: https://comos-federation.com/comos-logo.svg
    status: 200
x-enrichment:
  date: '2026-11-04'
  status: enriched
  artifacts_added: 52
  pass: modular-v1
  engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic

ComOS API — frequently asked questions

Does ComOS have an API?

Yes. APIs.io lists 1 API from ComOS, including ComOS Federation Gateway.

Is there an OpenAPI specification for the ComOS API?

Yes. APIs.io indexes 1 OpenAPI specification for ComOS, each linked for download from this page.

How do I authenticate with the ComOS API?

ComOS documents its authentication (3 schemes). The details are profiled on APIs.io as ComOS Authentication.

How much does the ComOS API cost?

ComOS publishes its prices; its ComOS (single flat rate) plan is No subscription. No rent. as of 2026-11-04. APIs.io lists 1 pricing plan for ComOS, with each plan's price, limits and inclusions under Pricing on this page.

Does ComOS have an MCP server?

Yes. APIs.io lists 1 MCP server for ComOS: Official hosted MCP server for the ComOS commerce network. One federated, stateless Streamable HTTP endpoint fronts every merchant tenant; pass tenant_id to scope a call. initialize returned serverInf

Is the ComOS API ready for AI agents?

ComOS has a Kin Score of 51.3 out of 100 (developing) and an Agent Readiness score of 52.6 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/comos-portal-com"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/comos-portal-com/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/comos-portal-com/evidence"

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.

GitHub Google LinkedIn

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