Get Started

Start Governing AI Actions Before They Execute

PFC sits at the execution boundary of your workflow and decides whether an AI-generated action is allowed before it commits.

No monitoring after the fact.
No trust-by-assumption.
Just deterministic control before execution.

Get Your API Key Watch Live Demo

From email workflows to automated system actions, PFC adds a control layer in front of execution so only approved actions are allowed to happen.

How onboarding works

Getting started with PFC is simple.

1

Create your account

Get your API key and access to your hosted PFC environment.

2

Test one real action

Send a sample action to PFC and see it return an allow or block decision.

3

Insert PFC before execution

Place PFC directly in front of your send, update, refund, or commit step.

4

Start governing live actions

Once connected, your workflow checks with PFC before execution every time.

What PFC does

PFC does not replace your AI system.

It governs the moment when AI output turns into action.

That means your system can still generate drafts, recommendations, and proposed actions. But before anything is sent, changed, approved, or committed, PFC evaluates the exact action and determines whether it is allowed to execute.

Example: Govern outbound email

Without PFC

Incoming email → AI drafts response → system sends

The action executes without a control decision at the boundary.

With PFC

Incoming email → AI drafts response → proposed send action goes to PFC → PFC returns allow or block → only approved actions send

PFC sits in front of the send step and governs the action before execution.

This is how PFC prevents AI from taking unapproved actions in production.

Your first live test

Use your API key to evaluate a proposed action.

curl -X POST "https://pfc-api.fly.dev/v1/evaluate" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "x-pfc-nonce: test-nonce-001" \
  -H "x-pfc-timestamp: 1700000000" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "send_email",
    "recipient": "customer@example.com",
    "subject": "Order Update",
    "body": "Your order has shipped."
  }'

If PFC returns an allow decision, the action is approved.
If it returns block, the action does not execute.

Get Your API Key Need proof first? Watch the live demo.

Where to place PFC

PFC belongs directly in front of execution.

  • before an outbound email is sent
  • before a refund is issued
  • before a CRM record is updated
  • before a workflow step commits
  • before an internal system change is applied

If an AI-generated output can change a real system, PFC should sit in front of it.

What you need to get live

1. A workflow that proposes actionsThis can be an AI agent, automation, internal tool, or application.
2. A point before executionThis is the send, update, approve, commit, or trigger step.
3. A call to PFCYour system submits the proposed action to PFC and proceeds only if approved.

Built for real production use

PFC is designed for environments where action control matters.

  • AI-generated email and support workflows
  • customer service automations
  • refunds and financial actions
  • CRM and sales automations
  • internal tools and operational systems
  • any workflow where AI output can trigger a real change

What happens after signup

Once you create an account, you can:

  • generate your API key
  • test one governed action immediately
  • connect PFC to a live workflow
  • verify governance at the execution boundary
  • move from audit and observation to actual control

Activation Path

Start with one workflow

If you already know the task you want to govern, PFC can be added at the exact step where execution happens.

Get Your API Key Or watch the live demo first

Ready To Launch

Start Governing Actions Before They Execute

The fastest way to understand PFC is to test one real action in your own workflow.

Get Your API Key Watch Live Demo

$49/month includes 1,000 governed decisions. Start with one workflow and expand as needed.

FAQ

Do I need to replace my AI system?

No. PFC sits in front of execution. Your AI can still generate outputs, but actions are governed before they commit.

What kinds of actions can PFC govern?

Any action that can be represented before execution, including sending email, updating records, issuing refunds, and triggering workflow steps.

Do I need a full integration team?

No. Many workflows can start with a simple insertion point before execution, then expand from there.

What is the fastest way to get started?

Choose one action type, get your API key, run one live evaluation, and place PFC directly before execution.