Civil Infrastructure Platform

The Civil Infrastructure Platform (CIP) is a Linux Foundation collaborative project that builds an industrial-grade open source base layer for civil infrastructure systems such as transportation, power generation and distribution, building and city management, industrial control, and healthcare equipment. CIP curates a Super Long-Term Support (SLTS) kernel and core user-space packages that can be maintained for more than ten years, plus working groups for security (IEC 62443 alignment), software update, real-time, and testing. CIP's primary programmable interface is source code — the kernel, CIP Core images and tooling published through GitLab and Debian-derived package archives — and it publishes machine-readable product lifecycle data for those. CIP also serves one live REST API: its own event calendar at cip-project.org/wp-json, declared in an RFC 9727 /.well-known/api-catalog and described by OpenAPI documents the site serves itself.

Civil Infrastructure Platform publishes 6 APIs on the APIs.io network. Tagged areas include Embedded, Industrial, Infrastructure, Linux, and Linux Foundation.

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

Civil Infrastructure Platform’s developer surface includes authentication, GitHub presence, engineering blog, documentation, support, pricing, signup flow, and 36 more developer resources.

🌐 Visit website 📡 Source on GitHub

39.9/100 developing ▬ flat Agent 10/100 agent aware Front door AI 1/6 silent Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessFreemium

3 APIs

Embedded Industrial Infrastructure Linux Linux FoundationLong-Term SupportOpen Source

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 39.9/100 · developing

Contract Quality 2.0 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 7.1 / 15

Operational Transparency 2.8 / 10

Contract Governance 5.3 / 9

Discoverability 5.4 / 8

Regulatory Posture 5.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 10/100 · agent aware

Machine-Readable Contract 0 / 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 0 / 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 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

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/.

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 github.com/api-evangelist/civil-infrastructure-platform: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

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

CIP SLTS Kernel

The CIP Kernel is a Super Long-Term Support (SLTS) Linux kernel branch maintained for ten or more years, providing a stable base for industrial systems that must remain in servi...

CIP Core Packages

CIP Core provides a curated set of Debian-derived user-space packages aligned with the SLTS kernel to deliver a complete reference platform for civil infrastructure devices.

CIP Software Update

The CIP Software Update working group maintains tooling such as SWUpdate and hawkBit-based servers used to deliver secure over-the-air updates across long-lived industrial deplo...

CIP Security

The CIP Security working group aligns the CIP base layer with IEC 62443-4-1 and 62443-4-2 industrial cybersecurity requirements and tracks CVE handling across the SLTS kernel an...

CIP Testing

The CIP Testing working group runs continuous-integration and hardware-in-the-loop testing on member-supplied boards to validate kernel and core packages against the SLTS branch.

Civil Infrastructure Platform Website (WordPress REST)

The public WordPress REST API (wp-json) of the Civil Infrastructure Platform website at cip-project.org: the route index of the site's content management system, catalogued as o...

Pricing Plans 1

Published pricing tiers and plan structures.

Civil Infrastructure Platform Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Civil Infrastructure Platform Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Civil Infrastructure Platform Finops

FINOPS

Semantic Vocabularies 1

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

Civil Infrastructure Platform Context

13 classes · 0 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Civil Infrastructure Platform API Rules

5 rules · 2 errors 3 warnings

SPECTRAL

Security Posture 3

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

Civil Infrastructure Platform Authentication

http · 1 scheme

SECURITY

Civil Infrastructure Platform Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Civil Infrastructure Platform Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

OpenAPI

OpenAPI

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

JSONLD

Spectral

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

GitLab

GitLab

GitHub

GitHub

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Compliance

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

ChangeLog

ChangeLog

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 5

The organization behind the API

LinkedIn

Website

Blog

BlogRSS

Twitter

Other 6

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Wiki

Mailing List

APICatalog

Source (apis.yml)

