For Agents
Create and publish forms, list and retrieve responses, and register webhooks for new submissions. Draft, validate, and publish forms through a dedicated agent endpoint set, and bootstrap an account and API key in one call.
Use for: I want to create a form and publish it immediately, Create an account and API key without opening a browser, List the latest responses for a form, Download a file attached to a form response
Not supported: Does not send email campaigns, process payments, or build landing pages. Use for creating forms, collecting responses, and managing response webhooks only.
The FormBuilder API creates, publishes, and reads forms, and can bootstrap an account and API key in a single signup call so no browser is needed. It lists form responses, downloads attachment files, and registers webhooks for new responses, and it offers an agent-oriented endpoint set for drafting, validating, and publishing forms with a safety review. Responses can be queried for only the records a token is authorized to read.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FormBuilder 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%2Fformbuilder.com%2Fformbuilder" | shStep 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%2Fformbuilder.com%2Fformbuilder" | 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.
What an agent can do with FormBuilder API.
Create an account and API key in a single signup call, no browser required
Create forms and optionally publish them in the same request
List a form's responses newest-first and retrieve a single authorized response
Download the committed file attachments on a response
Register, list, and delete webhooks that fire on new responses
Draft, validate, publish, and unpublish forms through the agent endpoint set
Query a form for only the responses a token is eligible to read
Patterns agents use FormBuilder API for, with concrete tasks.
★ Agent Form Lifecycle
An AI agent connected through Jentic can sign up for an account, create a form, publish it after a safety review, and then read the responses it collects, without a developer wiring the FormBuilder API by hand. The agent uses the dedicated agent endpoints to draft and validate structure before publishing.
Sign up for an account, create and publish a feedback form, then list the first page of responses
Response Collection and Webhooks
Applications pull form responses and react to new submissions in real time. FormBuilder lists responses newest-first, retrieves a single authorized response, and registers webhooks so a backend is notified the moment a response arrives.
Register a webhook for new responses on a form and list the most recent responses
Attachment Handling
Forms that accept file uploads need a way to retrieve the uploaded bytes. FormBuilder lists the committed private attachments on a response and downloads the original attachment file for processing or archival.
List the files attached to a specific response and download the original attachment bytes
19 endpoints — the formbuilder api creates, publishes, and reads forms, and can bootstrap an account and api key in a single signup call so no browser is needed.
METHOD
PATH
DESCRIPTION
/api/v1/signup
Create an account and API key in one call
/api/v1/forms
Create a form, optionally publishing it
/api/v1/forms/{formId}/responses
List responses for a form, newest first
/api/v1/hooks
Register a webhook for new responses
/api/v1/agent/forms
Create an idempotent private draft
/api/v1/agent/forms/{formId}/publish
Publish a form with safety review
/api/v1/forms/{formId}/responses/{responseId}
Retrieve one authorized response
/api/v1/signup
Create an account and API key in one call
/api/v1/forms
Create a form, optionally publishing it
/api/v1/forms/{formId}/responses
List responses for a form, newest first
/api/v1/hooks
Register a webhook for new responses
/api/v1/agent/forms
Create an idempotent private draft
/api/v1/agent/forms/{formId}/publish
Publish a form with safety review
/api/v1/forms/{formId}/responses/{responseId}
Retrieve one authorized response
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FormBuilder API by hand means creating a personal access token, learning its separate agent endpoint set, and handling the safety-review publish step yourself. Through Jentic you install once, import FormBuilder from the API Directory, store the token once, and your agent calls it.
Permission scoping
FormBuilder carries the form id in the URL path, so a rule can pin your agent to one form and the operations you pick, such as reading responses and listing hooks. You choose the operations it may call, so actions like publishing, unpublishing, or deleting a webhook are not included unless you add them.
Credential isolation
Your FormBuilder 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 a form' or 'list form responses', and Jentic returns the matching FormBuilder operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using FormBuilder API through Jentic.
What authentication does the FormBuilder API use?
The FormBuilder API authenticates with a personal access token sent as a bearer token in the Authorization header, per its OpenAPI spec. You can create a token in the developer portal or bootstrap an account and token through the signup operation without a browser. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.
Can I publish a form with the FormBuilder API?
Yes. You can publish a form directly when you create it, or use the agent publish operation, which runs a safety review before the form goes live and begins accepting submissions.
Can I limit what my agent is allowed to do with the FormBuilder API?
Yes. Since the form id sits in the URL path, write a rule that pins the agent to one form and allows only the response-reading operations, so it can pull submissions without publishing, unpublishing, or deleting a webhook. Every call it makes is logged.
Is there a FormBuilder MCP server?
You do not need an MCP server to give your agent the FormBuilder API. Jentic connects it directly from the API Directory: import FormBuilder, store your token once, and the agent calls its operations by intent without loading another server's tool definitions into its context.
What are the rate limits for the FormBuilder API?
The OpenAPI spec does not specify numeric rate limits for the FormBuilder API. Check the FormBuilder documentation at https://formbuilder.com for current limits.
How do I create a form with the FormBuilder API through Jentic?
Search Jentic for an intent like 'create a form', and it returns FormBuilder's form-creation operation with its input schema so your agent can define fields and publish in one call. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED