Did the nightly API monitor pass?
Postman shows the workspaces your key's user can see, the collections in each, and environments by name. It reads your monitors, which collection and environment each runs, its schedule, and its last run's status, errors, latency and assertions. When asked, and once an administrator has granted the action by name, it can comment on collections, run a monitor now, which sends real requests to the APIs it targets, create, change or delete monitors, create workspaces, post workspace updates, copy collections, and permanently delete a collection. Collection contents and environment variable values are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Postman tool, reads what it needs, and answers with the source cited.
These tools change something in Postman. 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 Postman 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.
Did the nightly API monitor pass?
Which Postman monitors are inactive?
When does the checkout monitor run next?
Add a comment to the Orders API collection saying the v2 endpoints are live.
Run the checkout monitor now
Priya Sharma, QA lead at Northwind, asked whether the nightly API monitor had passed. Memtro read the monitor's last run, which finished with two errors and three failed assertions. It also gave the next scheduled run, so Priya knew when to look again.
Dan Fletcher, backend engineer at Acme Ltd, deployed a fix and asked Memtro to run the checkout monitor rather than wait for the night. Memtro started the run in Postman, which sent the collection's requests to the checkout API, then read the result and reported every assertion passing.
The teams that lean on Postman most, a question each of them asks, and what they connect beside it.
A record in Postman 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
Aikido Security
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
ZenhubSign in to Postman as a dedicated user who has access only to the workspaces Memtro should use. Open Settings → Account settings → API keys.
Choose Generate API Key, name it Memtro and copy it. It cannot be scoped and can do everything its user can.
In Memtro, open Connections → Postman and paste API key. Set Region to eu only for Enterprise teams on api.eu.postman.com.
Ask: did the nightly API monitor pass?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Postman tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a collection; edit a comment on a collection; run a monitor now (uses monitor run quota); create a scheduled monitor for a collection (uses monitor run quota on every run); pause, resume, rename or reschedule a monitor; delete a monitor (permanent); create a personal, private or team workspace; post an update to a workspace's watchers; duplicate a collection into another workspace; delete a collection (permanent). 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, with an optional region. Sign in to Postman as a dedicated user who has access only to the workspaces Memtro should use. Open Settings → Account settings → API keys.
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
