Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Polyform 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%2Fpolyform.to%2Fpolyform-api" | 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%2Fpolyform.to%2Fpolyform-api" | 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 Polyform API.
List all forms in a workspace with metadata and creation dates
Retrieve form responses with filtering by date range and submission status
Configure webhooks to receive real-time notifications on form submissions
Manage webhook endpoints including creation, updates, and deletion
Access authenticated user profile and workspace information
GET STARTED
Query form structure including fields, validation rules, and design settings
Patterns agents use Polyform API for, with concrete tasks.
★ Embedded Form Integration in SaaS Applications
SaaS platforms embed Polyform forms directly into their product experience for user onboarding, feedback collection, and feature requests. The API enables creating forms programmatically based on customer tier or feature flags, retrieving responses to populate customer profiles, and routing submissions to CRM systems via webhooks. Development teams use the API to maintain forms in version control alongside application code, deploy form changes through CI/CD pipelines, and test form workflows in staging environments before production release.
Create Polyform form with fields matching customer onboarding flow, embed form in application using Polyform's iframe or API, configure webhook to POST submissions to backend CRM endpoint, retrieve responses for analytics dashboard.
Lead Capture and Marketing Automation
Marketing teams use Polyform for landing page lead capture with responses flowing automatically to marketing automation platforms. The API's webhook functionality enables real-time lead routing to HubSpot, Salesforce, or custom lead scoring systems. When a high-value lead submits a form (detected via enrichment APIs), webhooks trigger immediate sales notifications. The response retrieval endpoints enable daily exports to BI tools for conversion rate analysis and A/B test reporting on form variants.
Configure Polyform webhook to POST form submissions to marketing automation platform, enrich lead data using Clearbit API, route high-value leads to sales team via Slack notification, retrieve daily response exports for conversion tracking.
Customer Feedback and Support Request Collection
Product teams embed Polyform feedback forms within applications to collect feature requests, bug reports, and satisfaction scores. The API enables querying responses filtered by submission date to analyze feedback trends over sprint cycles. Webhook integration routes urgent support requests (indicated by priority field values) directly to ticketing systems like Jira or Linear. Customer success teams use the response export to identify common pain points and prioritize roadmap items based on quantitative feedback signals.
Embed Polyform feedback form in application, configure webhook to create Jira tickets for bug reports, query API daily for new feature requests, analyze response trends to prioritize product roadmap.
Event Registration and Attendee Management
Event organizers use Polyform for registration forms with the API handling attendee data synchronization to event management platforms. Webhook integration enables real-time attendee confirmations via email automation tools and Slack notifications for VIP registrations. The API's response filtering allows querying attendees by registration date for waitlist management and capacity planning. Post-event, organizers export all responses for badge printing, dietary preference tracking, and attendee analytics.
Create event registration form via Polyform, configure webhook to send confirmation emails via SendGrid, filter responses by registration date to manage waitlist, export attendee data for badge printing and catering planning.
4 endpoints — polyform is a modern form builder focused on developer-friendly workflows and clean design aesthetics.
METHOD
PATH
DESCRIPTION
/api/me
Get authenticated user profile and workspace info
/api/forms
List all forms in the workspace
/api/responses
Retrieve form responses with filtering
/api/webhooks
Create a new webhook endpoint
/api/me
Get authenticated user profile and workspace info
/api/forms
List all forms in the workspace
/api/responses
Retrieve form responses with filtering
/api/webhooks
Create a new webhook endpoint
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Polyform API by hand means setting up bearer auth against auth.polyform.to and coding its form, response, and webhook calls yourself. Through Jentic you install once, import the Polyform API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Polyform identifies forms and responses through request parameters rather than pinning one in the URL path, so scope the agent to the operations it needs, such as listing forms or reading responses. You choose that set, so a write like registering a webhook is included only if you add the POST /api/webhooks operation while a read-only agent keeps just the form and response reads.
Credential isolation
Your Polyform 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 'retrieve form responses from last week' or 'list forms', and Jentic returns the matching Polyform 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 Polyform API through Jentic.
What authentication does the Polyform API use?
The Polyform API uses Bearer token authentication. You generate API tokens from your Polyform workspace settings and include them in the Authorization header as a Bearer token for all requests.
How do webhooks work in Polyform?
Polyform webhooks send HTTP POST requests to your configured endpoint URL whenever specified events occur (like form submissions). The webhook payload includes the form response data in JSON format, enabling real-time integrations with CRM, email, and backend systems.
Can I filter form responses by date with the Polyform API?
Yes, the responses endpoint supports query parameters for filtering by submission date range, allowing you to retrieve only responses from specific time periods for reporting and analytics workflows.
Is Polyform suitable for embedding forms in SaaS applications?
Yes, Polyform is designed for developer-first workflows with an API-first architecture. You can programmatically create forms, manage them in version control, and embed them in applications using iframe or API-driven rendering.
How do AI agents use the Polyform API through Jentic?
Agents search Jentic for tasks like 'retrieve form responses from today' and receive Polyform operation schemas. Jentic securely stores API tokens, handles authentication, and allows agents to list forms, query responses, and configure webhooks with natural language parameters.
Can I limit what my agent is allowed to do with the Polyform API?
Yes. Because you run Jentic One yourself, you decide which Polyform operations the agent can call, and your own rules govern how the stored token is used at execution time. Polyform identifies forms and responses through request parameters rather than the URL path, so you scope the agent by the operation set you import, for example GET /api/forms and GET /api/responses for a read-only agent. A write such as registering a webhook via POST /api/webhooks is available to the agent only if you add that operation to its allowed set.
For Agents
Create and manage forms, collect responses, and configure webhooks through Polyform's developer-focused form platform.
Use for: List all forms in my workspace, Get responses submitted today for a contact form, Set up a webhook to send form submissions to my backend, Retrieve all form responses for analysis
Not supported: Provides form management, response collection, and webhook configuration. Does not handle payment processing, file uploads beyond basic attachments, or advanced conditional logic-use specialized form platforms for those features.
Polyform is a modern form builder focused on developer-friendly workflows and clean design aesthetics. The Polyform API provides programmatic access to form management, response collection, and webhook configuration. Unlike traditional form builders, Polyform emphasizes API-first architecture where forms can be created and managed entirely through code, enabling version control and infrastructure-as-code patterns. Developers use it to build custom form experiences embedded in applications, automate form creation for dynamic use cases, and route responses to backend systems via webhooks. The API supports retrieving authenticated user information, listing all forms in a workspace, accessing form responses with filtering, and managing webhook endpoints for real-time event notifications. It's particularly suited for SaaS applications needing embeddable forms, developer tools requiring feedback collection, and no-code platforms integrating form capabilities.