Integrations

Scan where you already write.

Pre-Trip does not have to be a separate tab. Bring the same source-cited compliance check into the tools your team drafts in, so a flag lands before you publish, not after.

A Chrome extension, a WordPress plugin, an MCP server, and a keyed API. Your drafts are scanned, not kept.

Four ways to connect

One engine, many front doors.

Available

WordPress

A compliance check right in the post editor. Pick the state and vertical, run the check, and get a pass or a fix list before the post goes live. Works in the block and classic editors.

Set it up
Available

The API

Build your own. The same engine over a keyed REST endpoint: paste, a live URL, or a creative image in, a source-cited verdict back. Versioned and rate-limited.

Read the API docs
Available

Browser extension

Check copy anywhere you write it, email platforms, ad managers, and any CMS, without leaving the page. Select the text, run the check, get the same source-cited verdict. Live in the Chrome Web Store.

Add to Chrome
Available

AI drafting tools

Scan from inside Claude, Cursor, and any MCP client, so a compliance check rides along as you draft. Connect the Pre-Trip MCP server with an API key. A one-click hosted connector is in beta.

Set it up
Every integration needs a Pre-Trip API key. Create a free account at scan.kesey.agency, then make a key under API keys and paste it into the extension, the plugin, or your own code. Keyed scans spend the same allowance the scanner does: your free checks first, one per asset type, then a Bus Pass or tokens.

Wire it into your stack.

Add the extension, install the plugin, or create a key, and the same rules the scanner runs go where your team already works.

Get an API key

Pre-Trip is a rigorous screen, not legal advice, and passing a scan is not a legal opinion. The integrations carry the same posture: your draft is scanned to run the check and is not stored. See Trust for how we draw that line.