Integrations
Solved Enroll connects over HTTPS: a REST API for records and quoting, signed webhooks for events, and an MCP server so an agent runtime can rank plans mid-conversation.
Three ways in, and one honest caveat
Everything on this page is a protocol or an API. That is deliberate, and it is also the limit of what we will claim.
- REST API. Clients, health profiles, quotes, recommendations, plans, applications, documents, and agency structure, over HTTPS with bearer-token auth, JSON bodies, cursor pagination, and idempotency keys on writes.
- Webhooks. Signed, timestamped deliveries when a case moves: created, quoted, ranked, sent, signed, submitted, acknowledged. Retried with backoff for up to 24 hours.
- MCP server. Tool discovery and tool calls, so an LLM agent runtime can rank plans and read back the reasoning without you rebuilding Medicare and underwriting logic.
Solved Enroll is in private beta. Integration credentials come from onboarding into a cohort or from a licensing conversation ahead of the 2027 public rollout. Join the waitlist to get in line.
What "compatible" means here
This page describes protocol and API-level compatibility only. Solved Enroll can connect to a dialer, a CRM, an agency management system, a warehouse, or an agent runtime because both sides speak HTTPS and JSON, not because of any commercial arrangement. Nothing on this page is a partnership, a certification, a carrier endorsement, an accreditation, or a marketplace listing, and we will not describe it as one. Carrier availability depends on the appointments your agency holds and on the submission method each carrier supports. AgentTech Dialer and Solved Telephony are sibling companies under Solved Ventures, which is a corporate fact rather than a technical claim.
Dialers and contact centers
The agent is already on the phone. The point of the integration is that the case is open by the time they say hello.
AgentTech Dialer
Click to quote from a live call. When the dialer connects, it posts the contact to the clients endpoint with its own lead identifier; Solved Enroll matches an existing client or creates one and returns a case reference the dialer deep-links the agent into. Quote and enrollment events come back as webhook deliveries, so the dialer disposition reflects what actually happened on the case.
AgentTech DialerAny dialer or CRM with click-to-call
The same flow works for any system that can make an HTTPS request. Post the contact fields plus your own external reference, get a client and case reference back, and open the case in a browser tab from your existing click-to-call button. There is no plugin to install on either side.
Clients endpointsInbound calls and warm transfers
On a transfer, the receiving agent needs the case rather than a summary of it. Look the client up by the external reference your platform already stores and open the case in the state the first agent left it, including a partially completed intake and any quote already run.
Resuming a caseCall references on the case
A call identifier, a recording URL, and a transcript URL from your telephony provider can be stored on the case as external references. A later compliance review of an enrollment can then reach the conversation that produced it without joining two systems by hand.
Documents endpointsCRM and agency management systems
Connected over the REST API and webhooks, in whichever direction your system prefers to work.
Two-way client sync
Create and update client records over REST, list them with cursor pagination, and merge duplicates when the same person arrives twice from two sources. Writes accept an idempotency key, so a retry after a timeout on your side does not produce a second record.
Clients endpointsOutcome push by webhook
Subscribe to quote.completed, recommendation.ready, application.sent, application.signed, application.submitted, and application.acknowledged. Your agency management system learns the outcome within seconds of it happening rather than at month end from a spreadsheet.
Webhook eventsYour identifiers, not ours
Clients, quotes, and applications all accept an external reference you control. Reconciliation runs against the keys your system already trusts, so you are not forced to store our identifiers in a custom field to make reporting work.
External referencesScheduled reconciliation
For systems that prefer batch, pull everything changed since your last cursor on a nightly schedule. Same data, same permissions, no webhook listener to keep online. Both models can run at once: webhooks for speed, a nightly pull as the backstop.
Pulling over the APICarrier submission
Electronic submission and status acknowledgement, in the format each carrier accepts.
Electronic application submission
A completed, signed application is transmitted electronically on the forms the carrier accepts rather than printed, scanned, and emailed. What each carrier accepts differs, and the platform holds the format and the field mapping per carrier so the agent never has to know which one wants what.
EnrollmentStatus acknowledgement
Submission state moves from submitted to acknowledged to a final disposition as the carrier responds. Every transition is written to the case with a timestamp, readable over the API, and delivered as an application.acknowledged webhook, so nobody logs into a carrier portal to find out.
Applications endpointsRequirements and corrections
When a carrier raises a requirement or rejects an application, the reason lands on the case. The correction is made against the existing case and resubmitted, rather than the agent starting a new application and losing the original trail.
Fixing a rejectionVersioned forms and rules
Carrier forms and underwriting rules are versioned with effective dates. An application submitted last quarter can be reviewed against the rule set and form version it was actually written under, which is what a carrier audit asks for.
Encoded carrier rulesWhich carriers you can submit to depends on the appointments your agency holds and on what each carrier supports. Nothing here asserts a carrier partnership or endorsement.
Data that comes in
Four feeds decide whether a quote is real. They are loaded, versioned by plan year, and applied before plans reach the screen.
CMS eligibility and enrollment history
Entitlement, current enrollment, and election period are checked before plans are shown, so the plan you quote is one the client can actually elect.
Eligibility checksPlan and formulary data
Benefits, premiums, service areas, formularies, tier placement, utilization management, and pharmacy pricing, loaded per plan year and kept versioned rather than overwritten.
Drug cost modelingProvider directories
Doctor and pharmacy network status is matched against the plans on screen, so a provider the client named is confirmed before the plan reaches the comparison.
Shop by doctorCarrier underwriting rules
Life rules are encoded as data rather than documentation: knockouts, lookback periods, build charts, medication implications, and rate class logic, versioned per carrier.
Underwriting rulesData that goes out
Four ways to get your book into your own systems, from a file on a schedule to a live event stream.
Scheduled CSV
Pick the records and the fields, set a cadence, and collect the file from a secure location. Useful when the receiving system is a spreadsheet or a person.
Scheduled exportsAPI pull
List endpoints with cursor pagination and a changed-since filter, up to 100 records a page, using the same permissions as the user the token belongs to.
List endpointsWebhook streams
Signed, timestamped deliveries for every case event, retried with backoff for up to 24 hours so a brief outage on your side does not lose the event.
WebhooksWarehouse export
A wider, flatter extract of clients, quotes, recommendations, applications, and case events, shaped for loading into a warehouse rather than for reading by a person.
Warehouse exportsE-signature delivery
One signature packet, three ways to put it in front of the client, chosen at the moment you need it.
Text message
A signing link delivered by SMS to the number on the client record, which is the only option that works when the client is on the phone and nowhere near a computer. A failed delivery can be resent to a different number without rebuilding the packet.
EnrollmentIn-person tablet
Hand the device over at the kitchen table. The packet opens in signing mode with the agent view hidden, the client signs, and the device returns to the case. Same forms, same audit trail as a remote signature.
Signature deliveryAn emailed packet for the client who wants to read it before signing, or who needs a family member present. Partial saves mean they can stop, come back, and finish rather than starting the application again.
Partial savesAI and agent runtimes
The AI Plan Recommender is the piece other systems most want, so it is available on its own. Rank plans from inside your own product, mid-conversation, and get the reasoning back with the ranking.
As a REST endpoint
Post a client profile and the lines you are contracted for, get ranked plans back with a score and the factors behind each one. Any language, any runtime, one HTTPS call. Deterministic, so the same profile returns the same ranking and a past case can be reconstructed.
Recommendations endpointsAs an MCP server
An agent runtime lists the available tools, calls the one it needs, and reads structured results back. Your model does not need to learn Medicare rules or carrier underwriting; it needs to know which tool to call and what the result means.
MCP endpointsMid-conversation ranking
Because the call returns a ranking and an explanation rather than a wall of plan data, an assistant can say which plan fits and why in the same turn. Licensing the recommender is separate from platform access and is available before general availability.
LicensingAn MCP tool call
{
"method": "tools/call",
"params": {
"name": "rank_plans",
"arguments": {
"client_id": "cli_8Fq2mR",
"line": "medicare",
"product_types": ["mapd", "pdp"],
"limit": 3
}
}
}
The full tool list, the response shape, and the ranked-recommendation payload are on the API reference. Credentials for the MCP server come from onboarding or a licensing conversation.
Where to go next
The reference, the workflow, and the people.
API reference
Resource groups, endpoint tables, webhook events, rate limits, and the error format.
Read the referenceDocumentation
How the platform behaves case by case, including exports, webhooks, and field masking.
Read the docsTell us what you run
Describe your stack and we will map it to specific endpoints rather than guess at a connector.
Contact usFAQs
Integration questions
Do I need a developer to connect something?
For a scheduled CSV export, no. For click to quote from a dialer, a CRM sync, or a webhook listener, yes, someone has to make an HTTPS request and handle a JSON response. There is no visual connector builder, and we would rather say that than imply one exists.
Is there a marketplace of prebuilt connectors?
No. Solved Enroll is in private beta and there is no app marketplace, no directory listing, and no certified connector program. Integration happens over the documented REST API, webhooks, and the MCP server. If your system speaks HTTPS and JSON, it can connect.
Which CRMs and agency management systems can I connect?
Any that can call an API or receive a webhook. We describe compatibility at the protocol level rather than naming products, because naming a product implies a tested connector and a relationship that does not exist. Tell us what you run and we will tell you exactly which endpoints you would use.
Does the AgentTech Dialer connection mean anything special?
It means we can be specific about the flow, because AgentTech Dialer and Solved Enroll are both part of Solved Ventures and the click-to-quote path has been built end to end. Technically it uses the same public endpoints any other dialer would use. There is nothing in the API reserved for it.
Can an integration run in real time?
Yes. Webhook deliveries fire within seconds of the event and are retried with backoff for up to 24 hours. Scheduled pulls are there for systems that would rather ask than listen, and plenty of agencies run both: webhooks for speed, a nightly pull as the backstop.
Can my own AI agent use the plan recommender?
That is what the MCP server is for. An agent runtime discovers the ranking tools, calls them with a client profile, and gets back ranked plans with the factors behind each score, mid-conversation. The same engine is available as a plain REST endpoint if your runtime does not speak MCP. Licensing is a separate conversation from platform access.
Something else? Contact us
Connecting something specific?
Tell us the system and the direction the data needs to move, and we will point you at the exact endpoints and events.