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

The gate: there mostly isn’t one

Unlike most systems on this list, NowCerts lets the agency switch on its own API. An admin sets it up under Agency Profile, Configure API, and the API signs in as a NowCerts user, so the connector sees exactly what that user sees. Give it a dedicated integration user.

The catch is the plan. Third-party pricing summaries report that the entry tier has no API access and the middle tier caps the number of integrations, which a Claude bridge would count against. NowCerts’ own pricing page did not confirm this when we checked, so ask before you build.

• No vendor review, no letter of agreement, no API fee that we could find.
• No published rate limit, so build in backoff anyway.
• The product now carries the Momentum name; the API is still at api.nowcerts.com.

What NowCerts gives you, and what it doesn’t

Momentum’s AI (AI support, smart workflows, an AI receptionist through a partner, a renewal agent) is its own and does not mention MCP or Claude. What it does ship is the most open integration surface of the six:

• OData list endpoints for insureds, policies, vehicles, drivers, agents, tasks and opportunities, with filters on change date for real delta syncs.
• Write endpoints for prospects, insureds, policies, quotes and tasks.
• Webhooks for about 300 event types (insured created, policy updated, status changed, prospect converted), sent to one URL the agency sets. Signing is not documented.
• A Zapier app with policy, quote, insured and prospect triggers. It is private and reached through an invite link, and Zapier access can lapse.

How you would actually connect Claude to NowCerts

This is the one system where a developer can start today. The bridge is an MCP server that tells Claude which NowCerts actions exist and calls the API when asked; a webhook receiver beside it handles the work nobody asks for.

1. 01
   Turn on the API and create an integration user

   Agency Profile, Configure API. Give the user only the access the connector needs.
2. 02
   Build read tools on the OData lists

   In our build, list calls needed $top, $skip and $orderby sent together, and $select and $expand returned server errors, so trim rows inside the bridge before Claude sees them.
3. 03
   Add writes, and verify each one

   Writes accept unknown fields silently and return success with nothing saved, and they use different field names than reads. Read back every record you create while testing.
4. 04
   Point the webhooks at a receiver

   Claude cannot receive them. A small receiver keeps a mirror current and starts jobs (or calls the Claude API) when a policy changes.
5. 05
   Choose where it runs

   A remote server added to Claude as a custom connector, or locally beside Claude Desktop with the credentials on one machine.

The limits that actually matter

• API access may depend on your plan tier, and the middle tier reportedly caps integrations.
• The public docs are wrong in places, and wrong writes fail quietly: a task with the wrong field names saves blank, attached to nothing.
• Webhook signing is not documented, so verify the source another way (a secret in the URL, an allowlist).
• Lists return whole rows, which is a lot of text for Claude unless the bridge trims it.

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 NowCerts needs a listener running outside Claude.

If you want NowCerts work that runs on its own

We are an engineering team that builds automation on top of the AMS an agency already runs. For NowCerts 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 NowCerts events and checked by rules where a wrong number matters.

• A Claude connector on your NowCerts book, built on the quirks we have already mapped, hosted and permissioned.
• Webhook-driven jobs: a new insured gets its ACORD prepped, a policy change gets checked against the carrier, a cancellation opens a task.
• For trucking books, policies matched to FMCSA filings so a lapse or an unscheduled truck shows up before the carrier calls.

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

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 + NowCerts, answered.