Lago + Memtro

Only when you ask, and only what it has been granted: create a customer when no customer has that external id; overwrite a customer's name, legal name, email or website; send a billable usage event to a subscription; delete a customer, terminating their subscriptions; finalize a draft invoice (numbers it, may email and charge the customer); void an invoice, optionally with a credit note and refund; refresh a draft invoice's amounts; retry generating a failed invoice; retry collecting payment on an invoice; issue a credit note on an invoice (credit, refund or offset); create a coupon; apply a coupon to a customer; create a prepaid-credit wallet for a customer; top up a wallet with paid or granted credits; subscribe a customer to a plan; cancel (terminate) a subscription; change a subscription's name, end date or plan overrides; issue a one-off invoice for add-ons (not sent for payment unless asked); record a manual payment on an invoice; email a customer a payment request for overdue invoices; set an invoice's payment status or metadata; delete a draft invoice permanently; create a plan; change a plan's name, price or trial (affects its subscribers); delete a plan with no subscriptions; create an add-on; create a billable metric; change a coupon; delete a coupon; terminate a wallet; void the remaining credit of a credit note. 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 Lago open Developers → API keys and reveal the organisation's key. Lago has no read-only or scoped keys, so it carries the whole organisation's rights, and an extra key just for Memtro is a premium feature.

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 Lago 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.