Integrations

Provider integrations

Connect your data providers to feed real growth signals into the Agent. Each provider is scoped to your workspace — credentials never cross workspace boundaries.

Available integrations

  • WebmasterID Core

    LiveIdentity & analytics

    Site ownership verification, AI referral detection, and the primary analytics layer. Required — Core is the identity foundation that all other providers attach to.

    Auth: API key (auto-provisioned)

  • Google Search Console

    LiveSearch performance

    Daily sync of clicks, impressions, CTR, and average position for all queries and URLs. Provides CWV field data and index coverage signals.

    Auth: OAuth 2.0

  • Bing Webmaster Tools

    LiveSearch performance

    Bing search performance data — clicks, impressions, and position for queries from the Bing family of search engines.

    Auth: API key

  • DataForSEO

    LiveKeyword enrichment

    Keyword search volume, competition score, CPC, and SERP feature presence for queries driving traffic to your sites. Mapped per site via the site provider mapping flow.

    Auth: API key

  • Google Analytics 4

    Coming soonUser behaviour

    Session and conversion data to correlate search performance with on-site behaviour. Coming in the M7–M12 roadmap.

    Auth: OAuth 2.0

  • GitHub

    Coming soonDeploy correlation

    Commit and release events correlated with ranking and performance shifts. Surfaces regressions introduced by specific deployments.

    Auth: OAuth app

  • Vercel / Netlify

    Coming soonDeploy correlation

    Build logs and edge cache signals to correlate deploy events with Core Web Vital and ranking changes.

    Auth: API key

Frequently asked questions

Are provider credentials stored securely?

Yes. OAuth tokens and API keys are encrypted at rest using AES-256. They are stored per workspace and never shared across workspaces or exposed to the AI execution layer.

Can I attach multiple GSC properties to one site?

You connect a GSC OAuth account to your workspace, then map a specific GSC property to each site. Multiple GSC accounts can be connected to a single workspace.

How does DataForSEO site mapping work?

After connecting your DataForSEO account, you map it to a specific site from the Provider data sources panel on the site detail page. The Agent uses the site root URL to derive the relevant keywords for enrichment.

Do all providers need to be connected?

No. Each provider is optional except WebmasterID Core. The Agent works with whatever providers you connect — fusing available signals. More providers = richer context and better-prioritised recommendations.