Install Jentic One Beta

Connect the CapitalFlow Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CapitalFlow Public 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%2Fcapital-flow.de%2Fcapital-flow" | 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%2Fcapital-flow.de%2Fcapital-flow" | 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 CapitalFlow Public API.

Retrieve a customer record by its identifier

Create a new customer

Update an existing customer's details

Share a customer intake form with a specific customer

Share a cashflow form with a specific customer

GET STARTED

Start building with CapitalFlow Public API

Explore with Jentic One

View OpenAPI Document

★ Agent-Managed Customer Onboarding

An AI agent onboards a new client by creating their customer record and then sharing the intake and cashflow forms addressed to that customer. Because the form-sharing operations take a customer identifier in the path, the agent can create the record and immediately dispatch the correct forms in one flow. This removes the manual dashboard steps from getting a client set up.

Create a customer record from a lead's details, then share the intake form and the cashflow form addressed to that customer

Customer Record Sync

Teams keep CapitalFlow customer records aligned with an external CRM by reading a customer by identifier and updating changed fields. The API exposes read, create, and update operations on customers so an integration can reconcile both systems. This suits recurring syncs where contact details change in one place and must propagate.

Read a customer by identifier, compare fields with the source CRM, and update the CapitalFlow record where they differ

Form Distribution to Clients

An agent sends the right form to each client by calling the share-form operations with the customer's identifier. Intake forms and cashflow forms are dispatched per customer, so a batch of clients each receives the form they need. This turns a repetitive send-the-form task into an automated step keyed off the customer list.

For each customer in a list, share the appropriate intake or cashflow form addressed to that customer identifier

Key Endpoints

5 endpoints — the capitalflow public api creates, reads, and updates customer records and shares intake and cashflow forms with specific customers.

METHOD

PATH

DESCRIPTION

GET

/integrations/v1/customers/{customerId}

Retrieve a customer by identifier

POST

/integrations/v1/customers

Create a customer

PUT

/integrations/v1/customers

Update a customer

PUT

/integrations/v1/forms/customer/{customerId}/share-form

Share an intake form with a customer

PUT

/integrations/v1/forms/cashflow/customer/{customerId}/share-form

Share a cashflow form with a customer

GET

/integrations/v1/customers/{customerId}

Retrieve a customer by identifier

POST

/integrations/v1/customers

Create a customer

PUT

/integrations/v1/customers

Update a customer

PUT

/integrations/v1/forms/customer/{customerId}/share-form

Share an intake form with a customer

PUT

/integrations/v1/forms/cashflow/customer/{customerId}/share-form

Share a cashflow form with a customer

Why Jentic?

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

Setup

Wiring the CapitalFlow Public API by hand means provisioning a key, learning the customer record shape, and building the path-keyed form-sharing calls yourself. Through Jentic you install once, import CapitalFlow from the API Directory, store the key once, and your agent creates records and shares forms.

Permission scoping

CapitalFlow puts the customer identifier in the URL path, so a rule can bound your agent to a single customer. You can also scope by operation, allowing reads while withholding the create and update operations, and every call the agent makes is logged.

Credential isolation

Your CapitalFlow 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 customer' or 'share a cashflow form', and Jentic returns the matching CapitalFlow operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using CapitalFlow Public API through Jentic.

What authentication does the CapitalFlow Public API use?

The CapitalFlow Public API authenticates with an API key sent in the cf-api-key request header per its OpenAPI spec. Through Jentic the key is held encrypted by your own Jentic One instance and attached at call time, so it never reaches the agent's context.

Can I share forms with a specific customer through the CapitalFlow Public API?

Yes. The share-form operations take a customer identifier in the path, so an agent can dispatch an intake form or a cashflow form addressed to one customer. The customer record can be created first in the same flow.

What are the rate limits for the CapitalFlow Public API?

The OpenAPI spec does not specify rate limits. Check the CapitalFlow documentation at https://www.capital-flow.de for current limits and usage guidance.

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

Yes. Because the customer identifier sits in the URL path, a rule can bound your agent to one customer, and you can also scope by operation to allow reads while withholding creates and updates. You choose which operations it may call, and every call is logged.

How do I onboard a CapitalFlow customer through Jentic?

Search Jentic for 'create a customer' or 'share a form', add the CapitalFlow Public API from the directory, and store your key once. Your agent then creates the record and shares the forms addressed to that customer. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a CapitalFlow MCP server?

You don't need an MCP server to give your agent the CapitalFlow Public API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent creates customers and shares forms. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

Capital Flow De CapitalFlow Public API

Name: CapitalFlow Public API
Brand: CapitalFlow Public API
Availability: InStock

Community OpenAPI document · agent-readyCRMContact ManagementapiKey5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create, read, and update CapitalFlow customer records, and share intake or cashflow forms with a specific customer. Returns customer records for an agent to keep in sync.

Use for: Look up a CapitalFlow customer by identifier, Create a new customer in CapitalFlow, Update a customer's contact details, Send a customer intake form to a client

Not supported: Does not handle payments, accounting ledgers, or document storage. Use for customer record management and form sharing only.

The CapitalFlow Public API creates, reads, and updates customer records and shares intake and cashflow forms with specific customers. Each customer is addressed by an identifier in the URL path, and form-sharing operations target that customer directly. Agents can onboard and maintain customer records and dispatch the right form to each client without working inside the CapitalFlow dashboard.

Jentic One on Github View OpenAPI Document

Connect the CapitalFlow Public API to your agent

Capabilities

Start building with CapitalFlow Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Capital Flow De CapitalFlow Public API