Integrations
Plugged into where you already work
Everything on this page is live in the product today. CRM and analytics connections are one-time OAuth grants through your own accounts; webhooks are stored encrypted and host-pinned; and the MCP endpoint is https://mcp.ansengine.co/mcp, set up from Settings in one copy-paste.
CRM and sales pipeline
Visibility insights meet your pipeline: each captured lead can be pushed into your own CRM carrying its self-reported AI source, so revenue reporting sees which deals AI answers produced.
One-click connect (OAuth). Push a lead as a contact; the AI source and the buyer's own words land in the record. Idempotent, duplicate-safe.
One-click connect (OAuth). Push a lead as a Lead with LeadSource set to the AI answer channel; duplicates resolve to an update, never a second record.
Analytics and search
The measurement side connects to what you already run, and writes back where a real API exists.
AI referral sessions, conversions, and revenue beside your measured presence; the citation-yield join tells you which cited pages actually produce visits.
Demand, drops, and CTR quick wins; plus write actions: sitemap submission and URL inspection through your own connection.
Notify participating engines the moment a fixed page changes. Google does not use IndexNow, and we say so instead of faking a button.
Crawler logs and AI traffic
First party AI traffic from your own request logs: which AI crawlers and agents read which pages, and which AI assistants send people back. A crawler is checked against its vendor's published IP ranges where the vendor publishes them, which today is fourteen of the twenty six crawlers we classify. Anthropic publishes one list for its three bots, so a match there proves Anthropic, not which bot. A request signed with Web Bot Auth is checked against the signer's published keys. The rest are recorded as user agent only rather than given a guessed verdict. No JavaScript tracker, because bots do not run JavaScript.
A log drain to our endpoint, NDJSON with an Authorization header, on Pro and Enterprise teams. No code changes.
A Worker we generate with your key baked in, on any plan including Free; or a Logpush job with the http_requests dataset on Enterprise.
An Edge Function on any plan, or a General HTTP log drain for traffic logs on Enterprise.
Standard logging v2 through an Amazon Data Firehose stream to our HTTP endpoint, JSON or w3c output, any distribution.
Real time log streaming to an HTTPS endpoint with the JSON format string we provide, configured in the Fastly UI.
DataStream 2 to a custom HTTPS endpoint in JSON format, authenticated with a custom header.
A Cloud Logging sink for load balancer request logs into Pub/Sub, pushed to us per entry.
A must use plugin that forwards AI crawler and AI referral requests from the origin, non blocking. Works on Kinsta, WP Engine, Flywheel, Pressable and self hosted sites.
A middleware for Next.js and Node servers that forwards only AI traffic, and a REST endpoint for every other stack or log shipper.
AI assistants and developer tools (MCP)
A 64 tool MCP server: 39 reads and 25 actions covering the whole loop. Every action that spends or cannot be undone needs a second call carrying a confirmation token the server issues. The agent makes that call itself, so the token stops a slip, not an agent you authorised, and it runs under your key with your role, plan and budget.
Site audits, crawl truth, and visibility data inside the coding session: one command or one JSON block, authenticated with your org API key.
Prompt, citation, and source performance in the conversation: add the endpoint as a connector and ask about your own measured answers.
The published API over HTTPS with a Bearer key, documented endpoint by endpoint. Included from the Monitor plan up.
Workflow and automation
Alerts and exports go where your team already works.
Instant lead alerts and the daily brief in your channel via an incoming webhook, stored encrypted and host-pinned.
A catch-hook fires on every captured lead with a structured, PII-free event; fan it out to thousands of apps from there.
Append the lead ledger, named-answer evidence included, to your own spreadsheet through your own grant. CSV export ships too.
Publishing and placement
The act surface stays human-approved: drafts move only after you say so.
Approved drafts export to your CMS as drafts, receipts kept. Shopify needs a published OAuth app and is not live yet, so it is not listed as if it were.
Disclosed placements from your own connected accounts, through the approval gate, never automatic.
Full endpoint and tool reference on the API and MCP docs. Missing an integration your team needs? Tell us and we will build it or say plainly why not.