How do AI visibility vendors differ for regulated industries?
On 17 September 2026, our publication review recorded three MCP-access plan labels for OtterlyAI: Standard, Premium and Enterprise. The vendor's SSO guide places SSO on Enterprise; differentiation for regulated buyers therefore depends on the specific documented control and plan, rather than whether an MCP connector exists.
What we measured
Measured. The three is a count of named plan labels in the published documentation record, originally published on 18 September 2026. Its OtterlyAI row has a 17 September field date. The public row receipt retains the selected fields and counting rule.
| Field | Published value |
|---|---|
| MCP connector | Yes |
| MCP plans | Standard, Premium and Enterprise; not Lite |
| Official API | Yes |
| API plans | Standard, Premium and Enterprise; not Lite |
| Record date | 17 September 2026 |
The count records public documentation, not an executed integration or a security audit. Broadcastwell publishes that comparison and is outside its table.
Reported. OtterlyAI's 18 March 2026 SSO guide, read on 29 October, describes Enterprise SAML 2.0 sign-in and a provider-assisted setup. Its 18 June 2026 assurance page, read the same day, places its SOC2 Type II audit on a roadmap with no date set. Those are separate documentation statements about identity controls and audit status.
Profound's enterprise page, read on 29 October 2026, states SOC2 Type II compliance and SSO through SAML or OIDC. Its 13 March 2025 announcement says the SOC2 report is available on request. We read the published statements; we did not obtain that report.
What this means for you
Reasoned. Keep API access separate. The dated OtterlyAI MCP row includes Standard, while its SSO guide names Enterprise. If central sign-in is a procurement requirement, a tick beside MCP access cannot settle whether the proposed plan supplies that identity-control route. Record the SSO plan and protocol as their own requirement.
For an OIDC requirement, Profound's enterprise page provides an explicit OIDC statement. The inspected OtterlyAI guide documents SAML 2.0. That gives you a published route for each comparison cell, with the OIDC position unresolved by the cited OtterlyAI guide rather than filled from its MCP row.
For audit evidence, distinguish Profound's published compliance claim from a review of the report it offers. OtterlyAI's roadmap statement supplies a different evidence state: it does not provide a completion date. A procurement record should retain those actual states instead of turning the phrase enterprise safeguards into an interchangeable audit badge.
Also asked as
I'm a coo. is there meaningful differentiation among ai visibility vendors for regulated industries, or is it marketing?
Related
- The dated MCP and API publication record
- The pinned OtterlyAI row
- The Manual on valid measurement
- Assessing evidence in a regulated business
- OtterlyAI SSO documentation
- Profound enterprise statements
Next step
For a defined public buyer-answer check, start with the Free 10-question check (one engine). No email is needed; runs are limited per network and per day, and by the site's daily allowance.
For one incorrect public product fact, Fix one answer, $490. Keep its documented source and the proposed correction together.
Claiming or correcting a vendor record is free and never depends on a purchase.
Our dated MCP and API documentation review.
Prepared by the Broadcastwell team.
Page owner: Priya Nair, Management Consultant. Corrections: hello@broadcastwell.com