Does Profound have official SDKs?

Yes. Profound publishes official Python and JavaScript or TypeScript SDKs for its REST API, including authentication, retries, error handling, and asynchronous support.

Can Claude or ChatGPT connect to Profound through MCP?

Profound publishes a hosted MCP server for compatible AI clients. It can expose visibility, sentiment, citations, raw data, Agent Analytics, and Agent build or run operations.

Does Profound publish outbound webhook support?

Not in the current public integration catalog or developer index we checked. That does not prove private support is unavailable, so buyers should request the exact event, authentication, retry, and log behavior in writing.

Profound integrations, API, MCP and export options

Quick answer

Does Profound have the API, MCP, exports, Looker, and integrations this team needs?

Profound has a substantial integration stack: CSV and JSON exports on Growth and Enterprise, an Enterprise REST API with Python and TypeScript SDKs, a hosted MCP server, a Tableau connector, and a broad native integration directory. Its Looker connection pulls Looker data into Profound Agents; it is not a Looker Studio export. A customer-facing outbound webhook product is not publicly documented, so buyers should verify event delivery and plan entitlements in writing.

Published by Trakkr. Sources checked 2026-08-25.

Evidence: Profound pricing and plan comparison, Create, manage and tag prompts, Profound SDK and REST API documentation, Profound MCP overview, Profound Tableau connector usage, Connect Looker to Profound, Profound integrations directoryNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.

Key facts and evidence

CSV and JSON: Growth and Enterprise; not StarterEvidence: Profound pricing and plan comparison, Create, manage and tag prompts
REST API: Enterprise on the current public plan tableEvidence: Profound pricing and plan comparison
SDKs: Official Python and JavaScript or TypeScript packagesEvidence: Profound SDK and REST API documentation
MCP: Hosted server for analytics, raw data, Agent Analytics, and Agent operationsEvidence: Profound MCP overview
Business intelligence: Tableau export connector; Looker reads into Profound rather than exporting to Looker StudioEvidence: Profound Tableau connector usage, Connect Looker to Profound
Outbound webhooks: Not publicly documented as a customer event productEvidence: Profound integrations directory, Profound SDK and REST API documentationNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.

Profound integration paths and buyer checks

Profound integration paths and buyer checks
Need	Profound	Trakkr	Decision check
Simple data export	CSV and JSON on Growth and Enterprise	CSV plus scheduled Sheets and Looker Studio paths are documented	Test the exact fields, filters, and schedule your report needsEvidence: Profound pricing and plan comparison, Create, manage and tag prompts, Trakkr integrations directory
REST API	Enterprise; default 600 requests per hour per key	Scale and Enterprise	Compare endpoint scope, mutation rights, quotas, and contract accessEvidence: Profound pricing and plan comparison, Profound SDK and REST API documentation, Trakkr API reference
MCP	Hosted server for Profound data and Agent operations	Available on every paid plan	Confirm Profound MCP entitlement in the proposed planEvidence: Profound MCP overview, Trakkr API reference
BI connector	Tableau imports Profound data; Looker data flows into Profound	Looker Studio live dashboards and Sheets are documented	Name the direction of data flow, not just the vendor logoEvidence: Profound Tableau connector usage, Connect Looker to Profound, Trakkr integrations directory
Event webhooks	Not publicly documented as a customer event product	Authenticated HTTPS webhooks are documented	Profound buyers should request event types, retries, signing, and delivery logsEvidence: Profound integrations directory, Profound SDK and REST API documentation, Trakkr integrations directoryNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.
Workflow integrations	Broad directory across CMS, analytics, productivity, CDN, and marketing tools	Broad action, CMS, analytics, reporting, and crawler directory	Test the required action because connector names do not prove read and write parityEvidence: Profound integrations directory, About integrations and connectors, Trakkr integrations directory

The comparison separates native Agent nodes, Aim connectors, customer-facing API access, and reporting exports because each has different direction, scope, and plan implications.

What can a team do with Profound's API, and which plan includes it?

Profound's current pricing table places API access on Enterprise. Its public REST documentation covers organization metadata, prompt creation and updates, answers, citations, visibility, sentiment, Agent Analytics, Agents, Knowledge Bases, and other report families.

