Mighty Office Mighty API
57
AI ReadinessFoundational (C+)57/100
Community OpenAPI document · agent-readyProductivityForms Surveysbearer9 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read form fields, read and create form answers, export report output as JSON, and upload files or attachments to Mighty-Office objects. Built for non-human clients of Mighty-Office.
Use for: Read the fields of a form, Create a new form answer, Retrieve a single form answer, Export a report as JSON
Not supported: Does not design forms, manage user accounts, or send notifications. Use for reading form fields, reading and creating form answers, exporting reports, and uploading files only.
The Mighty API gives non-human clients programmatic access to Mighty-Office features. It reads a form's fields including its subform fields, reads a single form answer with its subform answers, and creates new form answers against a form. It also exports a report's output as JSON, uploads a staging CSV file or attaches an image or document to an object, and fetches raw images and documents by token.
Install Jentic One Beta
Connect the Mighty API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mighty 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.
1
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%2Fmighty-office.com%2Fmighty-office" | sh2
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%2Fmighty-office.com%2Fmighty-office" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Mighty API.
Read a form's fields, including its subform fields
Read a single form answer with its subform answers
Create a form answer against a form
Export a report's output as JSON
Upload a staging CSV file or attach an image or document to an object
Fetch a raw image or document by its token
Use Cases
Patterns agents use Mighty API for, with concrete tasks.
★ Agent form submission
An AI agent collecting structured input reads a form's fields to learn what is required, then creates a form answer with the values it gathered. The Mighty API returns the field definitions, including subform fields, and accepts a new form answer against the form, so the agent can fill and submit a form end to end. Through Jentic the operations are discovered by intent and the token is injected at call time.
Read a form's fields, then create a form answer that supplies a value for each required field
Report export to JSON
Teams need a report's data in a machine-readable shape for downstream processing. The Mighty API exports a report's output as JSON by report id, so an agent can pull a report and hand its rows to another system without scraping a rendered page.
Export a report's output as JSON for a given report id and pass the rows to a downstream step
File and attachment upload
Workflows often attach supporting files to a record. The Mighty API uploads a staging CSV file and attaches an image or document to an object, and lets a client fetch raw images or documents back by token, so an agent can push a file into Mighty-Office and retrieve it later.
Attach a document to an object and then fetch the raw file back by its token to confirm the upload
Key Endpoints
9 endpoints — the mighty api gives non-human clients programmatic access to mighty-office features.
METHOD
PATH
DESCRIPTION
POST
/de/api/user/login
Log in and obtain a token
GET
/de/api/form/getfields/{formId}/{includeSubformFields}
Get a form's fields
GET
/de/api/formanswer/read/{formId}/{formanswerId}/{includeSubformAnswers}
Read a single form answer
POST
/de/api/formanswer/create/{formId}
Create a form answer
GET
/de/reportexport/json/{reportId}
Export a report's output as JSON
POST
/de/api/file/upload
Upload a staging CSV file
POST
/de/api/user/login
Log in and obtain a token
GET
/de/api/form/getfields/{formId}/{includeSubformFields}
Get a form's fields
GET
/de/api/formanswer/read/{formId}/{formanswerId}/{includeSubformAnswers}
Read a single form answer
POST
/de/api/formanswer/create/{formId}
Create a form answer
GET
/de/reportexport/json/{reportId}
Export a report's output as JSON
POST
/de/api/file/upload
Upload a staging CSV file
Jentic AI Readiness Score
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.
M
Mighty API
- Foundational (C+)57/100
73
Foundational Compliance66
Developer Experience & Jentic Compatibility36
AI-Readiness & Agent Experience94
Agent Usability75
Security46
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
66
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
20%
Example Density
How richly the API is illustrated with examples.
95%
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.
36
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
56%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
46
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: DSignals: 1
46%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Mighty API by hand means calling the login operation to mint a JWT, sending it as a bearer token on later calls, and handling the form-id path structure and file uploads yourself. Through Jentic you install once, import it from the API Directory, store the login credential once, and your agent calls it.
Permission scoping
Mighty puts the form id in the URL path, so a rule can pin your agent to the operations and forms you pick: it can read fields and create answers for one form. You choose the operation set, so the file-upload operations are not included unless you add them.
Credential isolation
Your Mighty login credential is stored once, encrypted, by your own Jentic One instance and the token is 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 a form answer' or 'export a report', and Jentic returns the matching Mighty 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.
FAQs
Specific to using Mighty API through Jentic.
What authentication does the Mighty API use?
The Mighty API uses a JWT bearer token, per its OpenAPI spec: a login operation returns the token, which later calls send in the Authorization header. Through Jentic the credential is stored once and the token is injected at call time, so it never enters the agent's prompt, logs, or context.
Can I create form answers with the Mighty API?
Yes. A create operation accepts a new form answer against a specific form id, and a read operation returns a single answer with its subform answers. An agent can read the form's fields first to learn what is required, then submit a complete answer.
What are the rate limits for the Mighty API?
The OpenAPI spec does not define numeric rate limits. Have your agent back off when it receives an HTTP 429 response, and contact Mighty-Office for the limits that apply to your account.
Is there a Mighty Office MCP server?
You don't need an MCP server to give your agent the Mighty API. Jentic connects it directly from the API Directory: import it, store your login credential once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.
Can I limit what my agent is allowed to do with the Mighty API?
Yes. Mighty puts the form id in the URL path, such as the form-fields and form-answer operations, so a rule can pin your agent to the operations and forms you pick, letting it read fields and create answers without the file-upload operations unless you add them. Every call it makes is logged.
How do I submit a form answer through Jentic?
Search Jentic for an intent such as 'create a new form answer' and it returns the matching create operation with its input schema, so your agent reads the form fields, assembles the values, and submits the answer. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED