SPIRE

SPIRE (SPIFFE Runtime Environment) is the reference implementation of the SPIFFE standard, providing a toolchain for establishing trust between software systems across a wide variety of hosting platforms through automated attestation and workload identity distribution. SPIRE manages a certificate authority, performs node and workload attestation, and issues SVIDs to workloads through the SPIFFE Workload API.

SPIRE publishes 5 API contracts indexed on the APIs.io network, including Workload API, Discovery API, Health API, and 2 more. Tagged areas include Authentication, Cloud-Native, Graduated, Identity, and Security.

The SPIRE catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 3 Spectral governance rulesets.

SPIRE’s developer surface includes documentation, getting-started guide, engineering blog, changelog, Stack Overflow tag, and 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.4/100 developing ▬ flat Agent 21/100 agent aware self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

2 published contracts

Authentication Cloud-Native Graduated Identity Security Zero Trust

What this lets a business do 1

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

Cybersecurity Management

BC-620

DiscoveryKeys

GET /keys

Kin Score

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

Composite quality — 42.4/100 · developing

Contract Quality 10.3 / 19

Developer Ergonomics 5.2 / 15

Access Clarity 1.2 / 15

Operational Transparency 3.6 / 10

Contract Governance 2.5 / 9

Discoverability 4.8 / 8

Regulatory Posture 1.6 / 15

Open Source Surface 10.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 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 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 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 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/spire/"><img src="https://apis.io/badge/spire/card.svg" alt="SPIRE 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
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

6 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 7.9 — up to +18.4 composite points
Developer Ergonomics scores 34.5 — up to +13.1 composite points
Contract Quality scores 55.1 — up to +11.2 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/spire/apis.yml: open an issue on github.com/api-evangelist/spire 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
Geospatial and Maps (OGC standards)	standard	40.9 (thin)	-	-
OpenSSF Best Practices Badge Holders	standard	40.9 (thin)	-	-

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 2

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)

AsyncAPI

measured — observed by APIs.io (published)

APIs 5

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

SPIRE Workload API

The SPIRE Agent exposes the SPIFFE Workload API as a Unix domain socket, allowing workloads running on the same node to request their X.509-SVIDs and JWT-SVIDs without requiring...

SPIRE Server API

The SPIRE Server exposes a gRPC API used by administrators and the SPIRE Agent to manage registration entries, node attestation, bundle federation, and server health. It allows ...

SPIRE Discovery API

OpenID Connect discovery document endpoint that describes the OIDC provider configuration and supported capabilities.

SPIRE Health API

Liveness and readiness health check endpoints for SPIRE Server and SPIRE Agent components, suitable for use as Kubernetes probes.

SPIRE Keys API

JSON Web Key Set endpoint that exposes public keys used to verify JWT-SVIDs issued by SPIRE.

Open Collections 5

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

SPIRE Health Check Discovery API

OPEN COLLECTION

SPIRE Check Discovery Health API

OPEN COLLECTION

SPIRE Health Check API

OPEN COLLECTION

SPIRE Health Check Discovery Keys API

OPEN COLLECTION

SPIRE OIDC Discovery Provider API

OPEN COLLECTION

SPIRE API pricing

Not yet checked against SPIRE's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against SPIRE's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Spire Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Spire Rate Limits

5 limits

RATE LIMITS

Service Levels 1

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

SPIRE

SLA

FinOps 1

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

Spire Finops

FINOPS

Event Specifications 1

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

SPIRE Workload API Events

