Which Uploadcare files were uploaded this week but never stored?
Uploadcare connects Memtro to your file uploads and storage. It reads the project, files by upload date and state, and one file's type, size, dimensions, tags and metadata key names. It searches files by name, metadata, type, tags, size or date, and reads file groups. When asked and granted, it can store or permanently delete files, copy a file, set or delete a metadata key, change tags, and delete a group. Uploadcare can tell Memtro as a file is uploaded, stored or found infected, and a job can start on it. Unstored files are removed 24 hours after upload.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Uploadcare tool, reads what it needs, and answers with the source cited.
These tools change something in Uploadcare. 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, choose the kinds you want, and Memtro registers its address with Uploadcare for you. Each event can start a job, with the event as its input. Uploadcare signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Uploadcare 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 files uploaded this week are still temporary?
How many files are stored in the project?
Find the images tagged hero.
Which files were removed last month?
Store the files uploaded this morning.
Dan Fletcher, web lead at Northwind, asked which product images from Monday were still temporary. Memtro listed the temporary files uploaded that day with name, type and size. It reminded him that Uploadcare removes them 24 hours after upload unless they are stored.
Acme Ltd set a job to start when Uploadcare reported a virus in a file. When one arrived, Memtro read the file's details and tagged it quarantine, as granted. Maya Okafor, IT manager, read the job's summary and asked Memtro to delete the file, which it did.
The teams that lean on Uploadcare most, a question each of them asks, and what they connect beside it.
A record in Uploadcare 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.
Jotform
DataForSEO
Moz API
Hygraph
Paperform
Kajabi
Kontent.ai
Teachable
WufooIn Uploadcare, open your project, then API keys. Copy the public key at the top, then add a secret key or use an existing one. A key pair reaches the whole project.
In Memtro, open Connections → Uploadcare and paste the Public key and the Secret key. Memtro signs each request with the secret and never sends it.
An administrator grants the store, delete, metadata and tag actions by name to the teams that may use them.
Ask which files were uploaded this week but never stored. Events are turned on from the connection's Events tab.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Uploadcare tools are the same everywhere.
Only when you ask, and only what it has been granted: store files so they are kept permanently; permanently delete files; copy a file within the project; set a file's metadata key; delete a file's metadata key; add or remove a file's tags; replace a file's tags; delete a file group (its files are kept). 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.
Public key and secret key. In Uploadcare, open your project, then API keys. Copy the public key at the top, then add a secret key or use an existing one. A key pair reaches the whole project.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Uploadcare for you. 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
