Readiness before launch
Maya Okafor, engineering manager at Acme Ltd, asked which of her team's services were below silver on the production readiness Scorecard. Memtro listed them with their level and the rules each was failing.
Who owns this service, and how is it scoring on our Scorecards?
Cortex connects Memtro to your internal developer portal. It reads catalog entities such as services, resources, domains and teams, with owner teams, owners, Slack channels, groups and repository, and one entity's links, hierarchy and Scorecard scores. It reads teams with their members, Scorecards with each entity's score, level and failing rules, deploys in a time window and an entity's custom events. When asked, and once an administrator has granted the action by name, it can add a custom event, a deploy record or a custom data value, record a dependency, or archive or unarchive an entity.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cortex tool, reads what it needs, and answers with the source cited.
These tools change something in Cortex. 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.
Once Cortex 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.
Which services are failing our production readiness Scorecard?
Who owns the checkout service?
What was deployed to production yesterday?
Which rules is the payments service failing?
Archive the old reporting service
Maya Okafor, engineering manager at Acme Ltd, asked which of her team's services were below silver on the production readiness Scorecard. Memtro listed them with their level and the rules each was failing.
Dan Fletcher, platform engineer at Northwind, asked Memtro to note the database migration on the orders service's timeline. Memtro added a custom event to the entity in Cortex. Nobody was notified, and it can be deleted in Cortex.
The teams that lean on Cortex most, a question each of them asks, and what they connect beside it.
A record in Cortex 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.
In Cortex, open your avatar → Settings → Security and access → API keys → Create new key. You need the Edit API keys permission.
Name it Memtro and choose a role that can view the catalog, Scorecards, teams and deploys, with Catalog edit rights only if Memtro should act. Copy the key, as it is shown once.
In Memtro, open Connections → Cortex and paste it into API key. Set Region or self-managed host to eu if you sign in at app.eu.cortex.io, or to your backend host name for self-managed Cortex.
Ask your first question: which services are failing our production readiness Scorecard?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cortex tools are the same everywhere.
Only when you ask, and only what it has been granted: add a custom event to an entity's timeline; record a deploy against an entity (records it, does not deploy); set a custom data value on an entity (may replace one with the same key); record that one entity depends on another; archive an entity (hidden from the catalog and Scorecards until unarchived); unarchive an entity. 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.
API key and optional region or self-managed host. In Cortex, open your avatar → Settings → Security and access → API keys → Create new key. You need the Edit API keys permission.
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