APIs across the group
There is no Solved Ventures API. The operating companies expose them, they share a set of conventions on purpose, and credentials always come from the company that runs the surface.
Surfaces at a glance
Four companies expose an API. Each row links out to the company that publishes it, because that is where the authoritative reference and the credentials live.
| Company | What the API reaches |
|---|---|
| Solved Telephony | In production Numbers, calls, recordings, messaging, routing, and CDRs. The layer underneath anything in the group that dials, sends, or records. |
| AgentTech Dialer | In production Contacts, calls, queues, dispositions, and webhooks. The working surface for a dialer floor and the CRM around it. |
| Solved Enroll | Private beta, 2027 rollout Clients, health profiles, quotes, recommendations, and applications, plus an MCP server for AI agents that need the same capabilities as tools. |
| Solved Marketing | Operating Lead delivery by HTTP post and by webhook, delivery reports, and disposition postback so outcomes return to the program that produced the lead. |
Solved Solutions and Solved Insurance are not on this table on purpose. Solved Solutions publishes contracting and commission guidance rather than a developer API, and Solved Insurance is in development pending state approval.
Solved Telephony
Carrier-grade telephony as an API. This is the surface a platform integrates when it wants numbers and calls inside its own product rather than in someone else's console.
| Resource | What you can reach |
|---|---|
| Numbers | Search unowned inventory, reserve, buy, assign, and release DIDs, plus port state and E911 and caller identity records. |
| Calls | Originate a call, list and inspect calls, hang up, and transfer. Timestamps, billable seconds, hangup cause, route, and attestation come back on the record. |
| Recordings | List recordings, read metadata, mint time-limited signed playback URLs, and delete media on a schedule separate from the record that references it. |
| Messaging | Send SMS and MMS, read delivery receipts rather than trusting the send response, and read consent state per destination and sending number. |
| Routing | Campaigns, buyers, publishers, real-time bids, caps and dayparting, and the recorded routing decision for a given call. |
| CDRs | Query call detail records by time, direction, sub-account, number, or route, and schedule exports to object storage or an endpoint you name. |
In production, sold inside and outside the group. The authoritative reference and your credentials come from Solved Telephony.
AgentTech Dialer
The dialer and CRM surface. This is what an agency integrates when it wants its own systems to drive or observe what happens on the floor.
| Resource | What you can reach |
|---|---|
| Contacts | Create and update contacts, attach them to a campaign, read the consent reference that arrived with them, and search by any attribute you passed in. |
| Calls | Read call activity with its recording and transcript references, and read the compliance score the call was given. |
| Queues | Read and manage queues, skills, and license routing rules, including the states a producer is licensed in. |
| Dispositions | Read and write dispositions, which are the events that promote a contact toward a client record. Custom disposition sets are read from the same surface. |
| Webhooks | Subscribe an HTTPS endpoint to call progress, call completion, recording availability, transcript availability, and disposition changes. |
In production, sold inside and outside the group. The authoritative reference and your credentials come from AgentTech Dialer.
Solved Enroll
Quoting and enrollment as an API, plus the comparative underwriting method exposed as a service. Access is granted to beta cohorts rather than issued on request.
| Resource | What you can reach |
|---|---|
| Clients | Create and read client records, which are the servicing-side object a promoted contact becomes. One record, several product lines. |
| Health profiles | Write a fact-find once as a versioned profile. A quote references the profile version it was priced against, which is what makes the result reconstructable. |
| Quotes | Priced options from carrier products, produced against versioned carrier rule sets rather than against a folder of documents. |
| Recommendations | A ranked set of quotes with the reasoning that produced the ranking. The AI Plan Recommender is this resource. |
| Applications | Assemble and submit an application, with producer licensing and appointment state checked at submission, and read what came back including a decline reason. |
| MCP server | The same capabilities exposed as tools for an agent that speaks the Model Context Protocol, so an AI agent can quote and rank without a bespoke integration. |
Private beta, public rollout planned for 2027. The authoritative reference and your credentials come from Solved Enroll.
Solved Marketing
Lead delivery is the integration. It is intentionally small: a lead arrives on submission, and outcomes come back so the program that produced it can be tuned.
| Resource | What you can reach |
|---|---|
| Lead delivery post | An HTTP post to an endpoint you name, on submission rather than in a nightly batch, carrying the lead identifier, the program, the intent captured, and the consent reference. |
| Delivery webhook | The same payload delivered as a signed webhook event, for buyers who would rather subscribe than expose a form endpoint. |
| Delivery reports | What was delivered, when, against which program and filter set, and which caps or dayparting windows were in effect. |
| Disposition postback | Send outcomes back: contacted, quoted, submitted, placed, or declined. This is the flow that makes lead quality measurable against business that stayed. |
Operating. The authoritative reference and your credentials come from Solved Marketing.
What is common across them
Six conventions hold on every surface above. They match because the platform teams share infrastructure, not because a standards document told them to.
Bearer-token auth over HTTPS
Every request carries Authorization: Bearer and a token issued by the company you are calling. Tokens are scoped to an account, restrictable to read-only or to a subset of resources, and revocable individually. There is no group-wide token.
JSON bodies
Requests and responses are JSON. Timestamps are RFC 3339 in UTC, telephone numbers are E.164 in both directions, state codes are two-letter, and monetary values are strings so nothing is lost to floating point.
Cursor pagination
Collections return data, has_more, and next_cursor. Pass the cursor back for the next page. Cursors are opaque: do not construct them, and do not assume they encode an offset, because the encoding can change.
Idempotency keys on writes
Send an Idempotency-Key header on any write. A repeat of the same key returns the original response instead of creating a second resource. Generate one key per logical operation and reuse it across retries, not per HTTP attempt.
Webhook signature verification
Deliveries carry a timestamp and an HMAC over the timestamp and the raw request body, keyed with your endpoint secret. Verify against the raw bytes before parsing, compare in constant time, and reject anything outside a short tolerance window.
Predictable errors and retries
Standard status codes, a machine-readable error type and code alongside the message, and a request identifier to quote when you report a problem. Webhook delivery is at least once and not ordered, so consumers key on the event id.
The same shape, whichever company you call
One authenticated read and one idempotent write, then the envelope that comes back. Hostnames are placeholders to keep the shape readable; yours arrive with your credentials.
# a read, cursor paginated
curl "https://api.solvedtele.com/v1/calls?limit=1" \
-H "Authorization: Bearer $TELEPHONY_TOKEN"
# a write, made safe to retry
curl -X POST https://api.solvedenroll.com/v1/quotes \
-H "Authorization: Bearer $ENROLL_TOKEN" \
-H "Idempotency-Key: 7f1c9a2e-4b60-4e19-9c2f-0d3a" \
-H "Content-Type: application/json" \
-d '{"client_id":"cli_01J9K2M1Q8ZB",
"profile_version":4,
"line":"final_expense"}'
# a webhook, verified before it is parsed
X-Solved-Signature: t=1758182527,v1=9c4f2b7e1d05a3...
{
"data": [
{
"id": "qte_01J9K2M4R7T0",
"client_id": "cli_01J9K2M1Q8ZB",
"profile_version": 4,
"rule_set_version": "2026.09.1",
"created_at": "2026-09-18T14:19:46Z",
"currency": "USD"
}
],
"has_more": true,
"next_cursor": "Y3Vyc29yOjE3NTgxODI1Mjc"
}
Note what travels on the quote: the profile version and the rule set version it was priced against. That is what makes a recommendation reconstructable a year later. See versioning and change history.
Credentials come from the company, not from here
This is a property of the access model rather than an inconvenience. There is no group-wide key, because a key that opened every company would defeat the separation the group is built on.
- Issued per company. Telephony tokens from Solved Telephony, dialer tokens from AgentTech Dialer, enrollment access from Solved Enroll, delivery endpoints from Solved Marketing.
- Scoped and revocable. Restrict a token to read-only or to a subset of resources, and issue separate tokens per service so a rotation is a deploy rather than an outage.
- Per environment. Ask for a sandbox credential alongside the production one so you can build before you touch anything real.
- Never client-side. Tokens belong on your server. A credential in a mobile app or a browser bundle is a credential you have published.
- Beta access is granted, not requested. Solved Enroll issues API access as part of onboarding a cohort ahead of the 2027 rollout.
Who issues what
- Telephony
- Trunk credentials and an API token, issued with onboarding at Solved Telephony.
- Dialer
- An account-scoped token from AgentTech Dialer, plus webhook endpoint secrets.
- Enrollment
- Cohort access from Solved Enroll, including MCP server access where it applies.
- Leads
- A delivery endpoint and a signing secret agreed with Solved Marketing per program.
Partner and carrier integration paths
Four shapes cover almost every conversation that starts on this page. Pick the closest one; the group level exists to get the right companies into the same room.
Platform and technology partners
Integrate one surface or several. Most partners take telephony for the media path and either the dialer surface or the enrollment surface on top, and drive provisioning and reporting from their own product. Credentials come from each company separately.
How the group integratesCarriers
Carrier integration is normally application submission plus a data exchange: what was submitted, what was decided, and what stayed on the books. Start the conversation at the group level, because it usually spans enrollment and distribution.
For carriersAI agents
An agent runtime can drive calls over the telephony surface and quote and rank over the enrollment surface. An agent that speaks the Model Context Protocol can use the Solved Enroll MCP server rather than a bespoke tool layer.
The technologyData and reporting
Scheduled exports and webhook streams rather than screen scraping. Records land in complete files per window, so a late-arriving record appears in the window its event closed in and the arithmetic stays correct.
Records into the warehouseNaming a protocol is not naming a partnership. Everything on this page describes API-level compatibility and nothing more; see how the group integrates for the same caveat in full.
FAQs
API questions
Is there a Solved Ventures API?
No. Solved Ventures is a holding company and does not operate a product, so there is nothing for it to expose. The operating companies expose the APIs, and this page is the map. If a page anywhere claims a holding-company API, it is wrong.
Where do I get credentials?
From the individual operating company, always. A telephony token comes from Solved Telephony, a dialer token from AgentTech Dialer, and enrollment access from Solved Enroll. There is no group-wide credential to request, and asking us for one will only get you introduced to the company that can actually issue it.
Can I integrate with the group as a whole?
You integrate with surfaces, not with a group. What we can do at the group level is make sure you are talking to the right companies at the same time, so you are not the one carrying a message between two of our teams. Tell us the shape of what you are building and we will set that up.
Are these live specifications I can generate a client from?
Not from this page. This describes the surfaces and the conventions they share. Authoritative request and response schemas, and the host you call, come from the operating company with your credentials. Treat any hostname in an example here as a placeholder.
Why do the conventions match across companies?
Because the platform teams share infrastructure and review each other work. A developer who has integrated one surface should not have to relearn pagination, idempotency, and webhook signing to integrate the next one. It is one of the few genuine benefits of the layers being owned rather than bought.
Is the Solved Enroll API available now?
To private beta cohorts. Solved Enroll is in private beta with a public rollout planned for 2027, and API access is granted as part of onboarding a cohort rather than issued on request. The AI Plan Recommender is licensable as a REST API or as an MCP server, and that conversation can start now.
What about Solved Insurance and Solved Solutions?
Solved Solutions publishes contracting and commission guidance rather than a developer API today; appointment and hierarchy state is read by the other companies internally. Solved Insurance products are in development pending state approval, so there is no product API and nothing to integrate against yet.
Something else? Contact us
Tell us what you are building.
We will name the companies you need, and get their teams on the call rather than making you relay between them.