Failures after a release
Maya Okafor, ML engineer at Acme Ltd, asked which predictions had failed since the morning release. Memtro listed them with model, version, status and error, and showed every failure came from one new version.
Which predictions failed today, and what is each deployment running on?
Replicate connects Memtro to your hosted AI models. It reads the account's predictions and trainings with status, timings, compute seconds and errors, never their inputs, outputs or logs. It reads deployments with hardware and instance counts, the hardware on offer, and public models. When asked, and once an administrator has granted the action by name, it can run a model or a deployment, which Replicate bills, cancel a run, start a fine-tune, create, resize or delete a deployment, create, describe or delete a model, and delete a model version. Replicate tokens have every right of their account.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Replicate tool, reads what it needs, and answers with the source cited.
These tools change something in Replicate. 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 Replicate, choosing the same kinds; the tab shows Replicate's own steps. Each event can start a job, with the event as its input. Replicate signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Replicate 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 predictions failed today?
How many compute seconds did yesterday's runs use?
What hardware is the image deployment running on?
What inputs does this model take?
Scale the image deployment down to zero minimum instances
Maya Okafor, ML engineer at Acme Ltd, asked which predictions had failed since the morning release. Memtro listed them with model, version, status and error, and showed every failure came from one new version.
Tom Reilly, platform lead at BigCo, asked Memtro to set the image deployment's minimum instances to zero. Memtro changed it in Replicate, taking effect as a new release at once, so the hardware is no longer billed while idle.
The teams that lean on Replicate most, a question each of them asks, and what they connect beside it.
A record in Replicate 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 Replicate, open Account → API tokens and choose the user or organization Memtro should act for.
Create a token named Memtro and copy it. It starts r8_ and has every right of its account: runs Memtro starts are billed there, only when somebody asks.
In Memtro, open Connections → Replicate and paste it into API token.
Ask your first question: which predictions failed today?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Replicate tools are the same everywhere.
Only when you ask, and only what it has been granted: run a model (billed per second or per output by Replicate); run a deployment (billed, and may wake an instance); cancel a running prediction; start a training (fine-tune) of a model version into a destination model (billed); cancel a running training; create a deployment of a model version on chosen hardware (billed while instances run); change a deployment's hardware, instance counts or version; delete a deployment (only after 15 minutes offline); create a model (public or private); change a model's description, readme or links; delete a private model with no versions; delete a model version, with all its predictions and output files. 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 token. In Replicate, open Account → API tokens and choose the user or organization Memtro should act for.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Replicate, choosing the same kinds; the tab shows Replicate'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