OpenSearch
OpenSearch is the open source, community-driven search, analytics, and observability suite (forked from Elasticsearch and Kibana) maintained under the Linux Foundation's OpenSearch Software Foundation. The platform exposes REST APIs across the search engine, the OpenSearch Dashboards UI, and a set of plugins. The Security plugin REST API lets administrators programmatically create and manage internal users, roles, role mappings, action groups, tenants, security configuration, audit log configuration, and SSL certificates.
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.
API Evangelist profiles OpenSearch the way a machine reads it — 52 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 — OpenSearch scores 41.0/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from OpenSearch'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/opensearch/"
title="OpenSearch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opensearch.svg"
alt="OpenSearch Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/opensearch/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/opensearch/"
title="OpenSearch on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/opensearch/card.svg"
alt="OpenSearch 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 OpenSearch
Each block below is one kind of artifact we hold for OpenSearch. 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 15
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.
OpenSearch Search and Indexing REST API
The core OpenSearch REST API for indexing documents, performing search queries (full text, vector, hybrid), aggregations, and managing indices, mappings, templates, aliases, and...
OpenSearch Account API
Self-service account endpoints for the calling user.
OpenSearch Action Groups API
Reusable groups of cluster and index permissions.
OpenSearch Allowlist API
Allowlist of HTTP APIs available to non-admin users.
OpenSearch Audit API
Audit log configuration.
OpenSearch Cache API
Manage the security cache.
OpenSearch Certificates API
Inspect SSL certificates loaded by the cluster.
OpenSearch Health API
Security plugin health check.
OpenSearch Internal Users API
CRUD for internal user database entries.
OpenSearch Nodes DN API
Allowlisted distinguished names for cross-cluster nodes.
OpenSearch Role Mappings API
Map users, backend roles, and hosts to security roles.
OpenSearch Roles API
CRUD for security roles and their permissions.
OpenSearch Security Config API
Inspect and update the running security configuration.
OpenSearch SSL Info API
Inspect SSL handshake information for the calling client.
OpenSearch Tenants API
Multi-tenancy support for OpenSearch Dashboards.
Scroll within the panel for all 15 ·
Open Collections 16
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONOpenSearch Security Plugin REST Account API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Action Groups API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Allowlist API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Audit API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Cache API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Certificates API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Health API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Internal Users API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Nodes DN API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Role Mappings API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Roles API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Security Config API
OPEN COLLECTIONOpenSearch Security Plugin REST API
OPEN COLLECTIONOpenSearch Security Plugin REST Account SSL Info API
OPEN COLLECTIONOpenSearch Security Plugin REST Account Tenants API
OPEN COLLECTIONScroll within the panel for all 16 ·
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.
MCP Server
MCP SERVERAgent Skills 10
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
aoss-nextgen-provisioning
AGENT SKILLaws-setup
AGENT SKILLcloud
AGENT SKILLlog-analytics
AGENT SKILLobservability
AGENT SKILLopensearch-launchpad
AGENT SKILLopensearch-skills
AGENT SKILLsearch
AGENT SKILLsolr-opensearch-migration-advisor
AGENT SKILLtrace-analytics
AGENT SKILLScroll within the panel for all 10 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
OpenSearch GraphQL Schema
This directory contains a conceptual GraphQL schema for the OpenSearch search, analytics, and observability platform — the open-source, community-driven suite forked from Elasti...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Opensearch Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Opensearch Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Opensearch Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
OpenSearch API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
OpenSearch Security Role
JSON SCHEMASecurity 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.
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.
Resources
Every other property we hold for OpenSearch — 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 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 3
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 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/opensearch · machine-readable index on apis.io
This is an independent, third-party profile of OpenSearch, 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.