Integrations
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.
WordPress plugin available now. A keyed API for everything else. Your drafts are scanned, not kept.
Available now
A compliance check right in the post editor. Pick the state and vertical, run the check, and get a pass or a fix list where every flag quotes the sentence, names the rule, and cites the statute, before the post goes live.
Your API key is stored on your server and never sent to the browser. Every scan is proxied through WordPress. Works in the block and classic editors. Read the setup and API docs.
Three steps
In WordPress, Plugins, Add New, Upload Plugin, and choose the zip. Activate it.
Settings, Pre-Trip Compliance. Paste a key from your Pre-Trip account and set a default state and vertical.
Open any post. In the Pre-Trip box, confirm the facets and run the check before you publish.
More ways to connect
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 docsCheck copy anywhere you write it, email platforms, ad managers, and any CMS, without leaving the page. Built and in private beta ahead of the web store listing.
Request early accessScan from inside the assistants your team writes with, so a compliance check rides along as you draft. Our MCP server works with Claude and other MCP clients today, in early access.
Request early accessCreate a key, install the plugin, and the same rules the scanner runs go where your team already works.
Get an API keyPre-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.