Finite State

Finite State is a product security platform for connected-device and embedded software manufacturers. It performs binary and firmware composition analysis, source-code scanning and third-party scan ingestion, SBOM generation and lifecycle management (CycloneDX and SPDX), VEX, EPSS- and reachability-based vulnerability prioritization, license-policy enforcement, and evidence-backed compliance reporting for regimes such as the EU Cyber Resilience Act, FDA 524B, ISO 21434 and IEC 62443. Programmatic access is offered through a token-authenticated REST API on the platform host, a legacy GraphQL API with an official Python SDK, the fs-cli command-line tool, and CI/CD integrations for GitHub Actions, Jenkins and Azure DevOps. Finite State also publishes an anonymous, read-only A2A JSON-RPC content API described by an agent card at its canonical well-known path.

Finite State is listed with 3 APIs on the APIs.io network. Tagged areas include Product Security, Software Supply Chain Security, SBOM, Firmware Analysis, and Vulnerability Management.

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

🌐 Visit website 📡 Profile data on GitHub

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

3 APIs 3 Agent Skills

Product SecuritySoftware Supply Chain Security SBOMFirmware AnalysisVulnerability Management Binary Analysis Connected Devices Compliance Cybersecurity IoT A2A

Kin Score

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

Composite quality — 37.9/100 · thin

Contract Quality 0.0 / 19

Developer Ergonomics 8.7 / 15

Access Clarity 6.7 / 15

Operational Transparency 3.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.9 / 8

Regulatory Posture 3.7 / 15

Open Source Surface 5.0 / 10

Agent readiness — 12/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 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 8 / 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.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against 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 75 points between them, because both conditional facets apply and carry 25 points together. 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/finite-state/"><img src="https://apis.io/badge/finite-state/card.svg" alt="Finite State 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)
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 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
Access Clarity scores 44.7 — up to +11.1 composite points
Contract Governance scores 18.2 — up to +9.8 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/finite-state/apis.yml: open an issue on github.com/api-evangelist/finite-state 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
Cloud Security Attestation and Secure-by-Design	mixed	44.1	-	1
Jenkins Plugins + CD Foundation Landscape	mixed	44.1	-	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.

Agent2Agent

measured — observed by APIs.io (conformant)

APIs 3

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

Finite State Platform API

Token-authenticated REST API for the Finite State platform, served under /api/public/v0 on the platform host. Interactive Swagger documentation is published per organization at ...

Finite State A2A Content API

Public, anonymous, read-only JSON-RPC 2.0 API exposing Finite State's published content: blog posts, resources, videos, events, podcasts and press articles. Four allowlisted met...

Finite State GraphQL API

GraphQL API historically documented at https://platform.finitestate.io/api/v1/graphql and still the transport used by the official Python SDK, which authenticates via a client-c...

Agent Skills 3

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

Browse and retrieve Finite State content

AGENT SKILL

Discover the Finite State agent surface

AGENT SKILL

Search Finite State content

AGENT SKILL

Security Posture 2

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

Finite State Authentication

apiKey/http/oauth2 · 4 schemes

SECURITY

Finite State 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

ContributionGuide

ContributionGuide

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

WellKnown

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Conformance

Lifecycle

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 6

Status, limits, changes, and where to get help

IssueTracker

Releases

Support

StatusPage

ChangeLog

Deprecation

Commercial 4

Pricing, plans, and the legal terms of use

License

Pricing

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

Blog

Website

Blog

BlogRSS

Other 1

Properties that don't map to a standard resource type

AgentCard

AgentCard

Source (apis.yml)

aid: finite-state
name: Finite State
description: Finite State is a product security platform for connected-device and embedded software manufacturers. It performs
  binary and firmware composition analysis, source-code scanning and third-party scan ingestion, SBOM generation and lifecycle
  management (CycloneDX and SPDX), VEX, EPSS- and reachability-based vulnerability prioritization, license-policy enforcement,
  and evidence-backed compliance reporting for regimes such as the EU Cyber Resilience Act, FDA 524B, ISO 21434 and IEC 62443.
  Programmatic access is offered through a token-authenticated REST API on the platform host, a legacy GraphQL API with an
  official Python SDK, the fs-cli command-line tool, and CI/CD integrations for GitHub Actions, Jenkins and Azure DevOps.
  Finite State also publishes an anonymous, read-only A2A JSON-RPC content API described by an agent card at its canonical
  well-known path.
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: false
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - 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
image: https://finitestate.io/images/backgrounds/hero-space.jpg
url: https://raw.githubusercontent.com/api-evangelist/finite-state/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-10-06'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
tags:
- Product Security
- Software Supply Chain Security
- SBOM
- Firmware Analysis
- Vulnerability Management
- Binary Analysis
- Connected Devices
- Compliance
- Cybersecurity
- IoT
- A2A
apis:
- aid: finite-state:platform-api
  name: Finite State Platform API
  description: Token-authenticated REST API for the Finite State platform, served under /api/public/v0 on the platform host.
    Interactive Swagger documentation is published per organization at https://[org].finitestate.io/swagger and the underlying
    OpenAPI document is served at /api/docs/openapi.json. Both the spec and every operation sit behind an API token, so no
    machine-readable contract is retrievable anonymously.
  humanURL: https://docs.finitestate.io/docs/dev-tools/finite-state-api/
  baseURL: https://app.finitestate.io/api/public/v0
  tags:
  - Product Security
  - SBOM
  - Vulnerability Management
  properties:
  - type: Documentation
    url: https://docs.finitestate.io/docs/dev-tools/finite-state-api/
  - type: APIReference
    url: https://docs.finitestate.io/docs/dev-tools/finite-state-api/
  - type: Authentication
    url: authentication/finite-state-authentication.yml
