Install Jentic One Beta

Connect the InsiderCX ARC API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the InsiderCX ARC 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%2Fswaggerhub.accounts-20%2Finsidercx-arc-api" | 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%2Fswaggerhub.accounts-20%2Finsidercx-arc-api" | 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 InsiderCX ARC API.

Create ARC object

Load ARC objects

Find ARC object by ID

Update ARC object

Delete ARC Object

GET STARTED

Start building with InsiderCX ARC API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use InsiderCX ARC API for, with concrete tasks.

★ Developer Tools Operations

Use the InsiderCX ARC API to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including create arc object, load arc objects, find arc object by id.

Call POST /data/ARC to create arc object

Automated ARC Management

Automate arc operations by combining multiple InsiderCX ARC API endpoints. Agents can load arc objects and then find arc object by id in a single workflow.

Call GET /data/ARC to load arc objects, then verify the result

AI Agent Integration via Jentic

AI agents discover and call InsiderCX ARC 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 arc object', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — insidercx arc api provides programmatic access to developer tools functionality.

METHOD

PATH

DESCRIPTION

POST

/data/ARC

Create ARC object

GET

/data/ARC

Load ARC objects

GET

/data/ARC/{objectId}

Find ARC object by ID

PUT

/data/ARC/{objectId}

Update ARC object

DELETE

/data/ARC/{objectId}

Delete ARC Object

POST

/data/bulk/ARC

Bulk Create ARC objects

POST

/users/login

User Login

POST

/data/ARC

Create ARC object

GET

/data/ARC

Load ARC objects

GET

/data/ARC/{objectId}

Find ARC object by ID

PUT

/data/ARC/{objectId}

Update ARC object

DELETE

/data/ARC/{objectId}

Delete ARC Object

POST

/data/bulk/ARC

Bulk Create ARC objects

POST

/users/login

User Login

Why Jentic?

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

Setup

Wiring the InsiderCX ARC API by hand means logging in through /users/login, sending its user-token header on every call to apis.insidercx.com, and managing single and bulk ARC object writes yourself. Through Jentic you install once, import the InsiderCX ARC API from the API Directory, store the user-token once, and your agent calls it.

Permission scoping

The ARC API puts the object id in the URL path (/data/ARC/{objectId}), so a rule can pin your agent to one ARC object for read and update. You choose the operations it may call, so destructive ones like deleting an object or running bulk writes are not included unless you add them.

Credential isolation

Your InsiderCX ARC user-token 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 an ARC object' or 'look up an ARC record by id', and Jentic returns the matching InsiderCX ARC 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 InsiderCX ARC API through Jentic.

What authentication does the InsiderCX ARC API use?

The InsiderCX ARC API uses an API key passed in the `user-token` 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 arc object with the InsiderCX ARC API?

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

What are the rate limits for the InsiderCX ARC 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 arc object through Jentic?

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

How many endpoints does the InsiderCX ARC API have?

The InsiderCX ARC API exposes 7 endpoints covering arc, userservice operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which InsiderCX ARC operations the agent may call and which user-token it uses. You can allow read and update on a single object by pinning the /data/ARC/{objectId} path to one ARC object, and withhold destructive operations like DELETE /data/ARC/{objectId} or the POST /data/bulk/ARC bulk write unless you explicitly add them. The stored user-token is injected only for the operations you permit.

Accounts 20 InsiderCX ARC API

Name: InsiderCX ARC API
Brand: InsiderCX ARC API
Availability: InStock

Browse all Swaggerhub Accounts 20 APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create arc object, load arc objects. Covers 7 operations with apiKey authentication.

Use for: I need to arc object, I want to load arc objects, Search for arc object by id, Find all arc object

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

InsiderCX ARC API provides programmatic access to developer tools functionality. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document