canonical: https://jentic.com/apis/us-app.lexopulus.com/us-app-lexopulus

# Us App Lexopulus Intake Public API

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

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

### Developer Tools Operations

Use the Intake Public API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including get all forms, get a form by its id, submit a form.

Example prompt: Call GET `/api/mod1/public/form` to get all forms

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

Example prompt: 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.

Example prompt: Search Jentic for 'get all forms', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Mod1** — Operations for mod1

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 79 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 16 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/us-app.lexopulus.com/us-app-lexopulus/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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