ELISA

ELISA (Enabling Linux in Safety Applications) is a Linux Foundation collaborative project that builds the shared tools, processes and evidence needed to use Linux in safety-critical systems. Its working groups and special interest groups span automotive, aerospace, medical devices, railways, space-grade Linux and open-source engineering process, producing white papers, case studies, kernel analysis tooling and a public technical directory. ELISA develops two tools of its own: BASIL, a software quality management and traceability application with an HTTP REST API and SPDX 3.0.1 export, and ks-nav, kernel-source navigation tooling. ELISA itself publishes a machine-readable API surface at https://elisa.tech/wp-json/ — declared through an RFC 9727 api-catalog and described by a live OpenAPI 3.0.0 document — plus an llms.txt and permissive Content Signals for AI use.

ELISA publishes 2 API contracts indexed on the APIs.io network. Tagged areas include Embedded, Linux, Linux Foundation, Safety, and Functional Safety.

ELISA’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, pricing, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.3/100 thin ▬ flat Agent 10/100 agent aware Front door AI 2/6 trace Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFree⚡ Free to try

1 published contract 2 Agent Skills

Embedded Linux Linux Foundation SafetyFunctional SafetyOpen Source Automotive Aerospace Medical Devices Traceability Standards Event

Kin Score

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

Composite quality — 35.3/100 · thin

Contract Quality 0.0 / 19

Developer Ergonomics 8.1 / 15

Access Clarity 11.4 / 15

Operational Transparency 2.1 / 10

Contract Governance 0.4 / 9

Discoverability 4.2 / 8

Regulatory Posture 2.9 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health 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/elisa/"><img src="https://apis.io/badge/elisa/card.svg" alt="ELISA 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
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
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 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
Contract Governance scores 4.5 — up to +11.5 composite points
Operational Transparency scores 21.1 — up to +10.3 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/elisa/apis.yml: open an issue on github.com/api-evangelist/elisa 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
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	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.

APIs 2

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

BASIL REST API

BASIL — "The FuSa Spice" — is ELISA's own software quality management tool. It decomposes a software component specification into snippets, maps work items (software requirement...

ELISA Website (WordPress REST)

The public WordPress REST API (wp-json) of the ELISA website at elisa.tech: the route index of the site's content management system, catalogued as one site surface rather than a...

Agent Skills 2

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

elisa-resolve-venues-organizers

AGENT SKILL

elisa-track-project-events

AGENT SKILL

ELISA API pricing

Prices published by ELISA. A free plan or tier is listed.

Plan	Price
Associate Member free	Free
General Member paid	$20000 per 5,000 and above employees (already an LF member) · $15000 per 2,000 – 4,999 employees (already an LF member)
Premier Member paid	$90000

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Elisa Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Elisa Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Elisa Finops

FINOPS

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.

Elisa Events Calendar Overlay

14 actions · documentation · elisa-events-calendar-openapi.json

DERIVED

Security Posture 2

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

Elisa Authentication

2 schemes

SECURITY

Elisa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

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

DataModel

Lifecycle

Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 5

Status, limits, changes, and where to get help

RateLimits

Support

HelpCenter

Community

ChangeLog

Commercial 6

Pricing, plans, and the legal terms of use

License

Pricing

TermsOfService

PrivacyPolicy

Plans

FinOps

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 4

Properties that don't map to a standard resource type

WhitePapers

CaseStudies

Overlay

APICatalog

Source (apis.yml)

aid: elisa
name: ELISA
description: 'ELISA (Enabling Linux in Safety Applications) is a Linux Foundation collaborative project that builds the shared
  tools, processes and evidence needed to use Linux in safety-critical systems. Its working groups and special interest groups
  span automotive, aerospace, medical devices, railways, space-grade Linux and open-source engineering process, producing
  white papers, case studies, kernel analysis tooling and a public technical directory. ELISA develops two tools of its own:
  BASIL, a software quality management and traceability application with an HTTP REST API and SPDX 3.0.1 export, and ks-nav,
  kernel-source navigation tooling. ELISA itself publishes a machine-readable API surface at https://elisa.tech/wp-json/ —
  declared through an RFC 9727 api-catalog and described by a live OpenAPI 3.0.0 document — plus an llms.txt and permissive
  Content Signals for AI use.'
type: Index
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: true
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - pricing
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: none
  trial: false
  try_now: true
  public: true
  label: Free and anonymous
  confidence: high
  source:
  - probe
  generated: '2026-08-27'
  method: probed
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/elisa.png
x-docs-platform: mkdocs
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
x-docs-hosting: github-pages
tags:
- Embedded
- Linux
- Linux Foundation
- Safety
- Functional Safety
- Open Source
- Automotive
- Aerospace
- Medical Devices
- Traceability
- Standards
- Event
tags_raw:
- Embedded
- Linux
- Linux Foundation
- Safety
- Functional Safety
- Open Source
- Automotive
- Aerospace
- Medical Devices
- Traceability
- Standards
- Events
- Open-Source
created: '2026-03-16'
modified: '2026-09-16'
url: https://raw.githubusercontent.com/api-evangelist/elisa/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: elisa:elisa-basil-api
  name: BASIL REST API
  description: BASIL — "The FuSa Spice" — is ELISA's own software quality management tool. It decomposes a software component
    specification into snippets, maps work items (software requirements, test specifications, test cases, test runs, justifications,
    documents) onto them, tracks completeness and exports a traceability matrix as SPDX Model 3, HTML or PDF. It ships a Flask
    HTTP REST API specifically so it can be driven from automated toolchains, and it is self-hosted — operators build the
    API and app containers from the provided Containerfiles. No OpenAPI or other machine-readable contract is published for
    it.
  humanURL: https://basil-the-fusa-spice.readthedocs.io/
  baseURL: null
  tags:
  - Traceability
  - Functional Safety
  - Quality Management
  - SPDX
  properties:
  - type: Documentation
    name: BASIL documentation
    url: https://basil-the-fusa-spice.readthedocs.io/
  - type: SourceCode
    url: https://github.com/elisa-tech/BASIL
  - type: ChangeLog
    name: BASIL releases
    url: https://github.com/elisa-tech/BASIL/releases
  - type: Demo
    name: ELISA public BASIL instance
    url: http://elisa-builder-00.iol.unh.edu:9056/
