Checking a table's owner
Sarah Chen, analyst at Northwind, asked who owned the customers table and whether it was verified. Memtro read the resource with its owners, tags, documentation and verified flag.
Who owns this table, and are any data-quality incidents open?
Secoda shows you catalog resources such as tables, columns, dashboards and metrics, with their descriptions, documentation, owners, tags and usage. It reads monitors and data-quality incidents, documents, questions and their answers, lineage between resources, and tags. When asked and granted, it can document or verify a resource, write, edit or delete documents, and ask or answer a question. It can also add tags, collections and lineage, run monitors, delete a resource or lineage link, and invite a user. Running a monitor queries the warehouse. Memtro never reads users, audit logs or integration credentials.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Secoda tool, reads what it needs, and answers with the source cited.
These tools change something in Secoda. 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 Secoda 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 data-quality incidents are active right now?
Who owns the orders table?
What feeds the revenue dashboard?
Is there a document on how churn is defined?
Which questions are still unanswered?
Sarah Chen, analyst at Northwind, asked who owned the customers table and whether it was verified. Memtro read the resource with its owners, tags, documentation and verified flag.
Tom Reilly, data lead at BigCo, asked Memtro to add the agreed definition to the net revenue metric. With the action granted, Memtro updated its description in Secoda, where the workspace sees it.
The teams that lean on Secoda most, a question each of them asks, and what they connect beside it.
A record in Secoda 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 Secoda open Workspace settings, then API, and generate a new API key as a service-account user with only the access Memtro needs.
In Memtro open Connections → Secoda and paste the API key. Set API host only for EU, APAC or on-premise Secoda.
An administrator grants the documentation, monitor and delete actions by name to the teams that may use them.
Ask: which data-quality incidents are active right now?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Secoda tools are the same everywhere.
Only when you ask, and only what it has been granted: create a document; edit a document; delete a document; edit a resource's description, documentation, owners, tags or flags; delete a catalog resource; ask a question (the assignee is notified); answer a question; create a tag; create a collection; run monitors now (queries the warehouse); add lineage between two resources; delete a lineage link; invite a user to the workspace. 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. In Secoda open Workspace settings, then API, and generate a new API key as a service-account user with only the access Memtro needs.
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