Install Jentic One Beta

Connect the BioFlow API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BioFlow 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%2Fgetbioflow.com%2Fgetbioflow" | 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%2Fgetbioflow.com%2Fgetbioflow" | 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 BioFlow API.

Create a page, add content blocks to it, and publish it

Update a page draft and remove individual blocks

List the contacts and files captured through the pages

Read an analytics summary over a chosen number of days

GET STARTED

Start building with BioFlow API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BioFlow API for, with concrete tasks.

★ Agent-Built Bio Pages

An AI agent that assembles a link-in-bio or landing page can call the BioFlow API through Jentic to create the page, add a block for each link or section, and publish it. The agent builds and ships the page without the developer wiring the bearer or x-api-key auth or the page and block paths by hand. Jentic returns the matching operation and its input schema so the agent edits the page inline.

Create a page, add a block for each supplied link, and publish the page once all blocks are added

Contact and Analytics Reporting

A dashboard can report how pages are performing by pulling the contacts they captured and an analytics summary for a chosen window. BioFlow lists captured contacts with cursor paging and returns an analytics summary over a set number of days, so a workflow can show leads collected and traffic trends together.

Pull the analytics summary for the last 30 days and list the contacts captured in that window

Webhook Delivery Management

A service that reacts to page events can register a webhook endpoint, confirm it with a test event, and recover from outages by replaying or resending failed deliveries. BioFlow manages webhook endpoints, lists their deliveries filtered by status, resends a single delivery, replays all failed ones, and rotates the signing secret.

Key Endpoints

22 endpoints — the bioflow api builds and publishes link-in-bio style pages made of content blocks.

METHOD

PATH

DESCRIPTION

POST

/v1/pages

Create a page

POST

/v1/pages/{page_id}/blocks

Add a block to a page

POST

/v1/pages/{page_id}/publish

Publish a page

GET

/v1/contacts

List captured contacts

GET

/v1/analytics/summary

Get an analytics summary

POST

/v1/webhook-endpoints

Create a webhook endpoint

POST

/v1/webhook-endpoints/{endpoint_id}/replay

Replay failed deliveries

POST

/v1/pages

Create a page

POST

/v1/pages/{page_id}/blocks

Add a block to a page

POST

/v1/pages/{page_id}/publish

Publish a page

GET

/v1/contacts

List captured contacts

GET

/v1/analytics/summary

Get an analytics summary

POST

/v1/webhook-endpoints

Create a webhook endpoint

POST

/v1/webhook-endpoints/{endpoint_id}/replay

Replay failed deliveries

Why Jentic?

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

Setup

Wiring BioFlow by hand means supplying its API key as a bearer token or x-api-key header, threading page and block ids through each path, and handling RFC 9457 problem details on errors. Through Jentic you install once, import BioFlow from the API Directory, store the key once, and your agent calls it.

Permission scoping

BioFlow puts the page id and webhook endpoint id in the URL path, so a rule can pin your agent to one page or one endpoint and the operations you pick. You choose which operations it may call, so page deletion and secret rotation are not included unless you add them.

Credential isolation

Your BioFlow 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 page' or 'replay failed webhook deliveries', and Jentic returns the matching BioFlow operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using BioFlow API through Jentic.

What authentication does the BioFlow API use?

The BioFlow API authenticates with an API key, supplied either as a bearer token in the Authorization header or in the x-api-key header, per its OpenAPI spec. Through Jentic the key is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Is there a BioFlow MCP server?

You don't need an MCP server to give your agent the BioFlow API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can build and publish pages straight away.

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

Yes. BioFlow puts the page id and the webhook endpoint id in the URL path, so a rule can bound your agent to one page or one endpoint and the operations you pick. Allow it to create pages and add blocks but leave page deletion and secret rotation out unless you add them, and every call it makes is logged.

Can I publish a page with the BioFlow API?

Yes. An agent creates a page, adds a content block for each section, and then calls the publish operation to make the page live, updating the draft with further edits before publishing again if needed.

What are the rate limits for the BioFlow API?

The OpenAPI spec exposes a usage operation that reports your current API usage but does not publish a fixed numeric ceiling. Check the BioFlow documentation for the current limits on your plan.

How do I create and publish a page with the BioFlow API through Jentic?

Search Jentic for an intent like 'create and publish a page' and it returns the BioFlow page operations with their input schemas, so your agent creates the page, adds blocks, and publishes it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getbioflow BioFlow API

AI ReadinessAI-Ready (A-)79/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementbearer, apiKey22 EndpointsREST

For Agents

Build link-in-bio style pages from blocks and publish them, list captured contacts and files, read an analytics summary, and manage webhook endpoints with delivery replay. Authenticates with an API key as a bearer token or in the x-api-key header.

Use for: Create a new page and publish it, Add a content block to a page, List the contacts captured on my pages, Get an analytics summary for a chosen date range

Not supported: Does not handle payments, email sending, or domain hosting. Use for building and publishing bio pages and managing their webhooks only.

The BioFlow API builds and publishes link-in-bio style pages made of content blocks. An agent creates a page, adds and removes blocks, updates the draft, and publishes it, then lists the contacts and files the pages have captured and reads an analytics summary over a chosen number of days. It also manages webhook endpoints end to end, listing deliveries, resending or replaying failed ones, sending a test event, and rotating the signing secret. Responses are JSON with RFC 9457 problem details on errors, and authentication is an API key sent as a bearer token or in the x-api-key header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

16%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: A-Signals: 4

54%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

90%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BioFlow API to your agent

Capabilities

Start building with BioFlow API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getbioflow BioFlow API

Jentic AI Readiness Score

BioFlow API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness