⬡

LinkCrypt + Obsidian (+ AI)

Use Obsidian for notes, your AI for reasoning, and LinkCrypt as the dedicated URL layer — all connected through the same REST API your agents already use.

How the trio fits together

  • Obsidian — long-form notes, backlinks, daily notes, and local Markdown.
  • LinkCrypt — canonical store for URLs: titles, tags, full-text search, imports from Pocket/Instapaper, Chrome extension.
  • AI assistant (Claude, ChatGPT, etc.) — calls GET /search / POST /links so research sessions update the library without copy-paste.

Pattern A — AI agent owns the HTTP calls

Configure your agent (see Claude / ChatGPT guides) with your LinkCrypt API key from Preferences. Ask it to "pull my saved links tagged project-x and summarize into today's note" — it queries the API and returns Markdown you paste into Obsidian, or writes via an Obsidian plugin if you use one.

Pattern B — Obsidian community plugins

There is no official LinkCrypt Obsidian plugin yet. You can still bridge the gap with plugins that run HTTP requests:

  • Templater — user scripts can fetch() (Node/Electron) to pull JSON from GET /links?tags=... and render a list into a template.
  • QuickAdd + custom scripts — capture a URL in Obsidian and POST to LinkCrypt with your API key (store the key in an environment variable or OS keychain, not in the vault).

Never commit API keys into a public vault or Git repo. Prefer machine-local env vars or your agent holding the secret.

Example: daily note excerpt (conceptual)

A script could call: 

GET https://getlinkcrypt.com/api/v1/links?tags=reading&limit=5
Authorization: Bearer YOUR_API_KEY

…then format results as Markdown bullets with titles and URLs for your daily note.

API keys REST reference Claude setup