Gnosem

Gnosem provides a cross‑vendor AI memory server that implements the Model Context Protocol (MCP). It offers a persistent per‑user memory store accessible from any MCP‑capable client such as Claude Desktop, ChatGPT, Gemini, Kimi, Cursor, Windsurf, and Zed. Free tier includes 200 memories and one API key; paid plans add unlimited memories, 1 GB storage, and priority indexing. The service emphasizes data privacy, encrypting storage at rest and isolating user data.

Gnosem publishes 10 API contracts indexed on the APIs.io network, including Auth API, Demo API, Export API, and 7 more. Tagged areas include Artificial Intelligence, Memory, MCP, Cross-vendor, and Cloud.

The Gnosem catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Gnosem’s developer surface includes engineering blog, authentication, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.4/100 thin Agent 51/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

1 published contract

Artificial Intelligence Memory MCPCross-vendorCloud

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 28.4/100 · thin

Contract Quality 13.4 / 21

Developer Ergonomics 3.5 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 2.2 / 10

Discoverability 5.6 / 9

Regulatory Posture 1.5 / 15

Agent readiness — 51/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/gnosem-dev/"><img src="https://apis.io/badge/gnosem-dev/card.svg" alt="Gnosem 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
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) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →

3 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points Ask about this →
Developer Ergonomics scores 20.7 — up to +15.9 composite points Ask about this →
Operational Transparency scores 0.0 — up to +13.0 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/gnosem-dev/apis.yml: open an issue on github.com/api-evangelist/gnosem-dev to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

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.

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

Gnosem Auth API

The Auth API from Gnosem — 3 operation(s) for auth.

Gnosem Demo API

The Demo API from Gnosem — 2 operation(s) for demo.

Gnosem Export API

The Export API from Gnosem — 1 operation(s) for export.

Gnosem Health API

The Health API from Gnosem — 1 operation(s) for health.

Gnosem Keys API

The Keys API from Gnosem — 1 operation(s) for keys.

Gnosem MCP API

The Mcp API from Gnosem — 1 operation(s) for mcp.

Gnosem Me API

The Me API from Gnosem — 1 operation(s) for me.

Gnosem Signup API

The Signup API from Gnosem — 1 operation(s) for signup.

Gnosem Stripe API

The Stripe API from Gnosem — 1 operation(s) for stripe.

Gnosem Upgrade API

The Upgrade API from Gnosem — 1 operation(s) for upgrade.

Scroll for all 10

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Gnosem Dev Context

12 classes · 35 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Gnosem API Rules

51 rules · 49 error-severity 1 warn-severity 1 info-severity

SPECTRAL

JSON Schema 9

Standalone JSON Schema definitions for this provider's data models.

DemoSearchRequest

2 properties

JSON SCHEMA

DemoSearchResponse

1 properties

JSON SCHEMA

Export

6 properties

JSON SCHEMA

Health

3 properties

JSON SCHEMA

JsonRpcRequest

4 properties

JSON SCHEMA

JsonRpcResponse

4 properties

JSON SCHEMA

Me

7 properties

JSON SCHEMA

RotateResponse

2 properties

JSON SCHEMA

SignupResponse

3 properties

JSON SCHEMA

Scroll for all 9

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Gnosem Authentication

http · 1 scheme

SECURITY

Gnosem Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

Gnosem Agentic Access

13 operations · 7 acting · 1 human-in-the-loop

13 operations · 7 acting

AGENTIC

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgentSkill

LLMsTxt

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: gnosem-dev
name: Gnosem
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://gnosem.dev/og.svg
description: Gnosem provides a cross‑vendor AI memory server that implements the Model Context Protocol (MCP). It offers a
  persistent per‑user memory store accessible from any MCP‑capable client such as Claude Desktop, ChatGPT, Gemini, Kimi, Cursor,
  Windsurf, and Zed. Free tier includes 200 memories and one API key; paid plans add unlimited memories, 1 GB storage, and
  priority indexing. The service emphasizes data privacy, encrypting storage at rest and isolating user data.
url: https://artifacts.apis.io/gnosem-dev/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-10 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Artificial Intelligence
- Memory
- MCP
- Cross-vendor
- Cloud
tags_raw:
- AI
- Memory
- MCP
- Cross-vendor
- Cloud
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/gnosem-dev-agentic-access.yml
- type: Spectral
  url: rules/gnosem-dev-rules.yml
- type: JSONLD
  url: json-ld/gnosem-dev-context.jsonld