Official Python and JavaScript or TypeScript SDKs handle authentication and common client behavior. The published default limit is 600 requests per hour for each API key, so high-volume reporting should model quota needs before purchase.

Evidence: Profound pricing and plan comparison, Profound SDK and REST API documentation

How do Profound MCP, Aim connectors, and Agent integrations differ?

Profound MCP lets an external compatible AI client access Profound analytics, raw data, Agent Analytics, and Agent operations. Aim connectors do the reverse kind of job: they let Aim use a third-party service inside a Profound conversation.

Native integrations add vendor-specific nodes to Profound Agents. Profound states that integration and connector lists are built separately, so a service can exist in one surface but not the other.

Evidence: Profound MCP overview, About integrations and connectors

Can Profound send its analytics to Looker or Looker Studio?

The documented Looker integration is not an outbound Profound analytics connector. It uses read-only Looker API credentials so Profound Agents and Sheets can query saved Looks or inline data from a customer's Looker instance.

Profound explicitly says this is not Looker Studio. Its documented outbound BI connector is Tableau, which imports raw answers or aggregated reports through an API-key connection.

Evidence: Connect Looker to Profound, Profound Tableau connector usage

What can a Growth buyer export without Enterprise API access?

Growth publishes CSV and JSON exports, and the prompt export includes prompt, topic, tags, visibility, average position, citation share, citation ranks, and executions. Starter publishes no export entitlement.

A public event-webhook product was not found in the current integration directory or developer index. Profound Agents can integrate with services, but buyers needing event delivery should ask separately about supported events, authentication, retry policy, signatures, and logs.

Evidence: Profound pricing and plan comparison, Create, manage and tag prompts, Profound integrations directory, Profound SDK and REST API documentationNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.

Evidence and method

API access is documented at endpoint level

Profound publishes endpoint families, SDK installation, authentication behavior, and a default rate limit rather than only a generic API claim.

Evidence: Profound SDK and REST API documentation

The integration directory is broad and current

The public directory names CMS, CDN, analytics, productivity, marketing, and research services with individual product pages.

Evidence: Profound integrations directory

Looker direction is explicit

Profound's developer documentation clearly says Looker is read-only, flows into Profound, and is different from Looker Studio and the Tableau export connector.

Evidence: Connect Looker to Profound, Profound Tableau connector usage

Webhook uncertainty is bounded

The absence finding is limited to the current public catalog and documentation index and does not claim that private or planned webhook support is impossible.

Evidence: Profound integrations directory, Profound SDK and REST API documentationNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.

How we checked this page

We separated exports, REST API, MCP, native Agent nodes, Aim connectors, inbound analytics sources, outbound BI, and event webhooks before checking entitlement and data direction.

1. Read Profound's current pricing, integration directory, help center, API index, MCP overview, Looker guide, and Tableau connector documentation.
2. Mapped each buyer request to the exact integration surface and recorded whether data moves into Profound or out to another system.
3. Checked the comparable Trakkr paths against current official Trakkr integration and API documentation.

Limitation: We did not authenticate to the Profound API, inspect a private connector catalog, or test negotiated Enterprise quotas.
Limitation: Integration actions, scopes, and entitlements can change independently even when a vendor remains in the public directory.

When is Trakkr or Profound the better integration fit?

Choose Profound when an Enterprise team wants its AI visibility data inside custom engineering workflows, Tableau, or a broad Agent integration ecosystem. Profound's documented REST surface and official SDKs are deeper than a simple export feature, and its Looker connection is useful when Agents need business data from Looker.

Choose Trakkr when the required path is Looker Studio, event webhooks, paid-plan MCP, or a Scale-level REST API without a custom Enterprise Profound contract. Trakkr documents those routes directly, while Profound's public catalog does not document outbound event webhooks or a Looker Studio export.

Evidence: Profound SDK and REST API documentation, Profound Tableau connector usage, Connect Looker to Profound, Profound integrations directory, Trakkr integrations directory, Trakkr API referenceNot publicly verified. Profound Agents can call external APIs, but that is not the same as a documented event webhook product. Confirm private or planned webhook support directly.

Yes. Growth and Enterprise publish CSV and JSON exports. Starter publishes no exports, and programmatic API access sits on Enterprise in the current plan table.