A customer chasing
Tom Reilly, customer service lead at Acme Ltd, asked where a customer's order had got to. Memtro tracked the parcel and gave the latest status with the carrier's events, the last one a scan at the delivery depot that morning.
Where is this customer's parcel, and what is still waiting to ship?
Starshipit connects Memtro to your shipping. It reads orders waiting to ship and orders shipped, with recipient name, destination city and country, carrier, service, tracking number and status, and their items. It also reads a parcel's tracking events, shipping rate quotes, the product catalogue and carrier manifests. When asked, and once an administrator has granted the action by name, it can create an order, change an unshipped order, record tracking-only orders for parcels shipped elsewhere and add a product. Street addresses, phone numbers and emails are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Starshipit tool, reads what it needs, and answers with the source cited.
These tools change something in Starshipit. 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 Starshipit 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 orders are still waiting to ship?
Where is order 10452?
What would it cost to send a 2 kg parcel to Auckland?
Which parcels went on yesterday's manifest?
Change order 10452 to signature required
Tom Reilly, customer service lead at Acme Ltd, asked where a customer's order had got to. Memtro tracked the parcel and gave the latest status with the carrier's events, the last one a scan at the delivery depot that morning.
Priya Sharma, operations manager at Northwind, asked Memtro to make a high-value order signature required before it was packed. Memtro changed the unshipped order in Starshipit and left its other details as they were.
The teams that lean on Starshipit most, a question each of them asks, and what they connect beside it.
A record in Starshipit 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 Starshipit, open Settings → API. Each child account has its own key, which decides which account Memtro sees.
Copy the API key and the Subscription key. The Developer tier is enough.
In Memtro, open Connections → Starshipit and paste the API key and Subscription key.
Ask your first question: which orders are still waiting to ship?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Starshipit tools are the same everywhere.
Only when you ask, and only what it has been granted: create an unshipped order with its delivery address and items; change an unshipped order's reference, shipping method, signature or delivery address; record tracking-only orders for parcels shipped outside Starshipit; add a product to the catalogue. 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 Subscription key. In Starshipit, open Settings → API. Each child account has its own key, which decides which account Memtro sees.
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