SPIFFE website screenshot

SPIFFE

Secure Production Identity Framework for Everyone (SPIFFE) is a set of open-source standards for securely identifying software systems in dynamic and heterogeneous environments through platform-agnostic, cryptographic identities. SPIFFE defines the SPIFFE ID URI format, the X.509 SVID and JWT SVID identity document formats, and the Workload API for issuing and rotating identities without secrets or passwords. SPIFFE is a graduated CNCF project.

SPIFFE publishes 2 APIs on the APIs.io network: Workload API and Bundle API. Tagged areas include Authentication, Cloud-Native, Graduated, Identity, and Security.

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

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

33.5/100 thin ▬ flat Agent 28/100 agent aware self hosted · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFreemium
1 APIs
AuthenticationCloud-NativeGraduatedIdentitySecurityZero Trust

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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 90 points between them, because the conditional facet above carries the other 10. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 90% 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/spiffe: 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 4

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

SPIFFE Workload API

The SPIFFE Workload API is a gRPC streaming interface through which workloads request and receive SPIFFE Verifiable Identity Documents (SVIDs) including X.509-SVIDs and JWT-SVID...

SPIFFE X.509 SVID

The SPIFFE X.509 SVID (SPIFFE Verifiable Identity Document) is a standard for encoding SPIFFE identities into X.509 certificates. The Subject Alternative Name field carries the ...

SPIFFE JWT SVID

The SPIFFE JWT SVID standard defines a format for encoding SPIFFE identities as JSON Web Tokens. JWT-SVIDs are used in scenarios where X.509 certificates are not practical, such...

SPIFFE Bundle API

SPIFFE trust bundle retrieval operations for fetching root CA certificates used to validate SVIDs issued by a trust domain

Open Collections 3

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

API Collection

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Spiffe Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Spiffe Rate Limits

5 limits

RATE LIMITS

FinOps 1

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

Event Specifications 1

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

SPIFFE Workload API Events

The SPIFFE Workload API is a gRPC streaming interface through which workloads request and receive SPIFFE Verifiable Identity Documents (SVIDs) and trust bundle updates. Workload...

ASYNCAPI

Semantic Vocabularies 1

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

Spiffe Context

0 classes · 7 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

SPIFFE API Rules

6 rules · 6 warnings

SPECTRAL

SPIFFE API Rules

6 rules · 5 warnings 1 info

SPECTRAL

SPIFFE API Rules

7 rules · 4 errors 3 warnings

SPECTRAL

JSON Schema 1

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

SPIFFE Identity Documents

0 properties

JSON SCHEMA

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Spiffe Svid Structure

0 properties

JSON STRUCTURE

Examples 1

Example request and response payloads for these APIs.

Security Posture 1

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

Spiffe Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

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

Spiffe Agentic Access

1 operation

1 operations · 0 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: spiffe
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: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/spiffe.png
name: SPIFFE
description: Secure Production Identity Framework for Everyone (SPIFFE) is a set of open-source standards for securely identifying
  software systems in dynamic and heterogeneous environments through platform-agnostic, cryptographic identities. SPIFFE defines
  the SPIFFE ID URI format, the X.509 SVID and JWT SVID identity document formats, and the Workload API for issuing and rotating
  identities without secrets or passwords. SPIFFE is a graduated CNCF project.
url: https://spiffe.io/
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: spiffe:spiffe-workload-api
  name: SPIFFE Workload API
  description: The SPIFFE Workload API is a gRPC streaming interface through which workloads request and receive SPIFFE Verifiable
    Identity Documents (SVIDs) including X.509-SVIDs and JWT-SVIDs, as well as trust bundle updates. It enables software to
    obtain cryptographic identities at runtime without requiring secrets to be embedded in configuration or code.
  humanURL: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md
  properties:
  - type: Documentation
    url: https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/
  - type: Reference
    url: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md
  - type: AsyncAPI
    url: asyncapi/spiffe-workload-asyncapi.yml
  - type: GitHubRepository
    url: https://github.com/spiffe/spiffe
  tags:
  - gRPC
  - Identity
  - JWT
  - Workload
  - X.509
