Actum
Docs

Agent-ready in minutes.

Scan to see where you stand, drop in one snippet to start logging agents, then run the probe and deploy fixes. No SDK to learn — it's an HTTP beacon and a few generated files.

1 · Install the collector

The collector logs AI agents hitting your site. The server version catches everything — including non-JS crawlers like GPTBot — so use it if you can. Grab your ingest key from the dashboard and choose how to install.

★ WordPress — no code

The easy path for ~40% of the web. Download the plugin, upload it under Plugins → Add New → Upload, then paste your two keys under Settings → Actum. It logs agents and serves your llms.txt + agent.json on your own domain automatically — kept in sync by Actum.

Download the WordPress plugin →

Prefer code? Drop one of these in instead:

Server / edge (recommended)
// middleware.ts — Actum collector (catches every agent, incl. non-JS crawlers)
import { NextResponse } from "next/server";
import type { NextRequest } from "next/server";

export function middleware(req: NextRequest) {
  fetch("https://tryactum.ai/api/collect", {
    method: "POST",
    headers: { "Content-Type": "application/json", "X-Actum-Key": "YOUR_INGEST_KEY" },
    body: JSON.stringify({
      ua: req.headers.get("user-agent"),
      ip: req.headers.get("x-forwarded-for") || req.ip,
      path: req.nextUrl.pathname,
      referrer: req.headers.get("referer"),
    }),
  }).catch(() => {});
  return NextResponse.next();
}
export const config = { matcher: "/:path*" };
Browser fallback
<!-- Browser fallback — drop into any page -->
<script>
fetch("https://tryactum.ai/api/collect", {
  method: "POST",
  headers: { "Content-Type": "application/json", "X-Actum-Key": "YOUR_INGEST_KEY" },
  body: JSON.stringify({ ua: navigator.userAgent, path: location.pathname, referrer: document.referrer }),
  keepalive: true,
}).catch(function(){});
</script>

Human traffic is dropped at the door — only AI agents are logged, so there's no personal browsing data stored.

2 · The engines

Journey

An AI buyer runs a real buying task on your live pages and reports the stage it falls out — shortlist, fit, or reaching the checkout. Learn more →

Agents

A Watcher re-runs the probe and flags regressions; Fix agents generate and host the artifact that closes each gap. Learn more →

Demand · supporting signal

Classifies which AI systems read your site and surfaces volume, trend, and high-intent live fetches — a discovery signal, not a count of transacting agents. Learn more →

Readiness

A neutral agent-readiness score, tracked weekly, with regressions flagged the moment a change breaks a fix.

3 · Built on the standards

The artifacts Actum generates speak the emerging agent-commerce standards, so you're building on the rails the platforms are standardising — not a proprietary dead end.

ACP

Agentic Commerce Protocol (Stripe / OpenAI) — product feeds & agent checkout.

MCP

Model Context Protocol — a structured endpoint agents read for context.

AP2

Agent Payments Protocol (Google) — agent payment authorization.

When you deploy a fix agent, Actum holds the master copy and re-generates it from your site on every Watcher run, so it stays correct as your offer and the standards move — you never touch it again. Your own domain serves the live copy (via the WordPress plugin or a one-line snippet), so an agent reads the current version at yoursite.com, not ours.

Start with a scan.

See your score in ~30 seconds, then grab your ingest key and install the collector.