Who
Teams running AI agents, n8n (or similar) automation, or internal workflows that call OpenAI, Replicate, SerpAPI, Firecrawl, Apify, SAP, CRM, or custom HTTP APIs.
What calls
One POST /v1/check before each expensive or sensitive tool step — same task_hash for the same unit of work (lead, ticket, URL, prompt context).
What failure
Runaway loops: same task re-processed, budget blown, or risky endpoints hit too often. Production returns loop_detected (429) when patterns exceed thresholds.
How to test
Workflow simulator (client-side) or live demos on Use cases.
How to join the pilot
Fill the form below and press the button: it opens an email to us (no server upload yet). Or email [email protected] with the same fields.
Pilot open · apply by email

Pre-call guard pilot

Pilot for teams running expensive AI or automation workflows.

ProceedGate adds one pre-call check before costly or sensitive tools. Detect repeated tasks, budget pressure, and risky tool calls before the next paid request — in agents, n8n flows, or custom runners.

Simulate a runaway workflow Join pilot Docs

What ProceedGate blocks

Repeated tasks, budget breaches, and risky tool calls

Catch workflow loops before OpenAI tokens, enrichment APIs, CRM writes, or scraper quota spiral.

Same URL retry storms

403s, TLS errors, and flaky targets trigger exponential backoff that still slams the same URL until your actor gives up.

429 retry loops

Rate limits plus aggressive retries create a quota firehose — especially when every “retry” is another billable search.

Pagination loops

Broken “next” links and template bugs crawl “page 1” forever — each pass is another paid fetch.

Stuck AI agent tasks

Tool-calling agents can hammer the same tool input; gate before the tool hits your external API.

Shared API / proxy budget drain

One bad job should not empty the workspace key everyone else uses. Hard-stop the loop, keep the rest of the fleet moving.

Built for your stack

Drop-in ahead of the vendors you already pay

ProceedGate is HTTP-native — wrap the call site you control (runner, actor, gateway, or small proxy).

OpenAI Replicate n8n SerpAPI Firecrawl Apify SAP / CRM Internal APIs

Also works for scraping / API loops

Same guard, scraper-shaped workloads

Retry storms on the same URL or task_hash — see Scraping and retry storm lab.

Integration

Three-line Node pattern

Below matches the published @proceedgate/node API (sdk-node/README.md in this repo). Swap in your workspace key and policy id.

Example · gate before paid tool call
import { createProceedGateClient, requireGateStepOk } from '@proceedgate/node';

const client = createProceedGateClient({
  baseUrl: 'https://governor.proceedgate.dev',
  actor: { id: 'scraper-1', project: 'your-workspace-id' },
  apiKey: process.env.PG_KEY,
});

// Before SerpAPI / Apify / Firecrawl / proxy call:
await requireGateStepOk(client, {
  policyId: 'retry_friction_v1',
  action: 'tool_call',
  context: {
    attempt_in_window: attemptNo,
    window_seconds: 60,
    tool: 'serp:keyword:page-1',
  },
});

Raw HTTP checks against https://governor.proceedgate.dev/v1/check are documented on Docs and in Use cases.

Pilot offer

What you get

Lead capture

Tell us about your workflow

This is not a hosted form. The button does not POST to ProceedGate. It only opens your mail app with a draft to [email protected]. If nothing opens, copy your answers and email that address manually.

Direct line: [email protected]

Prefer another channel? Reply to the email thread after it sends, or CC the address your team already uses for vendor security reviews.

Try the runaway workflow simulator or retry storm lab (client-side only, clearly marked).