Ask what your ReadMe developer docs say about an endpoint, and what the changelog announced.
Connect ReadMe with a project API key and Memtro searches that project's developer docs: guides, API reference, changelog and custom pages. On a ReadMe Refactored project it also lists guide categories, the pages in each, and a guide page's text. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can publish and edit changelog entries and guide pages, which public readers and customers see on the docs site, and create or rename categories. Deleting an entry or page is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ReadMe tool, reads what it needs, and answers with the source cited.
These tools change something in ReadMe. 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 ReadMe 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.
What do our docs say about webhook retries?
Which pages are in the Getting started category?
What did we announce in the changelog this month?
Show me the text of the authentication guide
Post a changelog entry that the orders endpoint now returns tracking numbers
Support gets a question from Northwind about rate limits on the orders endpoint. Memtro searches the ReadMe docs, finds the API reference page and the guide that cover it, and answers with the documented limit and links to both pages.
After shipping tracking numbers on the orders API, Ben Carter asks Memtro to announce it. Memtro drafts an added entry, and once Ben approves the wording it publishes it publicly on the changelog, where every docs reader, customers included, can see it. ReadMe emails nobody.
The teams that lean on ReadMe most, a question each of them asks, and what they connect beside it.
A record in ReadMe 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 dash.readme.com open your project → Configuration → API Keys, create a new API key, give it a label and copy it
A key belongs to one ReadMe project, so connect each project separately. Guides and categories work only on projects using ReadMe Refactored
In Memtro open Connections → ReadMe, paste the Project API key and connect
Ask what the docs say about webhooks
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ReadMe tools are the same everywhere.
Only when you ask, and only what it has been granted: publish a changelog entry (public or link-only, as chosen); edit a changelog entry; delete a changelog entry (permanent); create a guide page in a category (public or link-only, as chosen); edit a guide page's title, text, category, state or visibility; delete a guide page (permanent); create a docs category; rename or move a docs category. 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.
Project API key. In dash.readme.com open your project → Configuration → API Keys, create a new API key, give it a label and copy it.
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
