Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Indykite website screenshot

Indykite

IndyKite is the runtime control layer for agentic AI. Its enterprise platform applies trust, context, and runtime control across organizational data so autonomous AI agents can act securely, continuously injecting live signals — identity, provenance, freshness, sensitivity, and compliance status — into AI actions and access decisions at the moment they occur. The platform is built on an Identity Knowledge Graph (IKG) and delivers Knowledge-Based Access Control (KBAC), AuthZEN-based authorization, ContX IQ contextual queries, entity matching, and a hosted regional Model Context Protocol (MCP) server. IndyKite exposes a REST API (Capture, DataSchema, ContX IQ, AuthZEN, Entity Matching) and a Config API for managing organizations, projects, applications, app agents, service accounts, authorization policies, knowledge queries, event sinks, and MCP servers, plus a Go SDK and a Terraform provider. Added to the API Evangelist network via the speedinvest portfolio and enriched from the provider's public OpenAPI and documentation.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Indykite the way a machine reads it — 31 machine-readable artifacts across 21 APIs, 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 — Indykite scores 57.8/100 (developing), with a separate agent-readiness read of 71/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 57.8/100 · developing
Contract Quality 16.6 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 5.1 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 71/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 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 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Indykite

Each block below is one kind of artifact we hold for Indykite. 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 21

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.

Indykite Application Agent Credentials API

Application Agent Credential management

Indykite Application Agents API

Application Agent CRUD operations

Indykite Applications API

Application and agent management

Indykite Authorization Policies API

KBAC and ContX IQ Policies CRUD operations

Indykite AuthZEN API

Authorization API implemented according to [AuthZEN specification](https://openid.net/wg/authzen/specifications/).

Indykite Capture API

Capture REST API represents the service interface for data capture.

Indykite ContX IQ API

ContX IQ API supports CRUD operations on IKG which cooperates with authorization engine.

Indykite DataSchema API

DataSchema enables customers to define their own data models within the Identity Knowledge Graph (IKG)

Indykite Deprecated API

The Deprecated API from Indykite — 2 operation(s) for deprecated.

Indykite Entity Matching API

Entity Matching Pipeline configuration

Indykite EntityMatching API

The EntityMatching API from Indykite — 3 operation(s) for entitymatching.

Indykite Event Sinks API

Event Sink configuration

Indykite External Data Resolver API

External Data Resolver configuration

Indykite Knowledge Queries API

Knowledge Query management

Indykite MCP Servers API

MCP Servers configuration

Indykite Organizations API

Organization operations

Indykite Projects API

Project CRUD operations

Indykite Service Account Credentials API

Service Account Credential management

Indykite Service Accounts API

Service Account CRUD operations

Indykite Token Introspect API

Token introspection configuration

Indykite Trust Score API

Trust Score Profile management

Scroll within the panel for all 21 ·

Arazzo Workflows 3

Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

Capture graph data then make an authorization decision

Upsert nodes and a relationship into the Identity Knowledge Graph, then ask AuthZEN/KBAC whether a subject may act on a resource.

ARAZZO

Provision an IndyKite project and AppAgent credential

Create a project, an application and an application agent, then mint an AppAgent credential for data-plane calls.

ARAZZO

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

indykite-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

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

Security Posture 4

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.

Indykite Authentication

apiKey/http · 2 schemes

SECURITY

Indykite Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Indykite Vulnerability Disclosure

contact published

SECURITY

Indykite Trust Center

SOC 2 Type I, SOC 2 Type II, ISO 27001, HIPAA, GDPR, EU-U.S. Data Privacy Framework

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

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

Indykite Agentic Access

88 operations · 56 acting

88 operations · 56 acting

AGENTIC

Resources

Every other property we hold for Indykite — 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.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/indykite · machine-readable index on apis.io