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 4 API contracts indexed on the APIs.io network, including Workload API, Bundle API, and 2 more. 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 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.9/100 thin ▬ flat Agent 26/100 agent aware Front door AI 1/6 silent Heartbeat 93/100 alive self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemium

1 published contract

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

Bundle

Kin Score

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

Composite quality — 32.9/100 · thin

Contract Quality 10.1 / 19

Developer Ergonomics 5.0 / 15

Access Clarity 1.2 / 15

Operational Transparency 1.0 / 10

Contract Governance 2.5 / 9

Discoverability 4.8 / 8

Regulatory Posture 1.6 / 15

Open Source Surface 4.0 / 10

Agent readiness — 26/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 8 / 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/spiffe/"><img src="https://apis.io/badge/spiffe/card.svg" alt="SPIFFE 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)
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
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

5 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 33.3 — up to +13.3 composite points
Operational Transparency scores 10.5 — up to +11.6 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/spiffe/apis.yml: open an issue on github.com/api-evangelist/spiffe 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
Artifact Hub Cloud-Native Packages	standard	34.5 (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 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 2

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

SPIFFE Federation Endpoint Bundle API

OPEN COLLECTION

SPIFFE Federation Bundle Endpoint API

OPEN COLLECTION

SPIFFE API pricing

Not yet checked against SPIFFE'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 SPIFFE's documentation. All 5 limits →

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

Service Levels 1

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

SPIFFE

SLA

FinOps 1

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

Spiffe Finops

FINOPS

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 — asyncapi rules

6 rules · 6 warnings

SPECTRAL

SPIFFE — jsonschema 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.

Spiffe Get Trust Bundle Example

2 fields

EXAMPLE

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

GettingStarted

GettingStarted

Documentation 3

Reference material describing how the API behaves

ContributionGuide

ContributionGuide

JSONSchema

JSONSchema

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

JSONLD

JSONLD

SpectralRules

SpectralRules

Vocabulary

Vocabulary

Build 3

SDKs, sample code, and the tooling you integrate with

CodeOfConduct

CodeOfConduct

GitHubOrganization

GitHubOrganization

GitHubRepository

GitHubRepository

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Operate 5

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Community

Slack

StackOverflow

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

License

License

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

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: low
  source:
  - plans
  - security
  generated: '2026-11-06'
  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: Plans
  url: plans/spiffe-plans-pricing.yml
- type: RateLimits
  url: rate-limits/spiffe-rate-limits.yml
- type: FinOps
  url: finops/spiffe-finops.yml
- type: CapabilityMap
  url: capabilities/spiffe-capability-edges.yml
  name: SPIFFE Business Capability Map
- 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

SPIFFE API — frequently asked questions

Does SPIFFE have an API?

Yes. APIs.io lists 4 APIs from SPIFFE, including SPIFFE Workload API, SPIFFE X.509 SVID and SPIFFE JWT SVID, and 1 more.

Is there an OpenAPI specification for the SPIFFE API?

Yes. APIs.io indexes 1 OpenAPI specification for SPIFFE, each linked for download from this page.

How much does the SPIFFE API cost?

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

Is the SPIFFE API ready for AI agents?

SPIFFE has a Kin Score of 32.9 out of 100 (thin) and an Agent Readiness score of 25.7 (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/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"

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.