Silverfort
Silverfort is an identity security platform that protects human and non-human identities across hybrid environments — on-premises, cloud, and legacy — without agents, proxies, or changes to existing infrastructure. Its Runtime Access Protection (RAP) technology integrates inline with existing IAM infrastructure (Active Directory, Entra ID, Okta, Ping, AWS) and evaluates every authentication attempt in real time before access is granted, extending MFA, identity threat detection and response (ITDR), identity security posture management (ISPM), privileged access security, service-account and non-human-identity governance, and AI agent security to resources that traditional identity tooling cannot reach. Founded in 2016 and headquartered in Dallas, Texas, Silverfort exposes a REST API (the "Raven" service at raven.silverfort.io, with EU and Singapore regional hosts) covering user and resource risk, service-account inventory and insights, policies and enrollment — but the REST API reference is published only inside a customer-authenticated knowledge base, so no public machine-readable contract is available.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Silverfort the way a machine reads it — 3 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Silverfort scores 28.3/100 (thin), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
The Silverfort REST API Reference at docs.silverfort.com 302s to a Document360 OIDC login at identity.document360.io, and that docs host then answers HTTP 200 with the identical ~10.7KB login shell for every path — /openapi.json, /swagger.json and /llms.txt included — while the live API host raven.silverfort.io serves "Silverfort Raven is UP :-)" and a real 404 for every spec location.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Silverfort's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://docs.silverfort.com/product-documentation/docs/en/silverfort-rest-api-reference50-1→ HTTP 302https://raven.silverfort.io/openapi.json→ HTTP 404https://raven.silverfort.io/→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Silverfort's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/silverfort/"
title="Silverfort on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/silverfort.svg"
alt="Silverfort Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/silverfort/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/silverfort/"
title="Silverfort on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/silverfort/card.svg"
alt="Silverfort Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Silverfort
Each block below is one kind of artifact we hold for Silverfort. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Silverfort REST API
The Silverfort REST API (internally the "Raven" service) exposes user and resource risk read and write, service-account inventory and insights, policy control, and enrollment. A...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Silverfort — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/silverfort · machine-readable index on apis.io
This is an independent, third-party profile of Silverfort, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.