Order.co

Order.co (founded 2016 in New York as Negotiatus, rebranded to Order.co in 2021) is a procurement and finance-automation platform for mid-market and enterprise buyers: guided purchasing across a managed vendor catalog, purchase-order and approval workflow, accounts- payable automation, spend management and virtual cards, sold into multi-location operators in property management, hospitality, healthcare, retail, fitness, coworking, early childhood education, wellness, technology and nonprofit. The product connects to QuickBooks Online, NetSuite, Sage Intacct and Workday over API, and supports SSO through Okta and Ping Identity. Order.co publishes no developer portal, no API reference and no machine-readable specification for any of that - the procurement API is disclosed only to customers, and vendors receive API or EDI credentials during onboarding. What it does publish anonymously are two real, self-describing surfaces on its own hosts - the WordPress REST API behind www.order.co (blog, customer and vendor stories, ebooks, webinars, tools, 873 FAQ records, and the first-party industry and use-case taxonomies) and the Atlassian Statuspage v2 API on status.order.co - plus an llms.txt and a companion page written for language models.

Order.co publishes 5 API contracts indexed on the APIs.io network, including Components API, Incidents API, Maintenance API, and 2 more. Tagged areas include Company, Procurement, Spend Management, Accounts Payable, and Purchasing.

The Order.co catalog on APIs.io includes 1 Spectral governance ruleset.

Order.co’s developer surface includes authentication, code examples, engineering blog, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.5/100 thin ▬ flat Agent 30/100 agent ready Front door AI 6/6 dominant Heartbeat 40/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessOpen

2 published contracts 3 Agent Skills

Company Procurement Spend Management Accounts Payable Purchasing Vendor Management Payments Virtual Cards Finance Automation United States

Kin Score

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

Composite quality — 32.5/100 · thin

Contract Quality 3.4 / 21

Developer Ergonomics 4.8 / 17

Access Clarity 9.7 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 3.3 / 15

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 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 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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

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/orderco/"><img src="https://apis.io/badge/orderco/card.svg" alt="Order.co 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):

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
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

5 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 15.8 — up to +21.1 composite points
Developer Ergonomics scores 28.0 — up to +14.4 composite points
Operational Transparency scores 18.4 — up to +10.6 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/orderco/apis.yml: open an issue on github.com/api-evangelist/orderco 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.

OpenAPI

SPECTRAL

OpenAPI Overlays 2

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.

Orderco Content Overlay

13 actions · update · orderco-content-openapi.yml

DERIVED

Orderco Status Overlay

9 actions · update · orderco-status-openapi.yml

DERIVED

2 fields

EXAMPLE

Orderco Status Summary

5 fields

EXAMPLE

Scroll for all 11

Security Posture 2

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

Orderco Authentication

0 schemes

SECURITY

Orderco Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Login

Demo

Demo

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Examples

Examples

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 6

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

LinkedIn

Careers

Careers

Press

Press

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: orderco
name: Order.co
description: 'Order.co (founded 2016 in New York as Negotiatus, rebranded to Order.co in 2021) is a procurement and finance-automation
  platform for mid-market and enterprise buyers: guided purchasing across a managed vendor catalog, purchase-order and approval
  workflow, accounts- payable automation, spend management and virtual cards, sold into multi-location operators in property
  management, hospitality, healthcare, retail, fitness, coworking, early childhood education, wellness, technology and nonprofit.
  The product connects to QuickBooks Online, NetSuite, Sage Intacct and Workday over API, and supports SSO through Okta and
  Ping Identity. Order.co publishes no developer portal, no API reference and no machine-readable specification for any of
  that - the procurement API is disclosed only to customers, and vendors receive API or EDI credentials during onboarding.
  What it does publish anonymously are two real, self-describing surfaces on its own hosts - the WordPress REST API behind
  www.order.co (blog, customer and vendor stories, ebooks, webinars, tools, 873 FAQ records, and the first-party industry
  and use-case taxonomies) and the Atlassian Statuspage v2 API on status.order.co - plus an llms.txt and a companion page
  written for language models.'