aid: civil-infrastructure-platform
name: Civil Infrastructure Platform
url: https://raw.githubusercontent.com/api-evangelist/civil-infrastructure-platform/refs/heads/main/apis.yml
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
created: '2026-03-16'
modified: '2026-09-16'
type: Index
access: 3rd-Party
position: Consuming
specificationVersion: '0.23'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/civil-infrastructure-platform.png
x-docs-platform: sphinx
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-21
tags:
- Embedded
- Industrial
- Infrastructure
- Linux
- Linux Foundation
- Long-Term Support
- Open Source
tags_raw:
- Embedded
- Industrial
- Infrastructure
- Linux
- Linux Foundation
- Long-Term Support
- Open Source
- Open-Source
description: 'The Civil Infrastructure Platform (CIP) is a Linux Foundation collaborative project that builds an industrial-grade
  open source base layer for civil infrastructure systems such as transportation, power generation and distribution, building
  and city management, industrial control, and healthcare equipment. CIP curates a Super Long-Term Support (SLTS) kernel and
  core user-space packages that can be maintained for more than ten years, plus working groups for security (IEC 62443 alignment),
  software update, real-time, and testing. CIP''s primary programmable interface is source code — the kernel, CIP Core images
  and tooling published through GitLab and Debian-derived package archives — and it publishes machine-readable product lifecycle
  data for those. CIP also serves one live REST API: its own event calendar at cip-project.org/wp-json, declared in an RFC
  9727 /.well-known/api-catalog and described by OpenAPI documents the site serves itself.'
apis:
- aid: civil-infrastructure-platform:cip-kernel
  name: CIP SLTS Kernel
  tags:
  - Embedded
  - Kernel
  - Linux
  - SLTS
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
  properties:
  - url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance
    type: Documentation
  - url: https://gitlab.com/cip-project/cip-kernel
    type: Source Code
  description: The CIP Kernel is a Super Long-Term Support (SLTS) Linux kernel branch maintained for ten or more years, providing
    a stable base for industrial systems that must remain in service across multi-decade lifecycles.
- aid: civil-infrastructure-platform:cip-core
  name: CIP Core Packages
  tags:
  - Debian
  - Packages
  - Userspace
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipcore
  properties:
  - url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipcore
    type: Documentation
  - url: https://gitlab.com/cip-project/cip-core
    type: Source Code
  description: CIP Core provides a curated set of Debian-derived user-space packages aligned with the SLTS kernel to deliver
    a complete reference platform for civil infrastructure devices.
- aid: civil-infrastructure-platform:cip-software-update
  name: CIP Software Update
  tags:
  - OTA
  - Software Update
  - SWUpdate
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wiki.linuxfoundation.org/civilinfrastructureplatform/softwareupdate
  properties:
  - url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/softwareupdate
    type: Documentation
  description: The CIP Software Update working group maintains tooling such as SWUpdate and hawkBit-based servers used to
    deliver secure over-the-air updates across long-lived industrial deployments.
- aid: civil-infrastructure-platform:cip-security
  name: CIP Security
  tags:
  - IEC 62443
  - Industrial Security
  - Security
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsecurity
  properties:
  - url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsecurity
    type: Documentation
  description: The CIP Security working group aligns the CIP base layer with IEC 62443-4-1 and 62443-4-2 industrial cybersecurity
    requirements and tracks CVE handling across the SLTS kernel and user-space.
- aid: civil-infrastructure-platform:cip-testing
  name: CIP Testing
  tags:
  - CI
  - LAVA
  - Testing
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting
  properties:
  - url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting
    type: Documentation
  description: The CIP Testing working group runs continuous-integration and hardware-in-the-loop testing on member-supplied
    boards to validate kernel and core packages against the SLTS branch.
- aid: civil-infrastructure-platform:cip-project-org-website-wordpress-rest
  name: Civil Infrastructure Platform Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Civil Infrastructure Platform website at cip-project.org: the
    route index of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://cip-project.org/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://cip-project.org/wp-json
  x-platform: wordpress
  x-platform-surface: rest
