Cedarai

Cedar AI builds ARMS (Automated Rail Management System), a cloud-native, AI-powered transportation management platform for railroads, industrial shippers, transload and intermodal terminals, and fleet/car owners. The ARMS External API exposes REST and gRPC services for railcar inventory and history, waybills and bills of lading, work orders and train movements, switching and class lists, charges, shipper invoices and quotes, truck load tenders, network structure, and threaded notes (Linda) with AI summaries — plus Ed25519-signed webhooks for real-time operational events, across US (cedarai.com) and EU (cedarai.se) regions. Backed by Felicis.

Cedarai publishes 9 API contracts indexed on the APIs.io network, including ChargeService API, Equipment History API, Ims API, and 6 more. Tagged areas include Company, Rail, Transportation, Logistics, and Freight.

The Cedarai catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Cedarai’s developer surface includes engineering blog, documentation, API reference, getting-started guide, authentication, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

40.8/100 developing ▬ flat Agent 27/100 agent aware Front door AI 4/6 moderate Heartbeat 99/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

8 published contracts 3 Agent Skills

Company Rail Transportation Logistics Freight Supply ChainRailcar ManagementTransportation Management System Fleet Management Artificial Intelligence

What this lets a business do 3

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Supply Chain Management

BC-520

ImsTruckLoadTenderService

Freight Billing & Settlement Management

BC-2530

InvoicesService

POST /shipper/invoices/{id}/vouchers GET /shipper/invoices

Transport Operations Management

BC-2420

WorkOrderService

POST /t/v1/setout-cars POST /t/v1/depart-train

Kin Score

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

Composite quality — 40.8/100 · developing

Contract Quality 10.9 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 2.6 / 15

Operational Transparency 1.5 / 10

Contract Governance 1.6 / 9

Discoverability 5.9 / 8

Regulatory Posture 2.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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 0 / 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 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/cedarai/"><img src="https://apis.io/badge/cedarai/card.svg" alt="Cedarai 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
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
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

7 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 17.1 — up to +16.6 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points
Contract Quality scores 58.0 — up to +10.5 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/cedarai/apis.yml: open an issue on github.com/api-evangelist/cedarai 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
Rail Sales and Distribution (OSDM, railway union, EU railway licences)	long-tail	2.5 (thin)	1	-

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

measured — observed by APIs.io (published)

APIs 9

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

Cedarai ChargeService API

The ChargeService API from Cedarai — 3 operation(s) for chargeservice.

Cedarai Equipment History API

The Equipment History API from Cedarai — 1 operation(s) for equipment history.

Cedarai Ims API

The Ims API from Cedarai — 16 operation(s) for ims.

Cedarai InvoicesService API

The InvoicesService API from Cedarai — 3 operation(s) for invoicesservice.

Cedarai LindaService API

The LindaService API from Cedarai — 9 operation(s) for lindaservice.

Cedarai NetworkStructureService API

The NetworkStructureService API from Cedarai — 1 operation(s) for networkstructureservice.

Cedarai QuotesService API

The QuotesService API from Cedarai — 3 operation(s) for quotesservice.

Cedarai TruckLoadTenderService API

The TruckLoadTenderService API from Cedarai — 5 operation(s) for truckloadtenderservice.

Cedarai WorkOrderService API

The WorkOrderService API from Cedarai — 10 operation(s) for workorderservice.

Scroll for all 9

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

protobuf/arms/charge.proto ChargeService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService Equipment History API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService Ims API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService InvoicesService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService LindaService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService NetworkStructureService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService QuotesService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService TruckLoadTenderService API

OPEN COLLECTION

protobuf/arms/charge.proto ChargeService WorkOrderService API

OPEN COLLECTION

Scroll for all 9

Agent Skills 3

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

Track and move railcar inventory

AGENT SKILL

Export charges and reconcile shipper invoices

AGENT SKILL

Run a train work order

AGENT SKILL

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Cedarai

SLA

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Cedarai Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Cedarai API Rules

57 rules · 41 errors 9 warnings 7 info

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.

Cedarai External Openapi Overlay

1 action · update · cedarai-external-openapi.yml

DERIVED

Security Posture 2

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

Cedarai Authentication

apiKey · 2 schemes

SECURITY

Cedarai Domain Security

TLSv1.2 · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Webhooks

Lifecycle

Conformance

DataModel

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 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

AcceptableUsePolicy

AcceptableUsePolicy

Source (apis.yml)

aid: cedarai
name: Cedarai
description: Cedar AI builds ARMS (Automated Rail Management System), a cloud-native, AI-powered transportation management
  platform for railroads, industrial shippers, transload and intermodal terminals, and fleet/car owners. The ARMS External
  API exposes REST and gRPC services for railcar inventory and history, waybills and bills of lading, work orders and train
  movements, switching and class lists, charges, shipper invoices and quotes, truck load tenders, network structure, and threaded
  notes (Linda) with AI summaries — plus Ed25519-signed webhooks for real-time operational events, across US (cedarai.com)
  and EU (cedarai.se) regions. Backed by Felicis.
