Install Jentic One Beta

Connect the Inistate API to your agent

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

List reachable workspaces and read a workspace's detail

Discover the modules available in a workspace

List and filter the entries held in a module

Create a new entry in a module

Update an existing entry by id

GET STARTED

Start building with Inistate API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Inistate API for, with concrete tasks.

★ Agent-Driven Record Updates

An AI agent connected through Jentic lists the entries in a module, finds the one it needs with a filter, and updates it by id. Because entries, modules, and workspaces are addressed consistently, the agent reads and writes Inistate business records without a per-module integration.

List entries in a module, filter to the matching record, and update its fields by entry id

Workflow Activity Automation

Operations teams advance records through a process by running activities. Inistate exposes an activity-form operation that returns a form definition and initial payload and an activity operation that performs the action, so an agent fetches the form, fills it, and runs the step on the right entry.

Fetch the activity form for an entry, build the payload, and perform the activity to advance its workflow

Module Discovery and Reporting

Reporting tools map what a workspace contains before pulling data. Inistate's discovery operations list the modules in a workspace and their canvas payloads, so an agent learns the available modules and then lists each module's entries for a report.

Discover the modules in a workspace, then list the entries in a chosen module for a summary report

Key Endpoints

13 endpoints — the inistate api reads and writes the business records that live on the inistate low-code platform, organized as entries inside modules inside workspaces.

METHOD

PATH

DESCRIPTION

GET

/api/workspace

List reachable workspaces

GET

/api/workspace/{workspaceId}

Get a workspace's detail

POST

/api/m/list

List entries with filters

POST

/api/m

Create a new entry

PUT

/api/m/{entryId}

Update an existing entry

POST

/api/m/activity

Perform an activity on an entry

POST

/api/m/history

Get an entry's activity history

GET

/api/workspace

List reachable workspaces

GET

/api/workspace/{workspaceId}

Get a workspace's detail

POST

/api/m/list

List entries with filters

POST

/api/m

Create a new entry

PUT

/api/m/{entryId}

Update an existing entry

POST

/api/m/activity

Perform an activity on an entry

POST

/api/m/history

Get an entry's activity history

Why Jentic?

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

Setup

Wiring Inistate by hand means choosing between its `Authorization` API key and its OAuth 2.0 password flow, then learning the workspace, module, and entry shape before you can read a record. Through Jentic you install once, import Inistate from the API Directory, store the credential once, and your agent calls the entry and activity operations.

Permission scoping

Inistate carries read operations for workspaces, modules, and entries alongside write operations that create entries, update them, and run activities. You choose the operations your agent may call, so a rule can keep it to listing and reading entries and leave entry creation, updates, or activities out unless you add them.

Credential isolation

Your Inistate API key or OAuth token is held by your own Jentic One instance, encrypted, 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 'list entries in a module' or 'run an activity on an entry', and Jentic returns the matching Inistate operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Inistate API through Jentic.

What authentication does the Inistate API use?

The spec declares two options: an API key sent in the `Authorization` header in the form `fsk {your api key}`, and an OAuth 2.0 password-flow token from the `/token` endpoint. Through Jentic the credential you choose is held by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.

Can I create and update records with the Inistate API?

Yes. You create an entry in a module, update an existing entry by its id, and list entries with filters. Because entries live inside modules inside workspaces, your agent reads and writes business records across the platform through one consistent shape.

What are the rate limits for the Inistate API?

The OpenAPI spec does not specify rate limits. Check the Inistate community documentation at https://community.inistate.com for current limits before running bulk entry imports or updates.

Is there an Inistate MCP server?

You do not need an MCP server to give your agent the Inistate API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the workspace, entry, and activity operations on demand without loading an extra server's tool definitions into its context.

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

Yes. Write a rule that allows only the workspace and entry list operations, so the agent can read records across your modules and cannot create entries, update them, or run activities on them. You choose which operations it may call, and every call it makes is logged.

How do I update a record through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Inistate API from the Jentic directory and search by intent such as 'update an entry in a module'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Inistate API

AI ReadinessFoundational (D-)41/100

See full scorecard

Community OpenAPI document · agent-readyStorageDatabaseapiKey, oauth213 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List Inistate workspaces and modules, list and filter entries, create and update entries, run activities on them, and read an entry's history through the Inistate low-code platform API.

Use for: List all workspaces I can access in Inistate, Discover the modules available in a workspace, Find entries in a module that match a filter, Create a new entry in a module

Not supported: Does not host websites, send email campaigns, or process payments. Use for reading and writing Inistate workspaces, modules, and entries only.

The Inistate API reads and writes the business records that live on the Inistate low-code platform, organized as entries inside modules inside workspaces. An agent lists the workspaces it can reach, discovers the modules available in a workspace, and then lists, creates, and updates the entries each module holds. Activities drive the workflow on an entry, and a history operation returns the actions that have been performed on it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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).

50%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

36%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

39%

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: D-Signals: 1

40%

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: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Inistate API to your agent

Capabilities

Start building with Inistate API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Inistate API

Jentic AI Readiness Score

Inistate API Documentation

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