Install Jentic One Beta

Connect the Core API to your agent

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

Filter a form's submissions page by page with a SimpleFilter query, sort, and pageSize

Download files attached to a submission and resend its submission emails

Schedule an export of a form's submissions and list which fields can be exported

Assign a form task to recipients with a message, prefilled data, and publishInfo, then complete or revoke it

Invite users, add them to groups, and change their access through role grants

GET STARTED

Start building with Core API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Core API for, with concrete tasks.

★ AI operations agent that reads field submissions

An operations agent needs the latest inspection or work order submissions without a developer wiring the X-Api-Key header and paging logic by hand. Through Jentic the agent searches for 'list MoreApp form submissions', loads the submissions filter operation with its input schema, and posts a SimpleFilter for the date range. Your own Jentic One instance attaches the key at call time, and the agent summarises what the field team reported.

Call POST /api/v1.0/customers/{customerId}/forms/{formId}/submissions/filter/{page} with page 0 and a SimpleFilter of pageSize 50 sorted by date, then summarise any submissions that flag a defect

Dispatching form tasks to field staff

Service companies send technicians a specific form to complete at a job site. The task operation assigns a form to recipients with a message, prefilled data such as the job address, and publishInfo for when it appears, and the task can later be completed or revoked. Listing tasks per form shows which assignments are still open.

Call POST /api/v1.0/customers/{customerId}/{formId}/tasks with recipients, a message, data containing the job address, and publishInfo, then confirm it appears in the task list filter

Exporting submissions for reporting

Teams that report on form data outside MoreApp can list the exportable fields for a form and schedule an export of its submissions. Individual submissions and their attached files, such as photos or signatures, can also be fetched for audit.

Call GET /api/v1.0/customers/{customerId}/forms/{formId}/submissions/export/fields, then POST /api/v1.0/customers/{customerId}/forms/{formId}/submissions/export to schedule an export

Onboarding a new field user

When a technician joins, an admin invites them by emailAddress, adds the invite to the right group, and grants access to the forms that group uses. Groups, roles, and grants can be listed and adjusted later as people move between teams.

Call POST /api/v2/customers/{customerId}/invites with emailAddress and language, then POST /api/v2/customers/{customerId}/invites/{inviteId}/groups/{groupId} to add the invite to the inspectors group

Key Endpoints

48 endpoints — the moreapp core api reads and manages the form submissions, tasks, and account setup behind moreapp mobile forms.

METHOD

PATH

DESCRIPTION

POST

/api/v1.0/customers/{customerId}/forms/{formId}/submissions/filter/{page}

List all submissions

GET

/api/v1.0/customers/{customerId}/submissions/{submissionId}

Get a single submission

GET

/api/v1.0/customers/{customerId}/registrationFile/{fileId}/download

Download submission file

POST

/api/v1.0/customers/{customerId}/forms/{formId}/submissions/export

Schedule an export

POST

/api/v1.0/customers/{customerId}/{formId}/tasks

Create a task

POST

/api/v2/customers/{customerId}/invites

Invite user

GET

/api/v1.0/customers/{customerId}/datasources

List all datasources

POST

/api/v1.0/customers/{customerId}/forms/{formId}/submissions/filter/{page}

List all submissions

GET

/api/v1.0/customers/{customerId}/submissions/{submissionId}

Get a single submission

GET

/api/v1.0/customers/{customerId}/registrationFile/{fileId}/download

Download submission file

POST

/api/v1.0/customers/{customerId}/forms/{formId}/submissions/export

Schedule an export

POST

/api/v1.0/customers/{customerId}/{formId}/tasks

Create a task

POST

/api/v2/customers/{customerId}/invites

Invite user

GET

/api/v1.0/customers/{customerId}/datasources

List all datasources

Why Jentic?

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

Setup

Wiring MoreApp by hand means sending the X-Api-Key header, threading the customerId and formId through every path, and paging submissions with SimpleFilter bodies. Through Jentic you install once, import MoreApp from the API Directory, store the key once, and your agent calls it.

Permission scoping

MoreApp puts the customerId and formId in the URL path, as in /api/v1.0/customers/{customerId}/forms/{formId}/submissions, so a rule can hold your agent to one form and the operations you pick. You choose the operations it may call, so destructive ones like deleting a submission or removing a user are not included unless you add them.

Credential isolation

Your MoreApp 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 form submissions' or 'invite a user to MoreApp', and Jentic returns the matching MoreApp operation with its input schema, including the customerId, formId, and filter body.

FAQs

Specific to using Core API through Jentic.

What authentication does the MoreApp Core API use?

Per its OpenAPI spec, the MoreApp Core API uses an API key sent in the X-Api-Key request header, applied to all 48 operations. Through Jentic the key is stored by your own Jentic One instance and attached at call time, so the agent never handles it.

Can I download photos and files from submissions with the MoreApp Core API?

Yes. GET /api/v1.0/customers/{customerId}/registrationFile/{fileId}/download returns a file attached to a submission, and GET /api/v1.0/customers/{customerId}/submissions/{submissionId} returns the submission itself so you can find its file ids.

What are the rate limits for the MoreApp Core API?

The OpenAPI spec does not specify rate limits. Check the MoreApp developer documentation at https://docs.moreapp.com for current limits.

Is there a MoreApp MCP server?

You don't need an MCP server to give your agent MoreApp. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the submission, task, and user operations on demand without another server's tool definitions in its context.

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

Yes. Write a rule that allows only the submissions filter and single-submission read operations under one formId, and a reporting agent can read that form's results without deleting submissions, revoking invites, or changing roles. Every call it makes is logged.

How do I assign a form task through Jentic?

Search Jentic for 'assign a MoreApp form to a user', load the POST /api/v1.0/customers/{customerId}/{formId}/tasks operation, and execute it with recipients, message, data, and publishInfo, which the spec marks as required. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Moreapp Core API

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityForms SurveysapiKey48 EndpointsREST

For Agents

List and export MoreApp form submissions, download their files, assign form tasks to field users, and manage users, groups, roles, and datasources for a MoreApp account.

Use for: List all submissions for an inspection form from this week, Download the photo attached to a form submission, I need to assign a checklist form to a field technician, Schedule an export of all submissions for a form

Not supported: Does not design or publish form layouts, take payments, or send SMS. Use for MoreApp submissions, tasks, datasources, and account users only.

The MoreApp Core API reads and manages the form submissions, tasks, and account setup behind MoreApp mobile forms. It lists and filters submissions per form, fetches a single submission and its uploaded files, resends submission emails, and schedules exports of a form's submissions. Tasks assign a form to recipients with a message, prefilled data, and a publish date, and can be completed or revoked. Account operations cover users, invites, groups, roles, and grants, along with datasources that feed lookup lists into forms from a URL or Google configuration.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

69%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

99%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

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

Example Density

How richly the API is illustrated with examples.

75%

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

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

81%

OperationId Quality

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

59%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Core API to your agent

Capabilities

Start building with Core API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Moreapp Core API

Jentic AI Readiness Score

Core 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