Review before publishing
Priya Sharma, API lead at BigCo, asked what was left before publishing Orders 2.1. Memtro listed the open review comments and the standardization errors with their line and severity.
Which APIs changed this month, and what is still open in review?
SwaggerHub, now Swagger Studio, answers what is in your API registry. You see an owner's APIs and versions with published and private state, one version's definition summarised, review comments, standardization errors, integrations, projects and domains. When asked and granted, Memtro can comment, reply and resolve, save a definition, clone or fork a version, publish or unpublish it, make it public or private, set the default version, rename or delete, create projects and run an integration. SwaggerHub can tell Memtro when an API version is saved, and a job can start on it. SwaggerHub On-Premise is not supported.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right SwaggerHub tool, reads what it needs, and answers with the source cited.
These tools change something in SwaggerHub. 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 SwaggerHub, choosing the same kinds; the tab shows SwaggerHub's own steps. Each event can start a job, with the event as its input. SwaggerHub sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce SwaggerHub 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 APIs changed this month?
What operations does version 2.1 of the Orders API have?
Which review comments on the Payments API are still open?
What standardization errors does the latest Users API version have?
Resolve the comment on the Orders API about pagination.
Priya Sharma, API lead at BigCo, asked what was left before publishing Orders 2.1. Memtro listed the open review comments and the standardization errors with their line and severity.
At Northwind, a job starts when SwaggerHub reports an API version was saved. Memtro reads the definition summary and standardization errors, then, as granted, comments on the version with any errors for Tom Reilly, the API designer.
The teams that lean on SwaggerHub most, a question each of them asks, and what they connect beside it.
A record in SwaggerHub 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 app.swaggerhub.com, go to Account settings and copy your API Key. It is personal and reaches every organisation you belong to.
In Memtro, open Connections → SwaggerHub, paste it into API key and set Owner to the organisation or user name, exactly as in SwaggerHub URLs.
An administrator grants the actions by name, such as Set published or Delete API, to the teams that may use them.
Ask which APIs changed this month. Events are turned on from the connection's Events tab, and the address is then added as a webhook on each API version.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The SwaggerHub tools are the same everywhere.
Only when you ask, and only what it has been granted: comment on an API version; reply to a comment; resolve or reopen a comment; create an API or save a version's definition; create a new version by cloning one; fork an API version; publish or unpublish an API version; make an API version public or private; set an API's default version; rename an API; delete an API version; delete an API with all its versions; create a project; add an API or domain to a project; run an integration (push to source control or a gateway). 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 Owner. In app.swaggerhub.com, go to Account settings and copy your API Key. It is personal and reaches every organisation you belong to.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in SwaggerHub, choosing the same kinds; the tab shows SwaggerHub'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