url: https://raw.githubusercontent.com/api-evangelist/cedarai/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- felicis
x-tier: enriched
x-tier-reason: real-openapi-and-developer-surface
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
image: https://arms.cedarai.com/cedar-icon.svg
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
x-docs-hosting: vercel
tags:
- Company
- Rail
- Transportation
- Logistics
- Freight
- Supply Chain
- Railcar Management
- Transportation Management System
- Fleet Management
- Artificial Intelligence
apis:
- aid: cedarai:cedarai-chargeservice-api
  name: Cedarai ChargeService API
  description: The ChargeService API from Cedarai — 3 operation(s) for chargeservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - ChargeService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-chargeservice-api-openapi.yml
- aid: cedarai:cedarai-equipment-history-api
  name: Cedarai Equipment History API
  description: The Equipment History API from Cedarai — 1 operation(s) for equipment history.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - Equipment History
  properties:
  - type: OpenAPI
    url: openapi/cedarai-equipment-history-api-openapi.yml
- aid: cedarai:cedarai-ims-api
  name: Cedarai Ims API
  description: The Ims API from Cedarai — 16 operation(s) for ims.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - IMS
  tags_raw:
  - Ims
  properties:
  - type: OpenAPI
    url: openapi/cedarai-ims-api-openapi.yml
- aid: cedarai:cedarai-invoicesservice-api
  name: Cedarai InvoicesService API
  description: The InvoicesService API from Cedarai — 3 operation(s) for invoicesservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - InvoicesService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-invoicesservice-api-openapi.yml
- aid: cedarai:cedarai-lindaservice-api
  name: Cedarai LindaService API
  description: The LindaService API from Cedarai — 9 operation(s) for lindaservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - LindaService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-lindaservice-api-openapi.yml
- aid: cedarai:cedarai-networkstructureservice-api
  name: Cedarai NetworkStructureService API
  description: The NetworkStructureService API from Cedarai — 1 operation(s) for networkstructureservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - NetworkStructureService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-networkstructureservice-api-openapi.yml
- aid: cedarai:cedarai-quotesservice-api
  name: Cedarai QuotesService API
  description: The QuotesService API from Cedarai — 3 operation(s) for quotesservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - QuotesService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-quotesservice-api-openapi.yml
- aid: cedarai:cedarai-truckloadtenderservice-api
  name: Cedarai TruckLoadTenderService API
  description: The TruckLoadTenderService API from Cedarai — 5 operation(s) for truckloadtenderservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - TruckLoadTenderService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-truckloadtenderservice-api-openapi.yml
- aid: cedarai:cedarai-workorderservice-api
  name: Cedarai WorkOrderService API
  description: The WorkOrderService API from Cedarai — 10 operation(s) for workorderservice.
  humanURL: https://docs.cedarai.com/user-docs/api-reference/introduction
  baseURL: https://api-lg.arms.cedarai.com
  tags:
  - WorkOrderService
  properties:
  - type: OpenAPI
    url: openapi/cedarai-workorderservice-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.cedarai.com/insights/
  type: Blog
- url: https://www.cedarai.com/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/cedarai-capability-edges.yml
  name: Cedarai Business Capability Map
- type: Overlay
  url: overlays/cedarai-external-openapi-overlay.yaml
- type: Website
  url: https://cedarai.com
- type: DeveloperPortal
  url: https://docs.cedarai.com
- type: Documentation
  url: https://docs.cedarai.com
- type: APIReference
  url: https://docs.cedarai.com/user-docs/api-reference/introduction
- type: GettingStarted
  url: https://docs.cedarai.com/user-docs/admin/getting-started
- type: Login
  url: https://arms.cedarai.com/
- type: Blog
  url: https://cedarai.com/news
- type: PrivacyPolicy
  url: https://www.cedarai.com/privacy-policy/
- type: AcceptableUsePolicy
  url: https://www.cedarai.com/aup/
- type: StatusPage
  url: https://status.cedarai.com
- type: Authentication
  url: authentication/cedarai-authentication.yml
- type: Conventions
  url: conventions/cedarai-conventions.yml
- type: ErrorCatalog
  url: errors/cedarai-problem-types.yml
- type: Webhooks
  url: asyncapi/cedarai-webhooks.yml
- type: Lifecycle
  url: lifecycle/cedarai-lifecycle.yml
- type: Conformance
  url: conformance/cedarai-conformance.yml
- type: DataModel
  url: data-model/cedarai-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/cedarai-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/cedarai-llms.txt
- type: DomainSecurity
  url: security/cedarai-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Cedarai API — frequently asked questions

Does Cedarai have an API?

Yes. APIs.io lists 9 APIs from Cedarai, including Cedarai ChargeService API, Cedarai Equipment History API and Cedarai Ims API, and 6 more.

Is there an OpenAPI specification for the Cedarai API?

Yes. APIs.io indexes 9 OpenAPI specifications for Cedarai, each linked for download from this page.

How do I authenticate with the Cedarai API?

Cedarai uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Cedarai Authentication.

Is the Cedarai API ready for AI agents?

Cedarai has a Kin Score of 40.8 out of 100 (developing) and an Agent Readiness score of 27.4 (agent-aware), 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/cedarai"

All providers

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

Every operation they expose

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

How their score was established

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