Which critical security issues are open in our payments repository, and how do we fix them?
Aikido Security shows you the open issue groups in your feed by severity and type. Memtro also reads individual findings with package, CVE, repository, SLA date and status, plus notes, repositories, containers, domains and PR checks. When asked and granted, it can add a note, snooze, ignore, un-ignore or solve an issue, or adjust its severity. It can also start a repository, container or domain scan and label repositories. Aikido can tell Memtro when a new issue is found or a PR check fails, and a job can start. Only a workspace admin can create the client credentials.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Aikido Security tool, reads what it needs, and answers with the source cited.
These tools change something in Aikido Security. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Aikido Security, choosing the same kinds; the tab shows Aikido Security's own steps. Each event can start a job, with the event as its input. Aikido Security signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Aikido Security is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Aikido Security + MemtroWhich critical issues are open in the payments repo?
How do we fix the top issue group in the checkout service?
Which code repositories have not been scanned recently?
Did the last PR check on the api-gateway repository pass its gate?
Snooze the lodash issue group until the end of the month.
Priya Sharma, engineering manager at Acme Ltd, asked which critical issues were open in the payments repository before a release. Memtro listed the open issue groups for that repository with their related CVEs, time to fix and how to fix each one.
At Northwind, a job starts when Aikido reports that a PR check failed. It reads the PR check and the new issues it found, then lists each finding with its package, CVE and how to fix it. Dan Fletcher, lead developer, reads the summary before reviewing the pull request.
The teams that lean on Aikido Security most, a question each of them asks, and what they connect beside it.
A record in Aikido Security is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Aikido, open Settings → Integrations → API → Aikido REST and create client credentials with App Type Private. Only a workspace admin can do this. Choose the read scopes, plus the write scopes for the actions you want.
In Memtro, open Connections → Aikido Security and paste the Client ID and Client secret. Set Region if you sign in to Aikido at its US, AU or ME address.
An administrator grants actions such as snooze an issue or scan a repository by name to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added in Aikido's webhook settings.
Ask which critical issues are open in the payments repo.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Aikido Security tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to an issue group; snooze an issue or issue group until a date; unsnooze an issue or issue group; ignore an issue or issue group; un-ignore an issue or issue group; mark an issue as solved; adjust the severity of an issue or issue group; start a scan of a code repository; start a scan of a container; start a scan of a domain; add a label to a code repository; remove a label from a code repository. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Client ID and client secret. In Aikido, open Settings → Integrations → API → Aikido REST and create client credentials with App Type Private. Only a workspace admin can do this. Choose the read scopes, plus the write scopes for the actions you want.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Aikido Security, choosing the same kinds; the tab shows Aikido Security's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
