Live API + npm packages published

Praetor runs agent missions you can approve, meter, and prove.

A charter declares the goal, budget, tools, sandbox, and outputs. Praetor validates the mission, gates spend through MnemoPay, streams activity, and writes an audit trail your team can defend.

Run your first charter Choose hosted access
28 npm packages 550 tests green pt_live API keys Article 12 bundle
Production posture

Not another agent demo. A runtime with receipts.

Praetor is already packaged, deployed, and wired to billing. The customer UI should make that obvious before anyone opens GitHub.

28published packages under @kpanks
550passing tests across the stack
100free charters per month via portal
1budget, sandbox, audit path per mission
How it works

The charter is the contract. Praetor enforces the runtime.

Customers should understand the product in four moves: declare, gate, execute, prove.

01

Declare the mission

Write a YAML charter with the goal, tools, budget, approval threshold, sandbox, and required outputs.

02

Gate every paid action

FiscalGate routes paid tools through MnemoPay holds before work starts, so runaway missions hit the cap.

03

Execute in a sandbox

Docker hardening, SSRF guards, tool validation, and role-scoped registries keep missions inside the charter.

04

Export the proof

Every tool call, artifact, and network request can be signed into a Merkle audit chain and Article 12 bundle.

Live mission flow

Buyers need to see the control plane.

Praetor's customer story is not magic. It is a visible chain of approvals, holds, tool calls, sandbox events, and settlement.

00:01Charter validatedok
00:03MnemoPay hold created$0.25
00:07Browser tool allowedscoped
00:19Article 12 leaf signed#a81f
activity stream live sample
Use cases

One runtime. Many agent surfaces.

Praetor is strongest when the mission touches money, credentials, files, browsers, generated media, compliance records, or customer-facing artifacts.

BR

Browser operations

Drive Chromium through DOM-first automation for scraping, admin panels, forms, and workflows that need a real browser.

CD

Coding charters

Run repo-aware coding missions with scoped file tools, test commands, audit logs, and budget caps.

UG

UGC and design

Route design, video, voice, 3D, SEO, and social tasks through one governed mission envelope.

KB

Knowledge work

Scrape, chunk, synthesize, and store source-backed research with SSRF guards and evidence output.

AP

Agent APIs

Expose governed agent actions behind hosted API keys and plan limits through the BizSuite portal.

EU

Audit readiness

Export a tamper-evident trail when customers ask what happened, what it cost, and which tool touched what.

Developer path

Install locally or call the hosted API.

Self-hosted developers can start with the CLI. Customers who want hosted keys can use the same portal path as MnemoPay and GridStamp.

local installnpm
npm install -g @kpanks/cli

PRAETOR_DEV_MODE=1 praetor serve

praetor run charters/demo-basic.yaml \
  --article12 ./audit-bundle
hosted apipt_live
curl https://praetor-api.fly.dev/api/v1/missions \
  -H "Authorization: Bearer pt_live_..." \
  -H "Content-Type: application/json" \
  -d '{"goal":"audit this workflow"}'
Access model

Start with charters. Scale with controls.

The portal already issues Praetor API keys. The UI should make the path easy for builders, teams, and enterprise buyers.

Free
100

Charters per month for builders proving the runtime.

  • pt_live API key
  • CLI quickstart
  • Basic mission history
  • Community support
Get started
Pro
5,000

Charters per month for teams running recurring agent work.

  • Hosted API access
  • Higher mission limits
  • Fiscal gate reporting
  • Audit bundle exports
Request Pro access
Enterprise
Custom

For regulated teams that need governance, evidence, and deployment control.

  • Unlimited plan option
  • Private deployment path
  • Compliance review support
  • Custom tool allowlists
Talk to BizSuite
Positioning
Praetor is for the moment after the demo, when someone asks who approved the action, what it cost, where it ran, and how you prove it.
Questions buyers ask

Make governance legible before procurement asks.

Is Praetor an IDE?

No. Praetor is the runtime layer underneath agent work: charters, budgets, tools, sandboxing, and audit output.

Can I self-host it?

Yes. The CLI and packages are published. Hosted API access is available through the portal path.

What makes it different from a framework?

Praetor ships fiscal gating, audit logging, sandbox controls, and tool governance as defaults rather than add-ons.

Does it support creative and web work?

Yes. Praetor includes native packages for design, UGC, world generation, games, SEO, scraping, voice, and browser work.

Run the first governed mission

Give your agents a charter before you give them authority.

Install the CLI, run a demo charter, or request hosted API access through BizSuite. Praetor is built for work that needs a budget, a sandbox, and an audit trail.

Open GitHub Get hosted access