Install Jentic One Beta

Connect the Realeflow API to your agent

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

Get account status

Create a contact

List contacts

Access Realeflow API crm resources via REST API

Use Cases

Patterns agents use Realeflow API for, with concrete tasks.

GET STARTED

Start building with Realeflow API

Explore with Jentic One

View OpenAPI Document

Automated Account Management

Automate account operations by combining multiple Realeflow API endpoints. Agents can create a contact and then list contacts in a single workflow.

Call POST /contact/create to create a contact, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Realeflow 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 basic tokens manually.

Search Jentic for 'get account status', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — realeflow crm api for managing contacts, properties, and contact-property relationships in the real estate investment platform.

METHOD

PATH

DESCRIPTION

GET

/account/status

Get account status

POST

/contact/create

Create a contact

GET

/contact/list

List contacts

POST

/contact/propertyrelation

Create contact-property relation

POST

/property/create

Create a property

GET

/property/list

List properties

GET

/account/status

Get account status

POST

/contact/create

Create a contact

GET

/contact/list

List contacts

POST

/contact/propertyrelation

Create contact-property relation

POST

/property/create

Create a property

GET

/property/list

List properties

Why Jentic?

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

Setup

Wiring the Realeflow API by hand means encoding your key as HTTP basic auth, coordinating the contact and property create and list calls, and relating contacts to properties yourself. Through Jentic you install once, import the Realeflow API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Realeflow API creates contacts and properties through collection endpoints with data in the request body, so you limit the agent to the operations it needs, such as listing contacts or checking account status. It only calls the operations you allow, so creating a contact or property is out of scope unless you add it.

Credential isolation

Your Realeflow API basic credential 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 'get account status' or 'list contacts', and Jentic returns the matching Realeflow API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Realeflow API through Jentic.

What authentication does the Realeflow API use?

The Realeflow API uses HTTP Basic authentication. 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 get account status with the Realeflow API?

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

What are the rate limits for the Realeflow 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 get account status through Jentic?

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

How many endpoints does the Realeflow API have?

The Realeflow API exposes 6 endpoints covering account, contacts, properties operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Realeflow operations the agent may call and which credential it uses. You can allow read-only operations such as GET /account/status, GET /contact/list, and GET /property/list while withholding the write operations. That means POST /contact/create, POST /property/create, and POST /contact/propertyrelation stay out of scope unless you explicitly grant them.

Realeflow API

Name: Realeflow API
Brand: Realeflow API
Availability: InStock

AI ReadinessNon-Ready (F)40/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbasic6 EndpointsREST

For Agents

Programmatically get account status, create a contact. Covers 6 operations with basic authentication.

Use for: I need to account status, I want to a contact, Search for contacts, Find all contact-property relation

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Realeflow CRM API for managing contacts, properties, and contact-property relationships in the real estate investment platform. The API exposes 6 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: DSignals: 4

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

50%

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: FSignals: 1

10%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Realeflow API to your agent

Capabilities

Use Cases

Start building with Realeflow API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Realeflow API

Jentic AI Readiness Score

Realeflow 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