Skip to main content
Integrations · Peec AI
A Guild agent reads AI search visibility reports, brand perception data, and opportunity-scored recommendations from Peec AI, then acts on them by creating or updating brands, prompts, topics, and project structure. Guild stores the OAuth credential server-side so agent code never sees it. Credential policies let you restrict which operations each agent may call, and every request passes through Guild’s audit log.

Book a demo

See how teams govern agents that use Peec AI.

Talk to sales

Get access to Guild, then connect Peec AI to your first agent.

What the Peec AI integration exposes

The tools cover brand and competitor management, prompt and topic lifecycle, product catalog entries, and project configuration including teams, tags, categories, and saved views. Reporting tools return brand visibility, win rate, sentiment, shopping metrics, domain and URL citations, AI referral traffic, and agent readiness audits. Additional tools manage facts for claim checking, content optimisation actions, and the brand-perception attribute taxonomy. Tools use the prefix peec_ai_ and are imported from the guildai~peec-ai package.

How it works

1

Open Credentials and connect

In Guild, go to Access & setup > Credentials, click Connect, and select peec-ai. Guild sends you to Peec AI to authorize access and returns you when done.
2

Scope the credential

Guild supports account, workspace, member, and agent-scoped credentials. See Credentials to pick the scope that fits your team.
3

Import tools into your agent

Import PeecAiTools from the guildai~peec-ai package and spread it into your agent’s tools object. Use pick() as described in Tool sets to include only the tools your agent needs.

Why Peec AI access needs governing

Peec AI projects hold competitive intelligence, brand perception data, and opportunity-scored recommendations that inform strategic decisions. A misconfigured agent could create or delete brands, archive prompts, modify the brand-perception attribute taxonomy, or invite project members at scale. Guild’s credential proxy enforces ALLOW and DENY rules from credential policies before any request leaves Guild, so you can limit an agent to read-only report tools or restrict it to a single project’s operations. Credentials are injected server-side; agent code, prompts, and containers never see the OAuth token. You can scope a credential to one workspace, one member, or a single installed agent, so the Peec AI connection used by a reporting agent never serves an agent that writes to projects. Every call passes through the audit log regardless of which scope is in use.

About the Peec AI integration

Agents can create and manage brands, competitors, products, prompts, and topics within Peec AI projects. They can retrieve AI search visibility reports, brand perception data, shopping metrics, and opportunity-scored action recommendations. Agents can also configure project structure including teams, tags, categories, and saved views. The integration is guildai~peec-ai.

Authentication

  • Type: OAuth

Setup

1

Connect Peec AI

In Guild, go to Access & setup > Credentials, click Connect, select peec-ai, and sign in to Peec AI to authorize Guild.
See Credentials for workspace, member, and agent-scoped credentials.

OAuth scopes

Scopes Guild requests in the latest published version of guildai~peec-ai:

Usage

Selecting specific tools

Tools are named with the peec_ai_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~peec-ai:

Frequently asked questions

It uses OAuth. During setup you sign in to Peec AI to authorize Guild, and Guild stores the resulting credential server-side. The catalog entry records the auth type as OAuth.
Yes. Write a DENY rule in a credential policy that targets operations such as peec_ai_delete_brands and peec_ai_delete_prompts, then add an ALLOW rule for the reporting operations you want to permit. The proxy enforces DENY before ALLOW, so the deletions are blocked even if a broader ALLOW rule also matches.
Not yet. The catalog entry for guildai~peec-ai lists no webhook events, so event-driven triggers from Peec AI are not available through this integration.
Connect a dedicated credential from the installed agent’s page or from the workspace Credentials page under the dedicated option. Guild stores it under the account that owns the workspace and never offers it to other agents or workspaces, as described in Credentials.

Put a governed agent on Peec AI this week

Book a demo

See how teams govern agents that use Peec AI.

Talk to sales

Get access to Guild, then connect Peec AI to your first agent.
Also runs on Guild: AWS CloudWatch · Datadog · Google Logging · New Relic Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026