- type: Vocabulary
  url: vocabulary/gnosem-dev-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/gnosem-dev-data-model.yml
- type: ErrorCatalog
  url: errors/gnosem-dev-problem-types.yml
- type: Conformance
  url: conformance/gnosem-dev-conformance.yml
- type: LLMsTxt
  url: llms/gnosem-dev-llms.txt
- type: WellKnown
  url: well-known/gnosem-dev-well-known.yml
- type: Hosts
  url: hosts/gnosem-dev-hosts.yml
- type: Vendors
  url: vendors/gnosem-dev-vendors.yml
- type: Blog
  url: https://gnosem.dev/blog/
- type: Authentication
  url: authentication/gnosem-dev-authentication.yml
- type: DomainSecurity
  url: security/gnosem-dev-domain-security.yml
- type: Website
  url: https://gnosem.dev/
apis:
- aid: gnosem-dev:gnosem-dev-auth-api
  name: Gnosem Auth API
  description: The Auth API from Gnosem — 3 operation(s) for auth.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Authentication
  tags_raw:
  - Auth
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-auth-api-openapi.yml
- aid: gnosem-dev:gnosem-dev-demo-api
  name: Gnosem Demo API
  description: The Demo API from Gnosem — 2 operation(s) for demo.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Demo
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-demo-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-demo-search-request-schema.json
  - type: JSONSchema
    url: json-schema/gnosem-dev-demo-search-response-schema.json
- aid: gnosem-dev:gnosem-dev-export-api
  name: Gnosem Export API
  description: The Export API from Gnosem — 1 operation(s) for export.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Export
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-export-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-export-schema.json
- aid: gnosem-dev:gnosem-dev-health-api
  name: Gnosem Health API
  description: The Health API from Gnosem — 1 operation(s) for health.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-health-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-health-schema.json
- aid: gnosem-dev:gnosem-dev-keys-api
  name: Gnosem Keys API
  description: The Keys API from Gnosem — 1 operation(s) for keys.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Keys
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-keys-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-rotate-response-schema.json
- aid: gnosem-dev:gnosem-dev-mcp-api
  name: Gnosem MCP API
  description: The Mcp API from Gnosem — 1 operation(s) for mcp.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - MCP
  tags_raw:
  - Mcp
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-mcp-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-json-rpc-request-schema.json
  - type: JSONSchema
    url: json-schema/gnosem-dev-json-rpc-response-schema.json
- aid: gnosem-dev:gnosem-dev-me-api
  name: Gnosem Me API
  description: The Me API from Gnosem — 1 operation(s) for me.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Me
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-me-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-me-schema.json
- aid: gnosem-dev:gnosem-dev-signup-api
  name: Gnosem Signup API
  description: The Signup API from Gnosem — 1 operation(s) for signup.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Sign Up
  tags_raw:
  - Signup
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-signup-api-openapi.yml
  - type: JSONSchema
    url: json-schema/gnosem-dev-signup-response-schema.json
- aid: gnosem-dev:gnosem-dev-stripe-api
  name: Gnosem Stripe API
  description: The Stripe API from Gnosem — 1 operation(s) for stripe.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Stripe
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-stripe-api-openapi.yml
- aid: gnosem-dev:gnosem-dev-upgrade-api
  name: Gnosem Upgrade API
  description: The Upgrade API from Gnosem — 1 operation(s) for upgrade.
  humanURL: https://gnosem.dev/
  baseURL: https://gnosem.dev
  tags:
  - Upgrade
  properties:
  - type: OpenAPI
    url: openapi/gnosem-dev-upgrade-api-openapi.yml
x-enrichment:
  date: '2026-11-10'
  status: enriched
  artifacts_added: 23
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Gnosem API — frequently asked questions

Does Gnosem have an API?

Yes. APIs.io lists 10 APIs from Gnosem, including Gnosem Auth API, Gnosem Demo API and Gnosem Export API, and 7 more.

Is there an OpenAPI specification for the Gnosem API?

Yes. APIs.io indexes 10 OpenAPI specifications for Gnosem, each linked for download from this page.

How do I authenticate with the Gnosem API?

Gnosem documents its authentication (http · 1 scheme). The details are profiled on APIs.io as Gnosem Authentication.

Is the Gnosem API ready for AI agents?

Gnosem has a Kin Score of 28.4 out of 100 (thin) and an Agent Readiness score of 51.1 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/gnosem-dev"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/gnosem-dev/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/gnosem-dev/evidence"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.