Responsive

Breadth across classes with a documented API underneath and two agent-era surfaces on top. Inbound and outbound connectivity spans CRM and content systems, and Responsive frames the developer portal's purpose as connecting Responsive with a customer's systems of record, syncing governed content and automating response workflows. The REST API exposes Projects, Guided Projects, Intake, Content Library, ASK, Reports, Users and company metadata with batch operations, so integration is not limited to a prebuilt connector list.

Two further surfaces extend reach where the work actually happens: the LookUp browser extension pulls approved content into documents, spreadsheets, presentations, emails, online questionnaires and third-party portals, and the MCP server puts the platform inside Claude, ChatGPT, Cursor and Databricks Genie. No public connector directory or count is published, so the breadth shows in the API surface and the named delivery channels rather than in a catalog.

Sourcedeveloper.responsive.io and the Responsive LookUp Chrome Web Store listingread 2026-09-04

Multiple agents working over a configured response flow. Intake turns a received document into a project with approvals and owned, dated tasks; the Requirement Extraction, Import and Writing agents work through it with contributors across sales, legal and security; and Agent Studio lets the buyer build and refine custom agents in natural language.

Sourceresponsive.io/product/ai and developer.responsive.ioread 2026-10-01

A governed content library is the platform's center of gravity, and everything else draws on it. Agents match incoming questions to stored approved answers and draft fully sourced responses, with attribution back to the entry used, and the library is exposed as a first-class API resource alongside ASK, so grounded retrieval is addressable from outside the product as well as inside it.

The same corpus grounds the browser extension, which generates portal answers grounded in the approved knowledge base, and the MCP server, which Responsive describes as grounding AI assistants in approved Responsive data. That is one governed source of truth reached through four surfaces rather than four separate stores. The library persists across engagements, but it is content, not agent memory. Grounding quality depends on library hygiene that the platform does not fully automate, the usual tradeoff of a curated library.

Sourcedeveloper.responsive.ioread 2026-09-04

The vendor's own review-and-approve surface, and it is what the platform is bought for. Formal approval gates sit between a draft and a submission, sections carry named ownership, contributors are coordinated across teams rather than chased in email, and pre-submission checks run before a response leaves.

Intake creates the approvals and assigned tasks as a document arrives, so governance is the default path rather than an optional step, and Projects, Guided Projects and Intake exist as addressable API resources, which means the approval structure is a modeled object rather than a screen. Agents draft inside that process: the Writing Agent produces answers a human approves, and the Fit Analysis Agent scores go or no-bid so a team decides whether to commit before work begins. No confidence threshold that automatically withholds an answer and no blocked topic policy is documented, so the gates are procedural rather than conditional on what the AI produced.

Sourcedeveloper.responsive.io and the Responsive platform announcementread 2026-09-04

Access control and compliance are both documented, and the compliance commitments are contractual rather than promotional, which is the stronger form.

The data processing addendum contains a binding commitment to maintain SOC 2 Type 2 compliance and ISO 27001:2022 or equivalent at a minimum, with security measures enumerated in an annex and a clause preventing material reduction in protection, so the posture is an obligation a customer can enforce rather than a page that can be quietly edited.

As RFPIO the company was certified to ISO 27001 in 2020, and Responsive Bot carries Microsoft 365 App Certification with a CSA STAR registry entry.

On access, the developer portal states that access is governed by Responsive permissions, that API keys and MCP connections inherit the permissions of the issuing user or service user, and that activity is recorded for audit review, so the permission model reaches the programmatic and agent channels rather than stopping at the console. A Privacy Shield commitment names a superseded framework. No trust center or certification page is published, so the evidence is the contract and the developer documentation rather than a compliance portal.

Sourceresponsive.io/legal/dpa and developer.responsive.ioread 2026-09-04

Attribution on the answer, an audit record on the programmatic channel, and no trace of the agents in product.

Three things are real: every drafted answer carries source attribution back to the library entry it came from, TRACE quality scoring rates answers with pre-submission checks before anything is sent, and the developer portal states that API keys and MCP connections inherit the permissions of the user or service user they were issued from and that activity is recorded for audit review, so work arriving from outside is logged. Reporting is a documented core capability, with Reports exposed as an API resource.

The gap is that the audit record covers the programmatic channel rather than the agents. Nothing reconstructs why the Writing Agent selected one library entry over another, how the Fit Analysis Agent reached a go or no-bid score, or what changed in a draft between generation and approval.

