Curiosity
Curiosity provides an AI‑powered enterprise knowledge graph platform that lets organizations connect, enrich, and query their data across systems. Built for on‑premises or private‑cloud deployment, Curiosity Studio enables users to build custom AI‑driven tools, search, embeddings, and agents while keeping data within their own infrastructure. The platform supports a REST API, SDKs for C# and Python, and extensive developer documentation covering data ingestion, security, and extensibility.
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 Curiosity the way a machine reads it — 33 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 — Curiosity scores 43.2/100 (developing), with a separate agent-readiness read of 16/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.
Why this profile is thin
No OpenAPI, AsyncAPI, GraphQL, gRPC, or WSDL contract was found on the documented API host despite accessible documentation.
The documentation is public — a person can read it, but a machine cannot. This one is Curiosity's to change: publishing an OpenAPI (or AsyncAPI for events) at a stable URL would make the same surface consumable by a crawler, a linter, and an AI agent.
What we probed
https://docs.curiosity.ai/workspace-api/→ 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. 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-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Curiosity'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/curiosity/"
title="Curiosity on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/curiosity.svg"
alt="Curiosity Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/curiosity/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/curiosity/"
title="Curiosity on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/curiosity/card.svg"
alt="Curiosity 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 Curiosity
Each block below is one kind of artifact we hold for Curiosity. 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.
Curiosity Workspace API
Workspace API provides programmatic access to Curiosity's enterprise knowledge graph, enabling data ingestion, search, embeddings, and AI agent operations.
Curiosity Admin Agent API
The Admin Agent API from Curiosity — 2 operation(s) for admin agent.
Curiosity Build API
The Build API from Curiosity — 1 operation(s) for build.
Curiosity Cce API
The Cce API from Curiosity — 1 operation(s) for cce.
Curiosity Chatai API
The Chatai API from Curiosity — 4 operation(s) for chatai.
Curiosity Code API
The Code API from Curiosity — 1 operation(s) for code.
Curiosity Config API
The Config API from Curiosity — 1 operation(s) for config.
Curiosity Curiosity API
The Curiosity API API from Curiosity — 1 operation(s) for curiosity api.
Curiosity Embeddings API
The Embeddings API from Curiosity — 1 operation(s) for embeddings.
Curiosity Endpoints API
The Endpoints API from Curiosity — 4 operation(s) for endpoints.
Curiosity Graph API
The Graph API from Curiosity — 3 operation(s) for graph.
Curiosity Groups API
The Groups API from Curiosity — 4 operation(s) for groups.
Curiosity Install API
The Install API from Curiosity — 1 operation(s) for install.
Curiosity Login API
The Login API from Curiosity — 3 operation(s) for login.
Curiosity Messages API
The Messages API from Curiosity — 2 operation(s) for messages.
Curiosity Migrations API
The Migrations API from Curiosity — 1 operation(s) for migrations.
Curiosity Models API
The Models API from Curiosity — 3 operation(s) for models.
Curiosity Node API
The Node API from Curiosity — 5 operation(s) for node.
Curiosity SAML API
The Saml API from Curiosity — 2 operation(s) for saml.
Curiosity Search API
The Search API from Curiosity — 3 operation(s) for search.
Curiosity Chat Completions API
The Chat Completions API from Curiosity — 1 operation(s) for chat completions.
Scroll within the panel for all 21 ·
Pricing 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.
Semantic 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.
Curiosity 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.
Curiosity API Rules
SPECTRALJSON Schema 6
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.
PostApiEmbeddingsEmbeddingidRequest
JSON SCHEMAPostApiLoginPasswordPasswordidRequest
JSON SCHEMAPostChatCompletionsRequest
JSON SCHEMAPostV1MessagesRequest
JSON SCHEMAPutApiSearchSettingsLlmRequest
JSON SCHEMAPutApiSearchSynonymsForRequest
JSON SCHEMASecurity Posture 3
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 Curiosity — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
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
← All providers · Data indexed from github.com/api-evangelist/curiosity · machine-readable index on apis.io
This is an independent, third-party profile of Curiosity, 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.