RangeFlow API

Name: RangeFlow API
Brand: RangeFlow API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

Programmatically create a workflow, list workflows. Covers 3 operations with apiKey authentication.

Install Jentic One Beta

Connect the RangeFlow API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RangeFlow API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frangeflow.com%2Frangeflow" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frangeflow.com%2Frangeflow" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with RangeFlow API.

Create a workflow

List workflows

Execute a workflow

Access RangeFlow API developer tools resources via REST API

GET STARTED

Start building with RangeFlow API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use RangeFlow API for, with concrete tasks.

★ Developer Tools Operations

Use the RangeFlow API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including create a workflow, list workflows, execute a workflow.

Call POST /workflows to create a workflow

Automated Executions Management

Automate executions operations by combining multiple RangeFlow API endpoints. Agents can list workflows and then execute a workflow in a single workflow.

Call GET /workflows to list workflows, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RangeFlow API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create a workflow', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — api for workflow and process automation.

METHOD

PATH

DESCRIPTION

POST

/workflows

Create a workflow

GET

/workflows

List workflows

POST

/executions

Execute a workflow

POST

/workflows

Create a workflow

GET

/workflows

List workflows

POST

/executions

Execute a workflow

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the RangeFlow API by hand means passing your API key in the Authorization header on every call and hand-coding requests across its workflow and execution endpoints. Through Jentic you install once, import the RangeFlow API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

RangeFlow identifies workflows and executions in the request body rather than the URL path, so scoping is operations-only: you limit the agent to the operations it needs, such as listing workflows or creating an execution. You choose which of those operations it may call, so anything you leave out is not available to it.

Credential isolation

Your RangeFlow API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a workflow' or 'start an execution', and Jentic returns the matching RangeFlow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using RangeFlow API through Jentic.

What authentication does the RangeFlow API use?

The RangeFlow API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a workflow with the RangeFlow API?

Yes. Use the POST /workflows endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RangeFlow API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a workflow through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a workflow'. Jentic returns the matching RangeFlow API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RangeFlow API have?

The RangeFlow API exposes 3 endpoints covering executions, workflows operations.

Can I limit what my agent is allowed to do with the RangeFlow API?

Yes. Because the RangeFlow API identifies workflows and executions in the request body rather than the URL path, Jentic One scopes access at the operation level: you grant your agent only the operations it needs, such as listing workflows or creating an execution. Since Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use, and any operation you leave out is not available to it.