Gnosis Memory · Authentication Profile

Gnosis Memory Authentication

Authentication

OAuth 2.0 authorization code flow with Google, resulting in a bearer token placed in the Authorization header.

Gnosis Memory declares 1 security scheme(s) across its OpenAPI definitions.

Artificial IntelligenceMemoryEncryptionCross-PlatformDeveloper ToolsCompany
Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

Bearer http-bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-10'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://gnosismemory.com/setup
sources:
- https://gnosismemory.com/setup
description: OAuth 2.0 authorization code flow with Google, resulting in a bearer token placed in the Authorization header.
schemes:
- type: http-bearer
  name: Bearer
  evidence: Authenticate → Complete OAuth in your browser to get your token.
  location: header
  header: Authorization
  how_to_obtain: User completes Google OAuth sign‑in in the browser; the service returns a bearer token that the client stores and sends as the
    Authorization header.
docs: https://gnosismemory.com/setup

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/gnosismemory-com-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

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.