- aid: elisa:elisa-tech-website-wordpress-rest
  name: ELISA Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the ELISA website at elisa.tech: the route index of the site''s
    content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://elisa.tech/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://elisa.tech/wp-json
  x-platform: wordpress
  x-platform-surface: rest
common:
- type: RateLimits
  url: rate-limits/elisa-rate-limits.yml
- type: Website
  url: https://elisa.tech/
- type: License
  name: GPL-2.0
  url: https://github.com/elisa-tech/BASIL/blob/main/LICENSE
- type: DeveloperPortal
  name: ELISA Technical Directory
  description: ELISA's technical directory and knowledge base — the entry point to project results.
  url: https://directory.elisa.tech/
- type: Documentation
  name: ELISA Technical Directory
  description: ELISA's published technical output and knowledge base.
  url: https://directory.elisa.tech/
- type: APIReference
  name: ELISA Events API — live OpenAPI
  description: The OpenAPI 3.0.0 document ELISA serves for its events API namespace.
  url: https://elisa.tech/wp-json/tribe/events/v1/doc
- type: GettingStarted
  name: ELISA FAQs
  description: Frequently asked questions about the ELISA Project and how to get involved.
  url: https://elisa.tech/about/faqs/
- type: Support
  name: ELISA Technical Forum
  description: The devel mailing list, ELISA's primary technical support channel.
  url: https://lists.elisa.tech/g/devel
- type: HelpCenter
  name: Contact ELISA
  url: https://elisa.tech/about/contact/
- type: Blog
  name: ELISA Blog
  url: https://elisa.tech/blog/
- type: BlogRSS
  name: ELISA RSS feed
  url: https://elisa.tech/feed/
- type: GitHubOrganization
  name: ELISA GitHub
  description: Source code and repositories for ELISA, including BASIL and ks-nav.
  url: https://github.com/elisa-tech
- type: SignUp
  name: Become an ELISA Member
  url: https://elisa.tech/membership/join/
- type: Pricing
  name: ELISA Membership Pricing Guide
  description: Published annual membership dues by tier and employee band.
  url: https://elisa.tech/membership/join/
- type: TermsOfService
  name: Linux Foundation Terms of Use
  url: https://www.linuxfoundation.org/terms
- type: PrivacyPolicy
  name: Linux Foundation Privacy Policy
  url: https://www.linuxfoundation.org/privacy
- type: WhitePapers
  name: ELISA White Papers
  url: https://elisa.tech/white-papers/
- type: CaseStudies
  name: ELISA Case Studies
  url: https://elisa.tech/case-studies/
- type: Community
  name: ELISA Discord
  url: http://chat.elisa.tech/
- type: OpenAPI
  name: ELISA Events API (harvested)
  url: openapi/_original/elisa-events-calendar-openapi.json
- type: Overlay
  url: overlays/elisa-events-calendar-overlay.yaml
- type: WellKnown
  name: ELISA .well-known probe
  description: RFC 9727 api-catalog and llms.txt both served; index of every path probed.
  url: well-known/elisa-well-known.yml
- type: APICatalog
  name: RFC 9727 API Catalog
  description: ELISA's linkset declaring https://elisa.tech/wp-json/ as its API description.
  url: well-known/elisa-api-catalog.json
- type: LLMsTxt
  name: ELISA llms.txt
  url: llms/elisa-llms.txt
- type: Authentication
  url: authentication/elisa-authentication.yml
- type: Conventions
  url: conventions/elisa-conventions.yml
- type: ErrorCatalog
  url: errors/elisa-problem-types.yml
- type: DataModel
  url: data-model/elisa-data-model.yml
- type: Lifecycle
  url: lifecycle/elisa-lifecycle.yml
- type: Conformance
  url: conformance/elisa-conformance.yml
- type: ChangeLog
  name: BASIL release history
  url: changelog/elisa-changelog.yml
- type: Packages
  url: packages/elisa-packages.yml
- type: AgentSkill
  name: ELISA Agent Skills
  url: skills/_index.yml
- type: DomainSecurity
  url: security/elisa-domain-security.yml
- type: Plans
  url: plans/elisa-plans-pricing.yml
- type: FinOps
  url: finops/elisa-finops.yml
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com
x-enrichment:
  date: '2026-08-27'
  status: enriched
  artifacts_added: 15
  pass: local-v1

ELISA API — frequently asked questions

Does ELISA have an API?

Yes. APIs.io lists 2 APIs from ELISA, including BASIL REST API and ELISA Website (WordPress REST).

How do I authenticate with the ELISA API?

ELISA uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Elisa Authentication.

How much does the ELISA API cost?

ELISA publishes its prices; its General Member plan is $20000 per 5,000 and above employees (already an LF member) · $15000 per 2,000 – 4,999 employees (already an LF member) as of 2026-08-27. APIs.io lists 3 pricing plans for ELISA, with each plan's price, limits and inclusions under Pricing on this page.

Is the ELISA API ready for AI agents?

ELISA has a Kin Score of 35.3 out of 100 (thin) and an Agent Readiness score of 9.5 (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/elisa"

All providers

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

Every operation they expose

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

How their score was established

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