Peec integrations, API, MCP and exports
A buyer's map of Peec's beta Customer API, MCP server, CSV, Looker Studio, Crawl Insights, plan gates, rate limits, and webhook uncertainty.
Quick answer
Does Peec provide the API, MCP, exports and workflow integrations this team needs?
Peec has a beta Enterprise Customer API, a capable MCP server, all-chats CSV exports, an Advanced Looker Studio connector, and Crawl Insights through Cloudflare or log uploads. The API is broad and rate-limited to 200 requests per minute per project. MCP entitlement is inconsistent across official pages, and a customer-facing outbound webhook product is not publicly documented, so those two requirements need written confirmation.
Key facts and evidence
- Customer API
- Beta and limited to EnterpriseEvidence: Introduction to the Peec AI Customer API, Peec AI pricing for brands
- API quota
- 200 requests per minute per projectEvidence: Peec AI API rate limits
- MCP
- Read analytics and crawler data; confirmed writes to project objectsEvidence: Peec AI MCP Server documentation
- CSV
- Downloadable archive of all project chatsEvidence: Manage a Peec AI project, Peec AI sidebar and settings reference
- Looker Studio
- Documented on Advanced with project-scoped accessEvidence: Peec AI pricing for brands, Peec AI Data Studio connector
- Outbound webhooks
- Not publicly documented as a customer event productEvidence: Peec AI documentation index, Introduction to the Peec AI Customer APINot publicly verified. This does not rule out private, planned, or integration-partner webhook support. Buyers should request event types, authentication, signatures, retries, and delivery logs in writing.
Peec integration routes and decision checks
| Need | Peec | Trakkr | Decision check |
|---|---|---|---|
| REST API | Beta Customer API on Enterprise with read and write endpoint families | REST API on Scale and Enterprise | Compare production status, endpoint scope, change policy, and contract entitlementEvidence: Introduction to the Peec AI Customer API, Peec AI pricing for brands, Peec AI documentation index, Peec AI Customer API changelog, Trakkr API reference |
| MCP | Rich read and confirmed-write tools, but public plan entitlement conflicts | Documented on every paid plan | Ask Peec to identify the entitled plan and supported client in writingEvidence: Peec AI MCP Server documentation, Peec AI official AI instructions, Peec AI pricing for brands, Trakkr API referenceVerification: partially verified. The capability is fully documented, but plan entitlement is not consistent across current official sources. Confirm MCP access, write permissions, and token limits for the exact plan. |
| Reporting export | All-chats CSV plus Looker Studio on Advanced | CSV, Google Sheets, and Looker Studio paths documented | Test fields, filters, schedules, and historical depth with a real reportEvidence: Manage a Peec AI project, Peec AI sidebar and settings reference, Peec AI pricing for brands, Peec AI Data Studio connector, Trakkr integrations directory, Trakkr API reference |
| Crawler data | Cloudflare Worker or CSV, CLF, and text log uploads | Crawler feeds are documented in the integration directory | Confirm retention, bot mapping, deployment ownership, and processing delayEvidence: Peec AI Crawl Insights documentation, Trakkr integrations directory, Trakkr API reference |
| Event delivery | No customer-facing outbound webhook product found in public docs | Authenticated HTTPS webhooks documented | Peec buyers should request events, signing, retries, and delivery logsEvidence: Peec AI documentation index, Introduction to the Peec AI Customer API, Trakkr integrations directory, Trakkr API referenceNot publicly verified. This does not rule out private, planned, or integration-partner webhook support. Buyers should request event types, authentication, signatures, retries, and delivery logs in writing. |
API, MCP, exports, BI connectors, crawler ingestion, and event webhooks solve different jobs. A vendor logo or protocol name does not establish direction, field coverage, or plan access.
What can Peec's Customer API do, and who gets access?
Peec labels the Customer API beta and limits general access to Enterprise. Its public index covers reports, brands, prompts, tags, topics, chats, project profiles, model channels, Agent logs, products, perception, and company data.
The surface includes read and write operations. Keys can be scoped to a company or project, and Peec recommends the X-API-Key header rather than placing credentials in a query string.
Can Peec's API support a reporting pipeline?
Peec documents 200 requests per minute for each project, standard rate-limit headers, and HTTP 429 responses when the quota is exceeded. That is enough to model a first-pass extraction schedule.
Because the API is beta, production buyers should also ask about versioning, breaking-change notice, historical pagination, retry safety, support response, and negotiated limits.
What can Peec's MCP server read and change?
Peec documents OAuth 2.0 and personal access token authentication. MCP can read analytics, sources, Actions, and crawler data, and it can change prompts, topics, tags, brands, and classifications after client confirmation.
Writes require organization-owner permission and continue to respect project access. The unresolved issue is entitlement: official MCP and AI instruction pages imply broad access, while live brand pricing does not clearly grant it on self-serve tiers.
Can a team export Peec data without the Enterprise API?
Peec documents a downloadable CSV archive of all chats for a project. Advanced also includes a Looker Studio connector with prompt, project, model, country, source, visibility, sentiment, position, share-of-voice, citation, retrieval, and usage fields.
Those routes are not equivalent to the full Customer API. Buyers should test whether the CSV and connector expose the exact historical grain, tags, competitors, citations, and schedules required by their reporting workflow.
Does Peec accept crawler logs or send outbound webhooks?
Crawl Insights accepts continuous Cloudflare Worker data or uploaded CSV, CLF, and text log files. Peec says disconnecting a source does not erase the historical crawler data already collected.
We did not find a customer-facing outbound event-webhook product in the current public documentation index or API overview. That bounded absence does not rule out private support, so event requirements need direct confirmation.
Evidence and method
The API has published scope and limits
Peec lists concrete read and write endpoint families, key scoping, header authentication, and per-project rate-limit behavior.
Evidence: Peec AI documentation index, Peec AI Customer API changelog, Peec AI API authentication, Peec AI API rate limitsMCP is operationally capable but commercially unclear
The tool surface and permission behavior are documented, while the public pages do not agree on which plans receive access.
Evidence: Peec AI MCP Server documentation, Peec AI official AI instructions, Peec AI pricing for brands, Peec AI sidebar and settings referenceVerification: partially verified. The capability is fully documented, but plan entitlement is not consistent across current official sources. Confirm MCP access, write permissions, and token limits for the exact plan.Reporting and crawler paths are specific
Official guides describe the CSV archive, Looker Studio fields, Cloudflare route, supported log formats, and retained crawler history.
Evidence: Manage a Peec AI project, Peec AI sidebar and settings reference, Peec AI pricing for brands, Peec AI Data Studio connector, Peec AI Crawl Insights documentationWebhook uncertainty stays bounded
The finding covers only the current public documentation index and API introduction, not private contracts or unreleased functionality.
Evidence: Peec AI documentation index, Introduction to the Peec AI Customer APINot publicly verified. This does not rule out private, planned, or integration-partner webhook support. Buyers should request event types, authentication, signatures, retries, and delivery logs in writing.How we checked this page
We separated REST API, MCP, CSV export, business-intelligence reporting, crawler ingestion, and event webhooks, then checked scope, direction, permissions, plan entitlement, and public maturity for each route.
- 1. Read Peec's live pricing, API introduction, endpoint index, authentication, rate-limit, changelog, MCP, Looker Studio, Crawl Insights, and project guides.
- 2. Mapped each integration request to its data direction, access scope, plan gate, output fields, and documented operational limit.
- 3. Checked current official Trakkr integration and API documentation for the comparable reporting, automation, and developer routes.
- Limitation: We did not authenticate to Peec's beta API or MCP server, inspect a private connector catalog, or test negotiated Enterprise limits.
- Limitation: The webhook and MCP entitlement findings are limited to public material and should be replaced by signed contract language when available.
When is Peec or Trakkr the stronger integration fit?
Choose Peec when an Enterprise engineering team values its broad read and write Customer API, or when Advanced buyers need its documented Looker Studio fields. Its MCP surface is capable, and Crawl Insights offers both continuous Cloudflare collection and uploaded server logs.
Choose Trakkr when procurement needs clearer public entitlements or a broader ready-made workflow set: MCP is documented on every paid plan, REST API on Scale and Enterprise, and authenticated webhooks alongside Sheets, Looker Studio, CMS, analytics, task, Slack, Zapier, and Make routes.
Peec publishes Customer API documentation, but labels the API beta and limits general access to Enterprise on its current pricing and introduction pages.
The current documented limit is 200 requests per minute for each project, with rate-limit response headers and HTTP 429 when exceeded.
The public sources conflict. MCP documentation and AI instructions imply broad access, while the live brand pricing table does not clearly include self-serve MCP. Confirm the plan in writing.
Yes. Peec documents a Looker Studio connector on Advanced with dimensions and metrics spanning prompts, models, countries, sources, visibility, sentiment, positions, citations, and usage.
We did not find a customer-facing outbound event-webhook product in Peec's current public documentation index or API overview. Buyers should verify private availability directly.
Sources and related reading
See how AI talks about your brand
Enter your domain to get a free AI visibility report in under 60 seconds.