Commerce One

Commerce One, Inc. was a Pleasanton, California B2B e-commerce software company and one of the defining names of the dot-com era, running the MarketSite marketplace and the Global Trading Web trading network. Founded in 1994 as DistriVision and renamed Commerce One in 1997, it went public in July 1999 and peaked in 2000 at a $21.5B market capitalization on $401M of revenue. It filed for bankruptcy in October 2004; its patent portfolio went to Novell subsidiary JGR Acquisitions and the Commerce One name to Perfect Commerce in 2006. The company no longer operates and has no live API or developer portal. What survives, and what this profile documents, is xCBL — the XML Common Business Library — a royalty-free library of 44 XML business documents across 9 namespaces, still published and downloadable from xcbl.org. Commerce One also created SOX, the schema language that influenced W3C XML Schema and JAXB.

Commerce One is listed with 1 API on the APIs.io network. Tagged areas include Company, B2B, E-Commerce, Procurement, and Supply Chain.

Commerce One’s developer surface includes documentation, API reference, getting-started guide, support, FAQ, code examples, changelog, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

0.0/100 minimal ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company B2B E-Commerce Procurement Supply Chain XML EDI Schema Marketplace Defunct

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 0.0/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 0.0 / 9

Regulatory Posture 2.2 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/commerce-one/"><img src="https://apis.io/badge/commerce-one/card.svg" alt="Commerce One 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points

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.

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/commerce-one/apis.yml: open an issue on github.com/api-evangelist/commerce-one 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Procurement and B2B Buying (source-to-pay suites, spend management)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

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.

XML

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

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

xCBL — XML Common Business Library

xCBL 4.0 is a royalty-free library of XML business documents and reusable components for business-to-business e-commerce, published by Commerce One and still distributed from xc...

Security Posture 1

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

Commerce One Domain Security

no transport/DNS hardening detected

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Vocabulary

ErrorCatalog

Conformance

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

Examples

Examples

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

FAQ

FAQ

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Source (apis.yml)

aid: commerce-one
name: Commerce One
description: Commerce One, Inc. was a Pleasanton, California B2B e-commerce software company and one of the defining names
  of the dot-com era, running the MarketSite marketplace and the Global Trading Web trading network. Founded in 1994 as DistriVision
  and renamed Commerce One in 1997, it went public in July 1999 and peaked in 2000 at a $21.5B market capitalization on $401M
  of revenue. It filed for bankruptcy in October 2004; its patent portfolio went to Novell subsidiary JGR Acquisitions and
  the Commerce One name to Perfect Commerce in 2006. The company no longer operates and has no live API or developer portal.
  What survives, and what this profile documents, is xCBL — the XML Common Business Library — a royalty-free library of 44
  XML business documents across 9 namespaces, still published and downloadable from xcbl.org. Commerce One also created SOX,
  the schema language that influenced W3C XML Schema and JAXB.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: http://xcbl.org/images/xCBLtop.gif
url: https://raw.githubusercontent.com/api-evangelist/commerce-one/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- canaan-partners
x-tier: stub
x-tier-reason: portfolio-lead
x-status: defunct
x-defunct-date: 2004-10
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- B2B
- E-Commerce
- Procurement
- Supply Chain
- XML
- EDI
- Schema
- Marketplace
- Defunct
tags_raw:
- Company
- B2B
- eCommerce
- Procurement
- Supply Chain
- XML
- EDI
- Schema
- Marketplace
- Defunct
apis:
- aid: commerce-one:xcbl
  name: xCBL — XML Common Business Library
  description: 'xCBL 4.0 is a royalty-free library of XML business documents and reusable components for business-to-business
    e-commerce, published by Commerce One and still distributed from xcbl.org. It is a document-exchange vocabulary rather
    than an HTTP API: 44 business documents across a shared core namespace and eight functional-area namespaces (order management,
    pre-order management, financial, materials management, message management, application integration, catalog, statistics
    and forecasting). Version 4.0, released March 2003, is the first to use W3C XML Schema (XSDL) as its canonical form, replacing
    Commerce One''s own SOX schema language, and represents an initial alignment with OASIS UBL. The distribution ships 709
    .xsd modules plus valid sample instances.'
  humanURL: http://xcbl.org/xcbl40/xcbl40.shtml
  baseURL: http://xcbl.org
  image: http://xcbl.org/images/xCBLtop.gif
  tags:
  - XML
  - Schema
  - B2B
  - Procurement
  - Invoicing
  - Catalog
  properties:
  - type: Documentation
    url: http://xcbl.org/xcbl40/documentation.shtml
  - type: APIReference
    url: http://xcbl.org/xcbl40/documentation/listofdocuments.shtml
  - type: Vocabulary
    url: vocabulary/commerce-one-xcbl-vocabulary.yml
  - type: Examples
    url: examples/_index.yml
  - type: ErrorCatalog
    url: errors/commerce-one-problem-types.yml
  - type: Conformance
    url: conformance/commerce-one-conformance.yml
  - type: ChangeLog
    url: changelog/commerce-one-changelog.yml
  - type: Lifecycle
    url: lifecycle/commerce-one-lifecycle.yml
common:
- type: DeveloperPortal
  url: http://xcbl.org/
- type: Documentation
  url: http://xcbl.org/xcbl40/documentation.shtml
- type: APIReference
  url: http://xcbl.org/xcbl40/documentation/listofdocuments.shtml
- type: GettingStarted
  url: http://xcbl.org/about.shtml
- type: Support
  url: http://xcbl.org/devresources.shtml
- type: FAQ
  url: http://xcbl.org/faq.shtml
- type: TermsOfService
  url: http://xcbl.org/license.shtml
- type: Vocabulary
  url: vocabulary/commerce-one-xcbl-vocabulary.yml
- type: Examples
  url: examples/_index.yml
- type: ErrorCatalog
  url: errors/commerce-one-problem-types.yml
- type: Conformance
  url: conformance/commerce-one-conformance.yml
- type: ChangeLog
  url: changelog/commerce-one-changelog.yml
- type: Lifecycle
  url: lifecycle/commerce-one-lifecycle.yml
- type: WellKnown
  url: well-known/commerce-one-well-known.yml
- type: DomainSecurity
  url: security/commerce-one-domain-security.yml
- type: LLMsTxt
  url: llms/commerce-one-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 10
  pass: local-v1

Commerce One API — frequently asked questions

Does Commerce One have an API?

Yes. APIs.io lists 1 API from Commerce One, including xCBL — XML Common Business Library.

Is the Commerce One API ready for AI agents?

Commerce One has a Kin Score of 0.0 out of 100 (minimal) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.

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/commerce-one"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/commerce-one/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/commerce-one/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.