common:
- type: Overlay
  url: overlays/civil-infrastructure-platform-tec-v1-overlay.yaml
- type: Overlay
  url: overlays/civil-infrastructure-platform-events-overlay.yaml
- type: Overlay
  url: overlays/civil-infrastructure-platform-zapier-overlay.yaml
- type: Authentication
  url: authentication/civil-infrastructure-platform-authentication.yml
- type: DomainSecurity
  url: security/civil-infrastructure-platform-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/civil-infrastructure-platform
- type: Website
  url: https://www.cip-project.org/
- type: Wiki
  url: https://wiki.linuxfoundation.org/civilinfrastructureplatform
- type: GitLab
  url: https://gitlab.com/cip-project
- type: GitHub
  url: https://github.com/cip-project
- type: Mailing List
  url: https://lists.cip-project.org/g/cip-dev
- type: JSONLD
  url: json-ld/civil-infrastructure-platform-context.jsonld
- type: Spectral
  url: rules/civil-infrastructure-platform-rules.yml
- url: https://cip-project.org/blog/
  type: Blog
- type: OpenAPI
  url: openapi/_original/civil-infrastructure-platform-tec-v1-openapi-original.json
  name: CIP Events REST API (tec/v1)
- type: WellKnown
  url: well-known/civil-infrastructure-platform-well-known.yml
- type: APICatalog
  url: https://www.cip-project.org/.well-known/api-catalog
- type: LLMsTxt
  url: llms/civil-infrastructure-platform-llms.txt
- type: Conventions
  url: conventions/civil-infrastructure-platform-conventions.yml
- type: ErrorCatalog
  url: errors/civil-infrastructure-platform-problem-types.yml
- type: DataModel
  url: data-model/civil-infrastructure-platform-data-model.yml
- type: Lifecycle
  url: lifecycle/civil-infrastructure-platform-lifecycle.yml
- type: Conformance
  url: conformance/civil-infrastructure-platform-conformance.yml
- type: Compliance
  url: https://www.bestpractices.dev/projects/10564
  name: OpenSSF Best Practices — Gold badge
- type: VulnerabilityDisclosure
  url: security/civil-infrastructure-platform-vulnerability-disclosure.yml
- type: Security
  url: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipkernelmaintenance#security_fixes
  name: CIP security fix and vulnerability reporting process
- type: Packages
  url: packages/civil-infrastructure-platform-packages.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Plans
  url: plans/civil-infrastructure-platform-plans-pricing.yml
- type: RateLimits
  url: rate-limits/civil-infrastructure-platform-rate-limits.yml
- type: FinOps
  url: finops/civil-infrastructure-platform-finops.yml
- type: Documentation
  url: https://cip-documents.readthedocs.io/
- type: Support
  url: https://lists.cip-project.org/g/cip-dev
- type: Pricing
  url: https://cip-project.org/about/join
- type: SignUp
  url: https://enrollment.lfx.linuxfoundation.org/?project=cip
- type: TermsOfService
  url: https://www.linuxfoundation.org/terms
- type: PrivacyPolicy
  url: https://www.linuxfoundation.org/privacy
- type: BlogRSS
  url: https://cip-project.org/feed
- type: Twitter
  url: https://twitter.com/cip_project
- type: ChangeLog
  url: changelog/civil-infrastructure-platform-changelog.yml
- type: X-MCPServerCandidate
  url: mcp/civil-infrastructure-platform-mcp.yml
- type: APIReference
  url: https://cip-project.org/wp-json/tec/v1/docs
  name: Live self-served OpenAPI 3.0.4 reference for the CIP Events REST API
- type: GitHubOrganization
  url: https://github.com/cip-project
  name: CIP GitHub organization (0 public repos — the code lives on GitLab)
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-09-05'
  status: enriched
  artifacts_added: 22
  pass: local-v3

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/civil-infrastructure-platform"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/civil-infrastructure-platform/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/civil-infrastructure-platform/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.