url: https://raw.githubusercontent.com/api-evangelist/orderco/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: enriched
x-tier-reason: enrichment-pipeline
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 35
  pass: local-v1
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.order.co/wp-content/themes/order/assets/img/logos/order.svg
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Procurement
- Spend Management
- Accounts Payable
- Purchasing
- Vendor Management
- Payments
- Virtual Cards
- Finance Automation
- United States
apis:
- aid: orderco:orderco-components-api
  name: Order.co Components API
  description: The individual services Order.co reports health for.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Components
  properties:
  - type: OpenAPI
    url: openapi/orderco-components-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-incidents-api
  name: Order.co Incidents API
  description: Open and historical incidents with their dated updates.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Incidents
  properties:
  - type: OpenAPI
    url: openapi/orderco-incidents-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-maintenance-api
  name: Order.co Maintenance API
  description: Scheduled maintenance windows.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Maintenance
  properties:
  - type: OpenAPI
    url: openapi/orderco-maintenance-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:orderco-status-api
  name: Order.co Status API
  description: The rollup status indicator for the whole page.
  humanURL: https://status.order.co/
  baseURL: https://status.order.co/api/v2
  tags:
  - Status
  properties:
  - type: OpenAPI
    url: openapi/orderco-status-api-openapi.yml
  - type: APIReference
    url: https://status.order.co/api
  - type: StatusPage
    url: https://status.order.co/
  - type: Examples
    url: examples/orderco-status-summary.json
  - type: Examples
    url: examples/orderco-status-components.json
  - type: Examples
    url: examples/orderco-status-incidents.json
  - type: Examples
    url: examples/orderco-content-discovery.json
  - type: Examples
    url: examples/orderco-content-types.json
  - type: Examples
    url: examples/orderco-content-industries.json
  - type: Examples
    url: examples/orderco-content-customer-stories.json
- aid: orderco:order-co-website-wordpress-rest
  name: Order.co Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Order.co website at www.order.co: the route index of the site''s
    content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://www.order.co/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  x-platform: wordpress
  x-platform-surface: rest
  properties:
  - type: Documentation
    url: https://www.order.co/wp-json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/orderco-content-overlay.yaml
- type: Authentication
  url: authentication/orderco-authentication.yml
- type: Conventions
  url: conventions/orderco-conventions.yml
- type: ErrorCatalog
  url: errors/orderco-problem-types.yml
- type: Lifecycle
  url: lifecycle/orderco-lifecycle.yml
- type: StatusPage
  url: https://status.order.co/
- type: Conformance
  url: conformance/orderco-conformance.yml
- type: DataModel
  url: data-model/orderco-data-model.yml
- type: DomainSecurity
  url: security/orderco-domain-security.yml
- type: WellKnown
  url: well-known/orderco-well-known.yml
- type: LLMsTxt
  url: llms/orderco-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Examples
  url: examples/orderco-content-discovery.json
- type: Website
  url: https://www.order.co/
- type: Blog
  url: https://www.order.co/blog/
- type: BlogRSS
  url: https://www.order.co/blog/feed/
- type: Login
  url: https://app.order.co/login
- type: GitHubOrganization
  url: https://github.com/Negotiatus
- type: LinkedIn
  url: https://www.linkedin.com/company/order-company
- type: PrivacyPolicy
  url: https://www.order.co/privacy-policy/
- type: TermsOfService
  url: https://www.order.co/terms-and-conditions/
- type: Careers
  url: https://www.order.co/careers/
- type: Press
  url: https://www.order.co/newsroom/
- type: Demo
  url: https://www.order.co/demo/
- type: Integrations
  url: https://www.order.co/accounting-integrations/

Order.co API — frequently asked questions

Does Order.co have an API?

Yes. APIs.io lists 5 APIs from Order.co, including Order.co Components API, Order.co Incidents API and Order.co Maintenance API, and 2 more.

Is there an OpenAPI specification for the Order.co API?

Yes. APIs.io indexes 4 OpenAPI specifications for Order.co, each linked for download from this page.

How do I authenticate with the Order.co API?

Order.co uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Orderco Authentication.

Is the Order.co API ready for AI agents?

Order.co has a Kin Score of 32.5 out of 100 (thin) and an Agent Readiness score of 29.9 (agent-ready), 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/orderco"

All providers

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

Every operation they expose

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

How their score was established

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