Claude + AMS360:
what works today, and what doesn’t.

The gate: a Web Service API login and a Vertafore SDK agreement

AMS360’s Web Service API (WSAPI) is set up in the Administration Center with its own login, and Vertafore says the API itself carries no additional charge. Writing a program against it is a different matter: the developer needs the Web Service SDK from Vertafore Sales, enabled on the agency’s My Vertafore login once both sides sign. No SDK price is published.

Vertafore’s Developer Portal is the newer door: REST and OData APIs with OAuth apps, built in a sandbox and promoted to live by a support ticket. It requires a licensed Developer Portal account, and scopes are limited to what the agency has contracted.

• Permissions are set per entity (retrieve, add, update, delete). Start with retrieve only.
• Tie the API login to a specific employee and secured customers stay out of reach.
• Five failed logins lock the API login for 20 minutes; a bridge has to back off, not retry.

What Vertafore gives you, and what it doesn’t

Vertafore’s AI is in-house. The Velocity AI Platform (April 2026) brought agents into AMS360, including an Email Agent and a Reconciliation Agent in early access, and its September “Agentic Agency” release added Coach and Policy Check. None of it mentions MCP, Claude or plugging in your own model; Vertafore says agent-to-agent connections for one agent arrive later in 2026.

What exists today for an outside build:

• WSAPI (SOAP) for customers, policies, suspenses, notes and activity inserts.
• Developer Portal REST and OData APIs, by contract and scope.
• An open-source AMS360 MCP server on GitHub: five read-only tools over WSAPI, one commit, launched locally. Useful as a reference, not as production software.
• No Zapier app, and no documented webhooks.

How you would actually connect Claude to AMS360

With the SDK agreement signed, the bridge is a small MCP server: it tells Claude which AMS360 actions exist and calls WSAPI or the REST APIs when Claude asks.

1. 01
   Sign for API access

   The WSAPI SDK agreement, or a Developer Portal contract with the scopes you need. Expect a sales conversation and some weeks.
2. 02
   Create a narrow API login

   Custom entity access, retrieve only on customers, policies and suspenses to start, tied to one employee.
3. 03
   Build the MCP server

   Cache the WSAPI session, back off on lockouts, and keep the login in a secrets vault, not a config file.
4. 04
   Fill the gaps with a nightly pull

   WSAPI has no agency-wide renewal date-range query. A scheduled report export or OData pull into your own store answers “what renews next month”.
5. 05
   Choose where it runs

   Locally beside Claude Desktop (simplest, credentials stay put) or as a remote custom connector with OAuth in front.

The limits that actually matter

• Robotic access is prohibited by Vertafore’s standard terms, so browser automation of AMS360 is not an option.
• The terms also bar using Vertafore’s AI features or their outputs to train models.
• WSAPI cannot list activities or query renewals across the agency; those need a report or OData pull.
• SDK and Developer Portal pricing is not published.
• No webhooks found: nothing in AMS360 can wake Claude up.

Claude itself has one more limit on every AMS: it acts when someone asks, or on a scheduled task’s clock. It does not notice a new lead, a changed policy or a cancellation notice on its own. Anything that should happen because something changed in AMS360 needs a listener running outside Claude.

If you want AMS360 work that runs on its own

We are an engineering team that builds automation on top of the AMS an agency already runs. For AMS360 that means one of two things: we build and host the bridge above so your team can ask Claude about the book, or we skip the chat window and build the workflow itself, triggered by AMS360 events and checked by rules where a wrong number matters.

• A Claude connector on your AMS360 data through WSAPI, hosted, permissioned and read-first.
• Nightly renewal and suspense digests built from AMS360 and sent to each producer, no chat window needed.
• Carrier portal entry from the AMS360 record, with quotes synced back, run from our side of the line, not as a robot inside AMS360.

The first build is live in 14 days for $2,499, charged only if your team is using it, then $2,499 a month flat. You keep the code. More on what we automate on top of AMS360 and our AMS360 integration engineering.

Trucking agency? Our Market Tracker connector already works in Claude today: it answers carrier questions (filings, X-dates, safety, ISS) from the federal record, so the AMS bridge only has to carry your own book.

Claude + AMS360, answered.