Install Jentic One Beta

Connect the Intake Public API to your agent

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

Get all Forms

Submit a Form

File Upload Endpoint for File Attachment Fields

Values for Financial Info Field

Monitor Intake Public API operational status and events

GET STARTED

Start building with Intake Public API

Explore with Jentic One

View OpenAPI Document

Automated Mod1 Management

Automate mod1 operations by combining multiple Intake Public API endpoints. Agents can get a form by its id and then submit a form in a single workflow.

Call GET /api/mod1/public/form/{id} to get a form by its id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Intake Public 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 'get all forms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — api documentation for public lexopulus intake apis.

METHOD

PATH

DESCRIPTION

GET

/api/mod1/public/form

Get all Forms

GET

/api/mod1/public/form/{id}

Get a Form by its ID

POST

/api/mod1/public/form/{id}/submit

Submit a Form

POST

/api/mod1/public/file

File Upload Endpoint for File Attachment Fields

GET

/api/mod1/public/location

Get List of Countries & States to be used in Address Field

GET

/api/mod1/public/financial-info

Values for Financial Info Field

GET

/api/mod1/public/form

Get all Forms

GET

/api/mod1/public/form/{id}

Get a Form by its ID

POST

/api/mod1/public/form/{id}/submit

Submit a Form

POST

/api/mod1/public/file

File Upload Endpoint for File Attachment Fields

GET

/api/mod1/public/location

Get List of Countries & States to be used in Address Field

GET

/api/mod1/public/financial-info

Values for Financial Info Field

Why Jentic?

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

Setup

Wiring the Intake Public API by hand means attaching its API key, moving between form, file, location, and financial-info endpoints, and handling multi-step form submission yourself. Through Jentic you install once, import the Intake Public API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Intake Public API puts the form id in the URL path (/form/{id}), so a rule can pin your agent to one form: it can read that form and submit to it if you allow it. You choose the operations it may call, so nothing beyond the ones you list runs.

Credential isolation

Your Intake Public 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 'list all forms' or 'submit a form', and Jentic returns the matching Intake Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Intake Public API through Jentic.

What authentication does the Intake Public API use?

The Intake Public API uses an API key passed in the `x-api-key` 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 get all forms with the Intake Public API?

Yes. Use the GET /api/mod1/public/form endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Intake Public 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 all forms through Jentic?

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

How many endpoints does the Intake Public API have?

The Intake Public API exposes 6 endpoints covering mod1 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the six Intake Public API operations your agent may call and which credentials it may use. Since the form id sits in the URL path (/api/mod1/public/form/{id}), a rule can pin the agent to a single form so it only reads that form and submits to it. Anything you do not list, such as file upload, location lookups, or financial-info values, never runs.

Us App Lexopulus Intake Public API

AI ReadinessNon-Ready (F)39/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey6 EndpointsREST

For Agents

Programmatically get all forms, get a form by its id. Covers 6 operations with apiKey authentication.

Use for: I need to all forms, I want to a form by its id, Search for submit a form, Find all file upload endpoint for file attachment fields

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

API Documentation for Public Lexopulus Intake APIs. The API exposes 6 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 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).

17%

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

12%

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.

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

50%

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 Intake Public API to your agent

Capabilities

Start building with Intake Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Us App Lexopulus Intake Public API

Jentic AI Readiness Score

Intake Public 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