Live webinarWhat's new in Sodium: Information Requests, plus Q&A. Thu 19 Nov, 12 noonInformation Requests + Q&A, Thu 19 NovReserve your place

Give your AI agent the full Sodium API

The MCP connector covers the everyday work. When your agent needs to go further, such as reshaping hundreds of records, moving data in from another system or building something the connector's tools don't, it can work with the Sodium API directly.

You create an API key, start your agent with the prompt below, and the agent reads our guide to the API for itself. It's powerful, so limit the key to the job and delete it when the job is done.

Important notes

The MCP connector is the controlled way in. An API key lets your AI do anything the app can, limited only by the key's restrictions: much more powerful, and much more dangerous.

AI agents get things wrong. A deleted record or a sent email can't be called back.

  • Limit the key to a role. Viewer for read-only work, or on Pro a custom role with only the areas the job needs.
  • Block send unless the job is sending. Drafts still work.
  • Try a few records first before letting it loose on the rest.
  • Keep the key out of chats. Your agent will give you a private place to put it.
  • Delete the key when you're done, or straight away if anything looks wrong.

Create the key

Create it in your Sodium profile, under API Keys. Name it after the job, limit it to a role, and switch on Block send unless the job is sending.

Copy the key when it appears. Your agent will ask you for it.

Start your agent

Paste this into Claude Code, Codex, Cursor or whichever agent you use. It's ready to go as it is: the agent asks for the key and the job itself.

Paste this into your agent

I want you to work with my practice's data in Sodium, our practice management software, through the Sodium API.

Before you do anything else, read https://sodiumhq.com/docs/api/agent.txt and follow its rules. It lists a file for each area of the API: fetch only the ones you need.

I've created a Sodium API key. Don't ask me to paste it into this chat: set up a private way for me to give it to you, as the guide explains. Then check the connection and tell me which practice you're connected to.

Once you're connected, ask me what I'd like done. Check with me before you delete anything, send anything to a client, or change more than a few records. When we're done, remind me to delete the key.

The prompt points the agent at a guide written for it, not for you: how to authenticate, page through lists and handle errors, the rules above, and a file for each area of the API listing its endpoints and fields. It is built from the live API every time we publish the site, so it is never out of date. If your agent can't open web pages, download the guide and attach it.

Your data, your responsibility

The same GDPR housekeeping as the connector applies: use a business tier of your AI provider, and make sure the right data-processing terms are in place for the client data the agent will see. What an agent does with a key you gave it is done on your practice's behalf, so you stay responsible for it.

Stuck, or think the job should be a built-in tool? Tell us. What we build next comes from practices like yours.

Don't need all of that?

Use the MCP connector instead

Sign in with your own Sodium login, ask in plain English, and nothing can be deleted. It covers most of what practices want an AI assistant to do.