Sourcedeveloper.responsive.ioread 2026-09-04

A governed content library, not memory. Approved answers and prior submissions persist in the library, which is exposed as an API resource, and the extension writes captured information back into it. No memory the agents keep and read back as their own state, with a scope, lifetime or delete path, is documented.

Sourcedeveloper.responsive.io and responsive.io/product/airead 2026-10-01

Multi-tenant cloud with no location or topology control offered. No region selection, EU or other in-region option, private cloud, VPC, single-tenant tier or on-premises route appears on the data processing addendum, the developer portal or the platform pages.

Those pages are specific enough that silence there carries weight; the DPA in particular enumerates security measures in an annex without naming a hosting region.

The gap stands out because the platform is bought partly to answer security questionnaires and trust center requests for regulated buyers, and residency is a routine line in the documents it exists to complete.

Sourceresponsive.io/legal/dpa and developer.responsive.ioread 2026-09-04

Named agents each doing its own job, plus templates to adopt. The AI page names a Requirement Extraction Agent (shreds RFXs and questionnaires for go or no-go), an Import Agent (ingests assessments with tables and dropdowns), a Writing Agent (drafts from trusted content) and Ask (cited answers), and Agent Studio lets a customer start custom agents from "proven templates". Each agent does useful work without the others.

Sourceresponsive.io/product/airead 2026-10-01

Four ways in, all of them started by someone or something outside the platform's own clock. Intake converts a received document into a project with approvals and assigned tasks; the LookUp extension detects a supported questionnaire when a user opens a portal; the MCP server lets Claude, ChatGPT, Cursor or Databricks Genie reach content and project context; and the REST API supports deterministic system-to-system automation with batch operations.

Document coverage is wide, spanning RFPs, RFIs, DDQs, ESG requests, security questionnaires, trust centers and ad hoc information requests, and the product reaches contributors in the web app, the browser and inside assistants. None of that is a trigger the platform fires itself. No schedule, recurring run, inbound email watcher, webhook listener or portal poll is documented, and every route above waits for a person or an external system to act.

Sourcedeveloper.responsive.io and the Responsive platform announcementread 2026-09-04

The customer does not choose the model and no provider is named. No model list, routing policy, per-workspace selection or bring-your-own-key option appears on the platform pages, the developer portal, the data processing addendum or the extension listing.

The MCP server is a different thing: it connects Claude, ChatGPT, Cursor and Databricks Genie to Responsive content, on Responsive's stated thesis that assistants are becoming the first place revenue teams go to answer a customer question. That is the customer choosing the interface that reads Responsive, not a choice of what powers the product. A platform can be committed to the assistant era and still expose no model choice.

Sourcedeveloper.responsive.io and responsive.ioread 2026-09-04

A published developer portal with two routes and a stated rule for choosing between them. The REST API gives programmatic access to Projects, Guided Projects, Intake, Content Library, ASK, Reports, Users and company metadata, and Responsive directs integrators to it for fine-grained control, batch operations and deterministic system-to-system automation.

The MCP server is the other route, for connecting Claude, ChatGPT, Cursor, Databricks Genie or another MCP-compatible client to Responsive content and project context without writing integration code. Both inherit the permissions of the user or service user whose key issued them, and Responsive states that activity is recorded for audit review.

Sourcedeveloper.responsive.ioread 2026-09-04

A scored check on agent output and a test step for agents. TRACE Score rates AI-generated content for accuracy, relevance and traceability against trusted sources before submission, and Agent Studio lets a customer test custom agents in live workflows and iterate before rebuilding.

Sourceresponsive.io/product/airead 2026-10-01

An agent that reads and writes inside procurement portals it has no API to. The LookUp extension, published on the Chrome Web Store by RFPIO Inc., states that with third-party portal support it extends Responsive's workflows directly into external security and procurement portals, where users detect supported portal questionnaires, generate answers grounded in the approved knowledge base, and autofill responses without leaving the portal.

It also captures new information back into Responsive from the browser, so the traffic runs both ways. Procurement and vendor risk portals are the classic case of software with no programmatic interface. Coverage is limited to supported portals rather than arbitrary software, and no general browser control, headless session or virtual desktop is documented.

Sourcechromewebstore.google.com/detail/responsive%c2%ae-lookup-for-ch/lnmbffkdpinhcccidngekokeidglicicread 2026-10-01