- aid: finite-state:a2a-content-api
  name: Finite State A2A Content API
  description: 'Public, anonymous, read-only JSON-RPC 2.0 API exposing Finite State''s published content: blog posts, resources,
    videos, events, podcasts and press articles. Four allowlisted methods (content.list, content.get, content.search, content.metadata)
    are described by an A2A agent card served from the canonical well-known path. POST only; GET returns 405.'
  humanURL: https://finitestate.io/.well-known/agent-card.json
  baseURL: https://finitestate.io/api/a2a
  tags:
  - Content
  - Agents
  - A2A
  properties:
  - type: AgentCard
    url: a2a/finite-state-a2a.yml
- aid: finite-state:graphql-api
  name: Finite State GraphQL API
  description: GraphQL API historically documented at https://platform.finitestate.io/api/v1/graphql and still the transport
    used by the official Python SDK, which authenticates via a client-credentials exchange at /api/v1/auth/token and passes
    an organization context on every request. An anonymous POST to the documented endpoint returned 404 on 2026-08-04, so
    the surface is recorded as legacy alongside the newer REST API.
  humanURL: https://github.com/FiniteStateInc/finite-state-sdk-python
  baseURL: https://platform.finitestate.io/api/v1/graphql
  tags:
  - GraphQL
  - SBOM
  - Vulnerability Management
  properties:
  - type: SourceCode
    url: https://github.com/FiniteStateInc/finite-state-sdk-python
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://finitestate.io/feed
  type: Blog
- type: X-MCPServerCandidate
  url: mcp/finite-state-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: IssueTracker
  url: https://github.com/FiniteStateInc/finite-state-sdk-python/issues
- type: Releases
  url: https://github.com/FiniteStateInc/finite-state-sdk-python/releases
- type: ContributionGuide
  url: https://github.com/FiniteStateInc/finite-state-sdk-python/blob/main/CONTRIBUTING.md
- type: License
  name: MIT
  url: https://github.com/FiniteStateInc/finite-state-sdk-python/blob/main/LICENSE
- type: Website
  url: https://finitestate.io
- type: DeveloperPortal
  url: https://docs.finitestate.io/
- type: Documentation
  url: https://docs.finitestate.io/docs/
- type: APIReference
  url: https://docs.finitestate.io/docs/dev-tools/finite-state-api/
- type: GettingStarted
  url: https://docs.finitestate.io/docs/get-started
- type: Support
  url: https://finitestate.io/support
- type: Blog
  url: https://finitestate.io/blog
- type: BlogRSS
  url: https://finitestate.io/rss.xml
- type: GitHubOrganization
  url: https://github.com/FiniteStateInc
- type: Pricing
  url: https://finitestate.io/pricing
- type: SignUp
  url: https://finitestate.io/request-demo
- type: TermsOfService
  url: https://finitestate.io/terms-of-use
- type: PrivacyPolicy
  url: https://finitestate.io/privacy-policy
- type: StatusPage
  url: https://status.finitestate.io
- type: ChangeLog
  url: https://docs.finitestate.io/changelog
- type: AgentCard
  url: a2a/finite-state-a2a.yml
- type: LLMsTxt
  url: llms/finite-state-llms.txt
- type: WellKnown
  url: well-known/finite-state-well-known.yml
- type: Packages
  url: packages/finite-state-packages.yml
- type: SDKs
  url: packages/finite-state-packages.yml
- type: CLI
  url: cli/finite-state-cli.yml
- type: Authentication
  url: authentication/finite-state-authentication.yml
- type: Conventions
  url: conventions/finite-state-conventions.yml
- type: ErrorCatalog
  url: errors/finite-state-problem-types.yml
- type: Conformance
  url: conformance/finite-state-conformance.yml
- type: Lifecycle
  url: lifecycle/finite-state-lifecycle.yml
- type: Deprecation
  url: lifecycle/finite-state-lifecycle.yml
- type: DomainSecurity
  url: security/finite-state-domain-security.yml
- type: DataModel
  url: data-model/finite-state-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 19
  pass: local-v1
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://finitestate.io/.well-known/agent-card.json
  grade: near-conformant
  protocol_version: '0.3'
  control: 200

Finite State API — frequently asked questions

Does Finite State have an API?

Yes. APIs.io lists 3 APIs from Finite State, including Finite State Platform API, Finite State A2A Content API and Finite State GraphQL API.

How do I authenticate with the Finite State API?

Finite State uses bearer-token authentication (apiKey/http/oauth2 · 4 schemes). The details are profiled on APIs.io as Finite State Authentication.

Is the Finite State API ready for AI agents?

Finite State has a Kin Score of 37.9 out of 100 (thin) and an Agent Readiness score of 12.1 (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/finite-state"

All providers

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

Every operation they expose

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

How their score was established

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