- aid: spiffe:spiffe-x509-svid-api
  name: SPIFFE X.509 SVID
  description: The SPIFFE X.509 SVID (SPIFFE Verifiable Identity Document) is a standard for encoding SPIFFE identities into
    X.509 certificates. The Subject Alternative Name field carries the SPIFFE ID URI, enabling mutual TLS authentication between
    workloads using standard X.509 certificate validation libraries.
  humanURL: https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md
  properties:
  - type: Documentation
    url: https://spiffe.io/docs/latest/spiffe-about/svid/
  - type: Reference
    url: https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md
  - type: GitHubRepository
    url: https://github.com/spiffe/spiffe
  tags:
  - Certificate
  - Identity
  - mTLS
  - Security
  - X.509
- aid: spiffe:spiffe-jwt-svid-api
  name: SPIFFE JWT SVID
  description: The SPIFFE JWT SVID standard defines a format for encoding SPIFFE identities as JSON Web Tokens. JWT-SVIDs
    are used in scenarios where X.509 certificates are not practical, such as HTTP header-based authentication between services
    or for passing identity across trust domain boundaries.
  humanURL: https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md
  properties:
  - type: Documentation
    url: https://spiffe.io/docs/latest/spiffe-about/svid/
  - type: Reference
    url: https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md
  - type: GitHubRepository
    url: https://github.com/spiffe/spiffe
  tags:
  - Authentication
  - Identity
  - JWT
  - Security
- aid: spiffe:spiffe-bundle-api
  name: SPIFFE Bundle API
  description: SPIFFE trust bundle retrieval operations for fetching root CA certificates used to validate SVIDs issued by
    a trust domain
  humanURL: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md
  tags:
  - Bundle
  properties:
  - type: OpenAPI
    url: openapi/spiffe-bundle-api-openapi.yml
  - type: Documentation
    url: https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/
  - type: Reference
    url: https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Trust_Domain_and_Bundle.md
  - type: GitHubRepository
    url: https://github.com/spiffe/spiffe
  - type: SpectralRules
    url: rules/spiffe-rules.yml
common:
- type: IssueTracker
  url: https://github.com/spiffe/spiffe/issues
- type: CodeOfConduct
  url: https://github.com/spiffe/spiffe/blob/main/CODE-OF-CONDUCT.md
- type: ContributionGuide
  url: https://github.com/spiffe/spiffe/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/spiffe/spiffe/blob/main/LICENSE
- type: AgenticAccess
  url: agentic-access/spiffe-agentic-access.yml
- type: DomainSecurity
  url: security/spiffe-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/spiffe-secure-production-identity-framework-for-everyone
- type: JSONSchema
  url: json-schema/spiffe-svid-schema.json
- type: JSONLD
  url: json-ld/spiffe-context.jsonld
- type: SpectralRules
  url: rules/spiffe-rules.yml
- type: Vocabulary
  url: vocabulary/spiffe-vocabulary.yml
- type: Website
  url: https://spiffe.io/
- type: Documentation
  url: https://spiffe.io/docs/latest/
- type: GettingStarted
  url: https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/
- type: GitHubOrganization
  url: https://github.com/spiffe
- type: GitHubRepository
  url: https://github.com/spiffe/spiffe
- type: Community
  url: https://spiffe.io/community/
- type: Slack
  url: https://slack.spiffe.io
- type: Blog
  url: https://spiffe.io/blog/
- type: Security
  url: https://github.com/spiffe/spiffe/blob/main/SECURITY.md
- type: StackOverflow
  url: https://stackoverflow.com/questions/tagged/spiffe
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/spiffe"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/spiffe/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/spiffe/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.

A second provider on the same verified email joins the account you already have.