IronCore Labs
IronCore Labs builds application-layer encryption tools that keep sensitive data private while it stays usable. Its products include SaaS Shield (tenant-controlled envelope encryption with customer-managed keys / BYOK for multi-tenant SaaS), Cloaked Search (a transparent encrypting proxy for Elasticsearch and OpenSearch), Cloaked AI (encryption of vector embeddings for AI/RAG workloads while preserving similarity search), the Data Control Platform (end-to-end encryption SDKs where the end user holds the key), and an S3 Proxy for per-tenant object encryption. Developers integrate through the unified IronCore Alloy SDK (Rust, Python, Java, Kotlin), the legacy Tenant Security Client (Node.js, Go, PHP), and the self-hosted Vendor API Bridge REST API for programmatic tenant and KMS configuration management.
IronCore Labs publishes 5 API contracts indexed on the APIs.io network, including Configuration Assignment API, KMS Configuration API, Tag API, and 2 more. Tagged areas include Company, Encryption, Privacy, Security, and Application-Layer Encryption.
The IronCore Labs catalog on APIs.io includes 1 Spectral governance ruleset.
IronCore Labs’ developer surface includes documentation, API reference, getting-started guide, engineering blog, pricing, support, authentication, and 30 more developer resources.
What this lets a business do 2
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
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 |
|---|---|---|---|---|
| PKI and Encryption (certificate authorities, key management) | standard | 34.5 | - | - |
| Cloud Security Attestation and Secure-by-Design | standard | 34.5 | - | - |
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 1
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.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
IronCore Labs Configuration Assignment API
Assignments between KMS configurations and tenants
IronCore Labs KMS Configuration API
KMS configurations from different providers (AWS, Azure, GCP, Thales)
IronCore Labs Tag API
Label shared between service account configs and tenants. Controls where KMS configurations can be sent.
IronCore Labs Tenant API
Vendor tenants managed by the Config Broker
IronCore Labs Tenant Secret API
Tenant secrets created by the TSP and stored in the Config Broker
Open Collections 5
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Vendor API Bridge Configuration Assignment API
OPEN COLLECTIONVendor API Bridge Configuration Assignment Tag API
OPEN COLLECTIONVendor API Bridge Configuration Assignment Tenant API
OPEN COLLECTIONVendor API Bridge Configuration Assignment Tenant Secret API
OPEN COLLECTIONAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Rotate a tenant secret
AGENT SKILLService Levels 1
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
IronCore Labs API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll for all 7
Operate 4
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
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
IronCore Labs API — frequently asked questions
Does IronCore Labs have an API?
Yes. APIs.io lists 5 APIs from IronCore Labs, including IronCore Labs Configuration Assignment API, IronCore Labs KMS Configuration API and IronCore Labs Tag API, and 2 more.
Is there an OpenAPI specification for the IronCore Labs API?
Yes. APIs.io indexes 5 OpenAPI specifications for IronCore Labs, each linked for download from this page.
How do I authenticate with the IronCore Labs API?
IronCore Labs uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Ironcore Labs Authentication.
Is the IronCore Labs API ready for AI agents?
IronCore Labs has a Kin Score of 55.9 out of 100 (strong) and an Agent Readiness score of 26.2 (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.