Renewals coming up
Maya Okafor, an IT manager at Northwind, asked which domains expire in the next 60 days. Memtro listed them by expiry with whether auto-renewal was on, so she could see which would lapse.
Which of our domains expire in the next 60 days?
DNSimple hosts your DNS and registers your domains. Memtro reads domains with state, expiry and auto-renewal, zones and their records, whether a zone has reached every name server, SSL certificates, name servers, domain availability and email forwards. When asked and granted, it can create, change and delete DNS records, add and remove email forwards, switch auto-renewal and transfer lock, switch WHOIS privacy off, change name servers and delete a domain. DNSimple can tell Memtro when a domain renews or a record changes, and a job can start on it. DNSimple signs nothing, so keep the events address private.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right DNSimple tool, reads what it needs, and answers with the source cited.
These tools change something in DNSimple. 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 DNSimple for you. Each event can start a job, with the event as its input. DNSimple signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce DNSimple 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 domains expire in the next 60 days?
What MX records does acme.com have?
Has yesterday's change to the www record reached every name server?
Is acme.io available to register?
Point staging.acme.com at the new load balancer with a CNAME.
Maya Okafor, an IT manager at Northwind, asked which domains expire in the next 60 days. Memtro listed them by expiry with whether auto-renewal was on, so she could see which would lapse.
BigCo turned on DNSimple events so Dan Fletcher, its platform engineer, hears about certificate trouble. When a certificate failed to renew, a job read the domain's certificates and their expiry dates and put them in front of Dan.
The teams that lean on DNSimple most, a question each of them asks, and what they connect beside it.
A record in DNSimple 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 DNSimple, open Account → API & Access → Account access tokens, add a token named Memtro and copy it, as it is shown once. A read-only scoped token stops the actions working.
In Memtro, open Connections → DNSimple and paste the Account access token.
Add the Account ID only for a user access token. An administrator grants the record, name server and domain actions by name to the teams that may use them. Events are turned on from the connection's Events tab, and Memtro registers the address with DNSimple.
Ask which domains expire in the next 60 days.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The DNSimple tools are the same everywhere.
Only when you ask, and only what it has been granted: create a DNS record (live straight away); change a DNS record; delete a DNS record (permanent); create an email forward; delete an email forward (permanent); switch a domain's auto-renewal on (future renewals are charged) or off; lock a domain against transfer, or unlock it; switch a domain's WHOIS privacy off (publishes the registrant's contact); change a domain's name servers; delete a domain from the account (permanent). 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.
Account access token. In DNSimple, open Account → API & Access → Account access tokens, add a token named Memtro and copy it, as it is shown once. A read-only scoped token stops the actions working.
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 DNSimple 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