Ask for proof. Get the real thing.
Your buyers already ask AI assistants for proof before they ever reach your website. Publish your customer stories on Proofpoints and every approved story is searchable and citable by any AI assistant, automatically, from the moment it goes live; nothing to install, nothing to configure.
This page is that promise, running. Every result is fetched live, as you type, from the published story library; nothing is cached or mocked up. Search it, pull just the numbers, follow every citation home to a story a named customer approved, and click “Show the wire” to watch the calls happen.
Under the hood is MCP, an open standard that lets AI tools ask a live source questions mid-conversation and cite what comes back; no crawling, no stale copies, no guesswork. It is also how you connect Proofpoints to the tools you already use: point your team’s assistant, your copilot or your own product at the endpoint below, and your evidence is on tap wherever the work happens.
What you’re looking at
A stranger’s AI built the first version
Before we built this page, we ran a test. We gave an AI assistant that had never seen Proofpoints the endpoint address and nothing else; no documentation, no walkthrough. We asked it to build a working proof-search page.
It worked first time: search, filters, a numbers view, and a citation on every stat. That is the situation your buyer’s assistant is in every day, and it is why the endpoint exists. The full argument is in the guide.
Read the guide: Evidence, everywhere →Point your own assistant at it
The endpoint is open: read-only, no key, rate-limited, published stories only. Any MCP-capable client connects with just the URL.
https://proofpoints.com/api/mcp