The SPIRE Workload API is a gRPC streaming interface exposed by the SPIRE Agent on each node, through which workloads request and receive SPIFFE Verifiable Identity Documents (S...

ASYNCAPI

Semantic Vocabularies 1

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

Spire Context

0 classes · 9 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

SPIRE — asyncapi rules

6 rules · 6 warnings

SPECTRAL

SPIRE — jsonschema rules

6 rules · 5 warnings 1 info

SPECTRAL

SPIRE API Rules

9 rules · 3 errors 5 warnings 1 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

SPIRE Registration Entries

0 properties

JSON SCHEMA

SPIRE SVID

5 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Spire Registration Structure

0 properties

JSON STRUCTURE

Spire Svid Structure

0 properties

JSON STRUCTURE

Examples 4

Example request and response payloads for these APIs.

Spire Get Jwks Example

2 fields

EXAMPLE

Spire Get Liveness Example

2 fields

EXAMPLE

Spire Get Openid Configuration Example

2 fields

EXAMPLE

Spire Get Readiness Example

2 fields

EXAMPLE

Security Posture 1

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

Spire Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Spire Agentic Access

4 operations

4 operations · 0 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 4

Reference material describing how the API behaves

ContributionGuide

Documentation

JSONSchema

JSONSchema

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

JSONStructure

JSONStructure

JSONLD

SpectralRules

Vocabulary

Build 4

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Operate 7

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

Community

Slack

ChangeLog

StackOverflow

Scroll for all 7

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: spire
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/spire.png
name: SPIRE
description: SPIRE (SPIFFE Runtime Environment) is the reference implementation of the SPIFFE standard, providing a toolchain
  for establishing trust between software systems across a wide variety of hosting platforms through automated attestation
  and workload identity distribution. SPIRE manages a certificate authority, performs node and workload attestation, and issues
  SVIDs to workloads through the SPIFFE Workload API.
url: https://spiffe.io/docs/latest/spire-about/
tags:
- Authentication
- Cloud-Native
- Graduated
- Identity
- Security
- Zero Trust
tags_raw:
- Authentication
- Cloud Native
- Graduated
- Identity
- Security
- Zero Trust
created: '2025'
modified: '2026-05-19'
specificationVersion: '0.23'
type: Index
apis:
- aid: spire:spire-workload-api
  name: SPIRE Workload API
  description: The SPIRE Agent exposes the SPIFFE Workload API as a Unix domain socket, allowing workloads running on the
    same node to request their X.509-SVIDs and JWT-SVIDs without requiring any credentials. The Workload API also delivers
    trust bundle updates so that workloads can verify the identity of other workloads.
  humanURL: https://spiffe.io/docs/latest/spire-about/spire-concepts/
  properties:
  - type: Documentation
    url: https://spiffe.io/docs/latest/spire-about/spire-concepts/
  - type: Reference
    url: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md
  - type: AsyncAPI
    url: asyncapi/spire-workload-asyncapi.yml
  - type: GitHubRepository
    url: https://github.com/spiffe/spire
  tags:
  - gRPC
  - Identity
  - JWT
  - Workload
  - X.509
- aid: spire:spire-server-api
  name: SPIRE Server API
  description: The SPIRE Server exposes a gRPC API used by administrators and the SPIRE Agent to manage registration entries,
    node attestation, bundle federation, and server health. It allows creating and managing workload registration entries
    that define the SPIFFE IDs issued to workloads matching specified selectors, and supports federation with external SPIFFE
    trust domains.
  humanURL: https://spiffe.io/docs/latest/deploying/spire_server/
  properties:
  - type: Documentation
    url: https://spiffe.io/docs/latest/deploying/spire_server/
  - type: Reference
    url: https://github.com/spiffe/spire-api-sdk
  - type: JSONSchema
    url: json-schema/spire-registration-schema.json
  - type: GitHubRepository
    url: https://github.com/spiffe/spire-api-sdk
  tags:
  - Administration
  - Attestation
  - gRPC
  - Registration
  - Servers
  tags_raw:
  - Administration
  - Attestation
  - gRPC
  - Registration
  - Server
- aid: spire:spire-discovery-api
  name: SPIRE Discovery API
  description: OpenID Connect discovery document endpoint that describes the OIDC provider configuration and supported capabilities.
  humanURL: https://spiffe.io/docs/latest/spire-about/spire-concepts/
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/spire-discovery-api-openapi.yml
  - type: Documentation
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: Reference
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire
  - type: JSONStructure
    url: json-structure/spire-registration-structure.json
  - type: Documentation
    url: https://spiffe.io/docs/latest/keyless/oidc-federation-aws/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire/tree/main/support/oidc-discovery-provider
  - type: JSONStructure
    url: json-structure/spire-svid-structure.json
- aid: spire:spire-health-api
  name: SPIRE Health API
  description: Liveness and readiness health check endpoints for SPIRE Server and SPIRE Agent components, suitable for use
    as Kubernetes probes.
  humanURL: https://spiffe.io/docs/latest/spire-about/spire-concepts/
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/spire-health-api-openapi.yml
  - type: Documentation
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: Reference
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire
  - type: JSONStructure
    url: json-structure/spire-registration-structure.json
  - type: Documentation
    url: https://spiffe.io/docs/latest/keyless/oidc-federation-aws/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire/tree/main/support/oidc-discovery-provider
  - type: JSONStructure
    url: json-structure/spire-svid-structure.json
- aid: spire:spire-keys-api
  name: SPIRE Keys API
  description: JSON Web Key Set endpoint that exposes public keys used to verify JWT-SVIDs issued by SPIRE.
  humanURL: https://spiffe.io/docs/latest/spire-about/spire-concepts/
  tags:
  - Keys
  properties:
  - type: OpenAPI
    url: openapi/spire-keys-api-openapi.yml
  - type: Documentation
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: Reference
    url: https://spiffe.io/docs/latest/deploying/spire_agent/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire
  - type: JSONStructure
    url: json-structure/spire-registration-structure.json
  - type: Documentation
    url: https://spiffe.io/docs/latest/keyless/oidc-federation-aws/
  - type: GitHubRepository
    url: https://github.com/spiffe/spire/tree/main/support/oidc-discovery-provider
  - type: JSONStructure
    url: json-structure/spire-svid-structure.json
common:
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/spire/overview
- type: Plans
  url: plans/spire-plans-pricing.yml
- type: RateLimits
  url: rate-limits/spire-rate-limits.yml
- type: FinOps
  url: finops/spire-finops.yml
- type: CapabilityMap
  url: capabilities/spire-capability-edges.yml
  name: SPIRE Business Capability Map
- type: IssueTracker
  url: https://github.com/spiffe/spire/issues
- type: Releases
  url: https://github.com/spiffe/spire/releases
- type: CodeOfConduct
  url: https://github.com/spiffe/spire/blob/main/CODE-OF-CONDUCT.md
- type: ContributionGuide
  url: https://github.com/spiffe/spire/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/spiffe/spire/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/spire-agentic-access.yml
- type: DomainSecurity
  url: security/spire-domain-security.yml
- type: Website
  url: https://spiffe.io/
- type: Documentation
  url: https://spiffe.io/docs/latest/
- type: GettingStarted
  url: https://spiffe.io/docs/latest/try/getting-started-k8s/
- type: GitHubOrganization
  url: https://github.com/spiffe
- type: GitHubRepository
  url: https://github.com/spiffe/spire
- type: Community
  url: https://spiffe.io/community/
- type: Slack
  url: https://slack.spiffe.io
- type: Blog
  url: https://spiffe.io/blog/
- type: ChangeLog
  url: https://github.com/spiffe/spire/blob/main/CHANGELOG.md
- type: Security
  url: https://github.com/spiffe/spire/blob/main/SECURITY.md
- type: StackOverflow
  url: https://stackoverflow.com/questions/tagged/spiffe
- type: JSONSchema
  url: json-schema/spire-svid-schema.json
- type: JSONSchema
  url: json-schema/spire-registration-schema.json
- type: JSONStructure
  url: json-structure/spire-svid-structure.json
- type: JSONStructure
  url: json-structure/spire-registration-structure.json
- type: JSONLD
  url: json-ld/spire-context.jsonld
- type: SpectralRules
  url: rules/spire-rules.yml
- type: Vocabulary
  url: vocabulary/spire-vocabulary.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

SPIRE API — frequently asked questions

Does SPIRE have an API?

Yes. APIs.io lists 5 APIs from SPIRE, including SPIRE Workload API, SPIRE Server API and SPIRE Discovery API, and 2 more.

Is there an OpenAPI specification for the SPIRE API?

Yes. APIs.io indexes 3 OpenAPI specifications for SPIRE, each linked for download from this page.

How much does the SPIRE API cost?

APIs.io lists 3 pricing plans for SPIRE, with each plan's price, limits and inclusions under Pricing on this page.

Is the SPIRE API ready for AI agents?

SPIRE has a Kin Score of 42.4 out of 100 (developing) and an Agent Readiness score of 21.0 (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/spire"

All providers

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

Every operation they expose

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

How their score was established

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