FetchCatch overview

FetchCatch is a decision automation platform for SaaS teams who need runtime rules, workflows, and integrations — without hard-coding every branch or adopting a full BPM suite.

You design decision flows in a visual console, connect them to your existing HTTP APIs (via OpenAPI), and expose each flow as a single HTTP endpoint your apps can call. Flows can pause when they need a human in the loop, then resume when the user completes a form or an external system sends an event.

What problems does it solve?

The three surfaces

1. Web console

Sign up at fetchcatch.com, create a workspace, and use the flow designer to build graphs. Configure API sources, auth profiles, response types, and API keys — all from the browser.

→ Using the console

2. CLI (`fcc`)

Sync flows to your repository as JSON under .fetchcatch/. Review changes in pull requests, apply from CI, and let coding agents edit rules with guardrails.

→ CLI reference · Sync & CI

3. Evaluate API

Call published flows from your backend or edge functions:

POST https://api.fetchcatch.com/v1/evaluate/{flowSlug}
Authorization: Bearer {apiKey}

→ Evaluate API

Typical journey

1. Sign up → create workspace
2. Add an API source (your OpenAPI spec)
3. Design a flow in the console
4. Define a response type (optional but recommended)
5. Publish the flow
6. Create an API key
7. Call /v1/evaluate from your app

For teams using git:

fcc init → fcc login → fcc pull → edit JSON → fcc apply

Architecture at a glance

Your app ──POST /v1/evaluate──► FetchCatch API ──► Flow interpreter
                                      │
                                      ├──► Your HTTP APIs (OpenAPI nodes)
                                      ├──► SQL (durable run state)
                                      └──► Pause until resume event

• Tenant — your organization; isolated data and secrets
• Workspace — a project within a tenant (e.g. payments, onboarding)
• Flow — a decision graph with a slug used in the evaluate URL
• Run — one execution of a flow; may complete or pause
• Response type — schema for what a flow returns

→ Core concepts

Documentation versions

This is documentation v0.1, matching flow JSON schemaVersion: 1. When schemas change, a new doc version is published alongside; see manifest.json.

Where to go next