For Agents
Authenticate as an EasyFill user, list active child-care centres, retrieve responses for a form, and share a form to a centre via API.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EasyFill.ai 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%2Fadmin.easyfill.invo.zone%2Feasyfill" | 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%2Fadmin.easyfill.invo.zone%2Feasyfill" | 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 EasyFill.ai API.
Authenticate users with email and password to receive an EasyFill access token
List all active child-care centres connected to the EasyFill account
Retrieve the full set of submitted responses for a given form
GET STARTED
Use for: I need to log in and get an EasyFill access token, List all active child-care centres, Retrieve all responses submitted to form 1234, Share form 1234 to a specific child-care centre
Not supported: Does not handle email delivery, payment processing, or general user-account management - use for child-care form distribution and response retrieval only.
Jentic publishes the only available OpenAPI specification for EasyFill.ai API, keeping it validated and agent-ready. EasyFill.ai is a form-building platform aimed at child-care centres and similar service providers, and its API exposes 5 endpoints for authenticating users, listing active centres, retrieving form responses, and sharing forms to a specific centre. Use it to automate response collection and form distribution rather than doing it manually in the EasyFill admin UI.
Share a specific form to a child-care centre to collect responses there
Automate response collection workflows that would otherwise require manual UI clicks
Patterns agents use EasyFill.ai API for, with concrete tasks.
★ Form Response Export
Operations teams running surveys across multiple child-care centres pull all submitted responses for a form using GET /api/forms/{form_id}/responses. The export feeds into reporting pipelines or LLM-driven response summarisation without re-keying data from the admin UI. Setup takes minutes once a token is obtained.
Authenticate via POST /api/users/login, then call GET /api/forms/1234/responses and serialise the responses to CSV
Form Distribution to Centres
Programme managers share a form template to a specific child-care centre via POST /api/forms/share_to_child_care_center so each centre receives its own response collection link. This avoids manual sharing through the admin UI when many centres need the same form on a recurring schedule.
Share form 1234 to child care centre 56 via POST /api/forms/share_to_child_care_center
Active Centre Roster Sync
BI and ops teams sync the list of active child-care centres into a downstream system using GET /api/child_care_centers/active. The list is used as the source of truth for distribution lists, dashboards, and audits without scraping the admin UI.
Pull the active list of child care centres and write it to a Google Sheet for the operations team
Agent-Driven Response Summaries via Jentic
AI agents can authenticate to EasyFill and pull responses through Jentic to generate summaries of qualitative answers across all centres. Credentials are held in your Jentic One instance rather than passed into the agent prompt, which matters because EasyFill auth is by username and password.
Search Jentic for 'easyfill form responses', load GET /api/forms/{form_id}/responses, and execute it for form 1234 then summarise free-text answers
5 endpoints — jentic publishes the only available openapi specification for easyfill.
METHOD
PATH
DESCRIPTION
/api/users/login
Log in and receive an access token
/api/child_care_centers/active
List active child-care centres
/api/forms/{form_id}/responses
List responses for a form
/api/forms/share_to_child_care_center
Share a form to a centre
/api/users/login
Log in and receive an access token
/api/child_care_centers/active
List active child-care centres
/api/forms/{form_id}/responses
List responses for a form
/api/forms/share_to_child_care_center
Share a form to a centre
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the EasyFill.ai API by hand means exchanging an email and password login for a token and reattaching it to each form call. Through Jentic you install once, import EasyFill.ai from the API Directory, store the credential once, and your agent calls it.
Permission scoping
EasyFill.ai puts the form id in the URL path (/api/forms/{form_id}/responses) for reads while sharing targets travel in the request body, so you limit the agent to the operations it needs, such as reading form responses or listing active child-care centers. Because you pick the operations, sharing a form to a center stays out unless you include it.
Credential isolation
Your EasyFill.ai email and password are stored once, encrypted, by your own Jentic One instance and exchanged for an access token at execution time. Neither the password nor the token enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get easyfill form responses' or 'list active child-care centers', and Jentic returns the matching EasyFill.ai 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 EasyFill.ai API through Jentic.
Why is there no official OpenAPI spec for EasyFill.ai API?
EasyFill.ai does not publish a public OpenAPI specification. Jentic generates and maintains this spec from EasyFill's internal swagger.yaml so AI agents and developers can call it via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the EasyFill.ai API use?
EasyFill uses an API-key style token returned by POST /api/users/login. The token is sent on subsequent requests in the lowercase 'authorization' header. Through Jentic, the email/password credentials are exchanged for the token in the vault and the agent never handles either.
Can I retrieve all responses for an EasyFill form?
Yes. GET /api/forms/{form_id}/responses returns the submitted responses for the form ID supplied in the path. The endpoint is the canonical export path for response data.
How do I share a form to a child-care centre with the EasyFill.ai API through Jentic?
Search Jentic for 'easyfill share form to centre', load POST /api/forms/share_to_child_care_center, and execute it with the form ID and centre ID. Jentic returns the input schema so the agent supplies only the fields the endpoint accepts.
What are the rate limits for the EasyFill.ai API?
The OpenAPI specification does not publish numeric rate limits. EasyFill applies fair-use limits server-side; HTTP 429 responses indicate throttling. Through Jentic, retries with backoff can be configured in the execution request.
Can I list all active child-care centres in my EasyFill account?
Yes. GET /api/child_care_centers/active returns every centre currently active for your account, which is useful for syncing centre directories or driving form-distribution loops.
Can I limit what my agent is allowed to do with the EasyFill.ai API?
Yes. Because Jentic One is self-hosted and you decide which operations it exposes, you can allow your agent only the EasyFill calls it needs, such as GET /api/forms/{form_id}/responses to read submitted responses or GET /api/child_care_centers/active to list active centres. If you do not include the sharing operation, POST /api/forms/share_to_child_care_center stays out of reach, so the agent cannot distribute forms to a centre. The email and password credential is held by your own instance and exchanged for the access token at execution time, so the agent never handles it directly.