Elium is a European enterprise knowledge-management SaaS platform, founded in 2007 as Knowledge Plaza and renamed Elium in 2017, headquartered in Louvain-la-Neuve, Belgium. Teams capture, validate and govern company knowledge as structured articles - which Elium calls "stories" - inside spaces, using templates, multi-step approval, expiration management, duplicate and gap detection, and in-place multilingual translation. The same governed corpus is then served to people and to AI agents through AI search, smart assistants, external portals and integrations. Programmatically Elium is a GraphQL provider, not a REST one: each customer platform serves its own per-tenant GraphQL endpoint with 17 queries, 206 mutations and 18 subscriptions, documented in a fully published SpectaQL reference, secured with OAuth 2.0 on a single apiv1 scope. In June 2026 Elium added a per-tenant remote Model Context Protocol server exposing three read-only knowledge tools to ChatGPT, Claude and custom agents. API and MCP access are Enterprise-plan only. Elium is ISO/IEC 27001:2022 certified and SecNumCloud-qualified, with EU-default and sovereign French hosting options.
Elium is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Software-as-a-Service, Knowledge Management, Knowledge Base, and Enterprise Search.
The Elium catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Elium’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 26 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/elium/"><img src="https://apis.io/badge/elium/card.svg" alt="Elium on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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 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.
Elium's single GraphQL endpoint, served per tenant at https://{platform}.elium.com/graphql. 17 queries, 206 mutations and 18 subscriptions over 1128 type definitions, covering s...
A remote Model Context Protocol server, announced 3 June 2026, served per tenant at https://{platform}.elium.com/services/mcp with OAuth 2.0 authorization and optional Dynamic C...
aid: elium
name: Elium
description: 'Elium is a European enterprise knowledge-management SaaS platform, founded in 2007 as Knowledge Plaza and renamed
Elium in 2017, headquartered in Louvain-la-Neuve, Belgium. Teams capture, validate and govern company knowledge as structured
articles - which Elium calls "stories" - inside spaces, using templates, multi-step approval, expiration management, duplicate
and gap detection, and in-place multilingual translation. The same governed corpus is then served to people and to AI agents
through AI search, smart assistants, external portals and integrations. Programmatically Elium is a GraphQL provider, not
a REST one: each customer platform serves its own per-tenant GraphQL endpoint with 17 queries, 206 mutations and 18 subscriptions,
documented in a fully published SpectaQL reference, secured with OAuth 2.0 on a single apiv1 scope. In June 2026 Elium added
a per-tenant remote Model Context Protocol server exposing three read-only knowledge tools to ChatGPT, Claude and custom
agents. API and MCP access are Enterprise-plan only. Elium is ISO/IEC 27001:2022 certified and SecNumCloud-qualified, with
EU-default and sovereign French hosting options.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: self-serve
trial: false
try_now: false
public: false
gated: none
gated_source:
- onboarding
label: Paid · Self-serve signup
confidence: high
source:
- plans
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://elium.com/logos/elium-logo.svg
url: https://raw.githubusercontent.com/api-evangelist/elium/refs/heads/main/apis.yml
x-type: company
x-source: serena-portfolio
specificationVersion: '0.23'
created: '2026-08-17'
modified: '2026-08-17'
tags:
- Company
- Software-as-a-Service
- Knowledge Management
- Knowledge Base
- Enterprise Search
- AI Search
- GraphQL
- MCP
- Collaboration
- Documentation
- RAG
- Europe
tags_raw:
- Company
- SaaS
- Knowledge Management
- Knowledge Base
- Enterprise Search
- AI Search
- GraphQL
- MCP
- Collaboration
- Documentation
- RAG
- Europe
- Knowledge-Management
apis:
- name: Elium GraphQL API
description: Elium's single GraphQL endpoint, served per tenant at https://{platform}.elium.com/graphql. 17 queries, 206
mutations and 18 subscriptions over 1128 type definitions, covering stories (content), spaces, users, templates/schemas,
tags, comments, annotations, alerts, smart assistants and tenant administration. OAuth 2.0 bearer with one scope, apiv1.
Relay cursor connections for pagination; errors are returned in-band on each mutation payload rather than as HTTP status
codes. No OpenAPI is published - GraphQL is the contract. Enterprise plan only.
humanURL: https://learn.elium.com/en/api/
baseURL: https://{platform}.elium.com/graphql
tags:
- GraphQL
- Knowledge Management
- Enterprise Search
tags_raw:
- GraphQL
- Knowledge Management
- Enterprise Search
- Knowledge-Management
properties:
- type: Documentation
url: https://learn.elium.com/en/api/
- type: APIReference
url: https://learn.elium.com/reference/
- type: GettingStarted
url: https://learn.elium.com/en/api/getting_started/quick_start
- type: GraphQL
url: graphql/elium-graphql-operations.yml
- type: Authentication
url: authentication/elium-authentication.yml
- type: OAuthScopes
url: scopes/elium-scopes.yml
- type: Conventions
url: conventions/elium-conventions.yml
- type: ErrorCatalog
url: errors/elium-error-codes.yml
- type: DataModel
url: data-model/elium-data-model.yml
- type: RateLimits
url: rate-limits/elium-rate-limits.yml
- name: Elium MCP Server
description: A remote Model Context Protocol server, announced 3 June 2026, served per tenant at https://{platform}.elium.com/services/mcp
with OAuth 2.0 authorization and optional Dynamic Client Registration. Three published tools, all read-only - FindRelevantArticles
(semantic search), FindSpecificArticles (filtered search) and ReadFullArticle - each running with the permissions of the
authenticated user. Documented setup paths for ChatGPT and Claude. Enterprise plan only.
humanURL: https://help.elium.com/en/articles/12767574-mcp
baseURL: https://{platform}.elium.com/services/mcp
tags:
- MCP
- AI Search
- RAG
properties:
- type: MCPServer
url: mcp/elium-mcp.yml
- type: ToolCrosswalk
url: mcp/elium-tool-crosswalk.yml
- type: Documentation
url: https://help.elium.com/en/articles/12767574-mcp
- type: Authentication
url: authentication/elium-authentication.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Website
url: https://elium.com/
- type: DeveloperPortal
url: https://learn.elium.com/en/api/
- type: Documentation
url: https://learn.elium.com/en/api/
- type: APIReference
url: https://learn.elium.com/reference/
- type: GettingStarted
url: https://learn.elium.com/en/api/getting_started/quick_start
- type: Support
url: https://help.elium.com/en/
- type: Blog
url: https://elium.com/blog
- type: Pricing
url: https://elium.com/pricing
- type: SignUp
url: https://elium.com/free-trial
- type: Login
url: https://elium.com/login
- type: TermsOfService
url: https://elium.com/legal/website-terms-of-use/
- type: PrivacyPolicy
url: https://elium.com/legal/privacy-policy/
- type: StatusPage
url: https://status.elium.com/
- type: ChangeLog
url: https://elium.com/changelog
- type: ChangeLog
url: changelog/elium-changelog.yml
- type: Security
url: https://elium.com/trust/controls
- type: Compliance
url: https://elium.com/trust
- type: MCPServer
url: mcp/elium-mcp.yml
- type: LLMsTxt
url: llms/elium-llms.txt
- type: AgentSkill
url: skills/_index.yml
- type: Authentication
url: authentication/elium-authentication.yml
- type: OAuthScopes
url: scopes/elium-scopes.yml
- type: Conventions
url: conventions/elium-conventions.yml
- type: ErrorCatalog
url: errors/elium-error-codes.yml
- type: Lifecycle
url: lifecycle/elium-lifecycle.yml
- type: Conformance
url: conformance/elium-conformance.yml
- type: DataModel
url: data-model/elium-data-model.yml
- type: Packages
url: packages/elium-packages.yml
- type: Plans
url: plans/elium-plans-pricing.yml
- type: RateLimits
url: rate-limits/elium-rate-limits.yml
- type: TrustCenter
url: security/elium-trust-center.yml
- type: VulnerabilityDisclosure
url: security/elium-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/elium-domain-security.yml
x-api-base:
verdict: templated-by-design
repair_tool_verdict: no-usable-base
note: 'repair-api-bases.py reports "no-usable-base" because BOTH bases template the HOST, not just a path segment. That
verdict is correct about the shape and wrong about the cause: Elium has no shared API host to record. It deploys one platform
per subdomain and its own documentation uses placeholder tenant names throughout - my-platform.elium.com in the quick
start, mycompany.elium.com in the token example, your-platform-name.elium.com in the MCP article. api.elium.com resolves
but serves an application 404 on every path, including every spec path probed, so it is not the base either. Leaving {platform}
in place is the accurate record; substituting any concrete tenant would invent a customer''s hostname. Do not "repair"
this in a later round.'
evidence:
- url: https://api.elium.com/
status: 404
- url: https://api.elium.com/openapi.json
status: 404
- url: https://demo.elium.com/graphql
status: 404
method: POST
- url: https://demo.elium.com/services/mcp
status: 404
method: POST
checked: '2026-08-17'
x-pointers-deliberately-absent:
note: Recorded so a later round does not re-litigate these, and does not add a pointer the provider has not earned. Each
was probed or searched in this pass.
OpenAPI: None exists. Probed api.elium.com/openapi.json, /openapi.yaml, /swagger.json, /v1/openapi.json, /api-docs, /docs,
/redoc plus the docs host - all 404. GraphQL is this provider's contract.
AgentCard: /.well-known/agent-card.json and legacy /.well-known/agent.json probed on elium.com, api.elium.com, learn.elium.com
and help.elium.com - 404 everywhere except learn.elium.com, which answers 200 with an HTML docs shell for every /.well-known/*
path. No card, so per the pipeline contract no a2a/ artifact was authored.
WellKnown: Elium serves no /.well-known/ document of its own. The probe is recorded in well-known/elium-well-known.yml with
every status; no pointer, because a file documenting an absence must not be scored as a presence.
SecurityTxt: Absent on elium.com and api.elium.com. The 200 text/plain security.txt on help.elium.com is INTERCOM's (Canonical
app.intercom.com, contacts bugcrowd.com/intercom) because the help centre is Intercom-hosted.
Idempotency: Elium has no idempotency mechanism. Searched all 206 mutations, 244 input types and the API guides for /idempoten/i
- zero matches. Retrying storyPost creates a second story.
SDKs: No client library in any language on npm, PyPI, RubyGems, Packagist, crates.io, pkg.go.dev, Maven or NuGet. The four
first-party @eliumhq npm packages are internal build tooling, newest release 2020-01-15.
Webhooks: No outbound webhooks are advertised. The event surface is 18 GraphQL subscriptions, recorded in asyncapi/elium-events.yml
without an AsyncAPI or Webhooks pointer.
AsyncAPI: No AsyncAPI document is published.
Deprecation: Five operations carry a Deprecated marker in the reference, but there is no deprecation policy page, no notice
period and no RFC 8594 Sunset support to point at.
GitHubOrganization: github.com/elium and github.com/Elium belong to Molecule Science (molecule-science.com), a different
company. Elium's own code is on GitLab at gitlab.com/elium/product, which returns 403 anonymously.
Postman: www.postman.com/eliumhq returns only the Postman SPA shell - no public workspace or collection.
Roadmap: elium.com/roadmap returns 404.
CLI: No first-party CLI is published.
Sandbox: No sandbox, test mode, or test-vs-live key separation is published. There is a free trial of the product but no
developer test environment.
x-enrichment:
date: '2026-08-17'
status: enriched
artifacts_added: 23
pass: local-v1
Elium API — frequently asked questions
Does Elium have an API?
Yes. APIs.io lists 2 APIs from Elium, including Elium GraphQL API and Elium MCP Server.
How do I authenticate with the Elium API?
Elium uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Elium Authentication.
How much does the Elium API cost?
Elium publishes its prices; its Team plan is € 1 5/mo per user as of 2026-10-28. APIs.io lists 3 pricing plans for Elium, with each plan's price, limits and inclusions under Pricing on this page.
Does Elium have an MCP server?
Yes. APIs.io lists 1 MCP server for Elium: Remote MCP server at {platform}.elium.com over HTTP requiring OAuth; 3 tools listed.
Is the Elium API ready for AI agents?
Elium has a Kin Score of 55.5 out of 100 (strong) and an Agent Readiness score of 25.9 (agent-aware), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: