Integrations
One core. Every place you work.
Your JARs follow you into the AI app you already use, your team's Slack and Telegram, the repository you ship from, and the notes you keep.
Each connection is off until you switch it on, reaches only the JAR you choose, and every answer keeps its receipt.
Degen Research
Where are we on the launch?
Private answers and tl;dr shipped on Thursday. The invite flow waits on review; see Tuesday’s notes.
Receipt · 2 notes cited · nothing left
AI apps · MCP
Your JARs, inside the AI app you already use
Approve the app once, in Diogenes, and your private chats, Consilium and Knowledge open in a panel beside the conversation.
- The app reaches only the JARs you chose and spends only the credits you allowed.
- The app's model sees a Diogenes reply only when you choose Share on it. Everything else stays in Diogenes.
- One click to add in Cursor and VS Code; a connector in Claude, ChatGPT and Mistral.
Claude
On the web and on the desktop, as a connector.
ChatGPT
Connectors; Codex in the desktop app connects the same way.
Mistral
A JAR's Knowledge beside a European model.
Cursor
Your project's JAR beside the code you are writing.
VS Code
Through its MCP support; your JARs in the editor.
Slack · Telegram · Git · Notes
Where your team works
Connect a channel or a group to a JAR and Diogenes answers there, from that JAR's Knowledge, with a receipt under every answer. Connect the repository and the notes too, and it answers from what actually changed.
- Ask privately in Slack: start with “privately” and the answer comes in a DM. Write “tl;dr” in a thread and save it to the JAR with one button.
- Reminders, scheduled posts, notes saved to the JAR, and rules for how it answers in that place.
- The repository is read live with a read-only token, sealed and never shown again: commits, files, a search, open merge or pull requests.
Slack
Channels and DMs. Answers in a thread when mentioned; who may ask and how much a day is yours to set.
Telegram
Groups. Reads the photos, files and voice notes it is asked about.
Your Git project
GitLab, GitHub or Bitbucket, one repository per JAR, read only.
Obsidian and Notion
A folder, a vault or an export into a JAR's Knowledge; each note keeps where it came from.
Wallets · Chains
Crypto-native, end to end
Sign in with the wallet you already have, and ask about any address, token or transaction on the chains Diogenes reads live.
- No email and no password: you sign in by signing a message. On a phone, your wallet app approves through WalletConnect.
- Read-only, with each figure linked to its block explorer; charts of price and supply history right in the answer.
- Diogenes is invite-only for now: a new wallet needs an invite code from someone who uses it.
Your wallet is your account
MetaMask, Coinbase Wallet, Trust Wallet, Rabby, or any wallet over WalletConnect.
Live prices and on-chain data
Ethereum, Base, Arbitrum, OP Mainnet, Polygon, BNB Smart Chain, Avalanche, HyperEVM, Plasma, Robinhood Chain and more.
API · Models
Build on it
The tools you already use, the model you choose, and the same Knowledge and receipts underneath.
- An OpenAI-compatible API: the SDKs and tools you already use work with a new base URL and a Diogenes key. Only the request format is OpenAI's; nothing is sent to OpenAI.
- Open models run privately by default, some on NEAR AI's verified route. Outside models, such as Claude and GPT, are a choice you make per provider, and never answer inside a JAR.
Connect what you use
Every connection is off until you switch it on.
No name. No email. Wallet-native.