Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zivvy Web Forms 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%2Fzivvy.com%2Fzivvy" | 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%2Fzivvy.com%2Fzivvy" | 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 Zivvy Web Forms API.
Add a web lead (POST)
Get age groups
Integrate Zivvy Web Forms API into automated workflows
Query and filter Zivvy Web Forms API records by parameters
Monitor Zivvy Web Forms API operational status and events
GET STARTED
Patterns agents use Zivvy Web Forms API for, with concrete tasks.
★ CRM Operations
Use the Zivvy Web Forms API to perform crm operations programmatically. The API provides 3 endpoints covering core functionality including add a web lead (post), add a web lead, get age groups.
Call POST / to add a web lead (post)
Automated ?Action=Getagegroups Management
Automate ?action=getagegroups operations by combining multiple Zivvy Web Forms API endpoints. Agents can add a web lead and then get age groups in a single workflow.
Call GET / to add a web lead, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Zivvy Web Forms API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'add a web lead (post)', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — zivvy (powered by addmembers/rainmaker) provides apis for adding web leads and retrieving age groups for martial arts schools.
METHOD
PATH
DESCRIPTION
/
Add a web lead (POST)
/
Add a web lead
/?action=GetAgeGroups
Get age groups
/
Add a web lead (POST)
/
Add a web lead
/?action=GetAgeGroups
Get age groups
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Zivvy Web Forms by hand means passing your apikey on the query string against the addmembers.com host and shaping web lead payloads yourself. Through Jentic you install once, import Zivvy Web Forms from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Zivvy Web Forms passes lead details in the request body and query rather than as owned path resources, so scoping is operations-only: limit the agent to the operations it needs, such as adding a web lead or reading age groups. You choose the operations it may call, so anything you leave out is not included unless you add it.
Credential isolation
Your Zivvy Web Forms 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 'add a web lead' or 'get age groups', and Jentic returns the matching Zivvy Web Forms 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 Zivvy Web Forms API through Jentic.
What authentication does the Zivvy Web Forms API use?
The Zivvy Web Forms API uses an API key passed in the `apikey` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I add a web lead (post) with the Zivvy Web Forms API?
Yes. Use the POST / endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Zivvy Web Forms API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I add a web lead (post) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a web lead (post)'. Jentic returns the matching Zivvy Web Forms API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Zivvy Web Forms API have?
The Zivvy Web Forms API exposes 3 endpoints covering ?action=getagegroups operations.
Can I limit what my agent is allowed to do with the Zivvy Web Forms API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Zivvy Web Forms operations your agent may call. Zivvy Web Forms passes lead details in the request body and query rather than as owned path resources, so scoping is operations-only: you can allow the agent to add a web lead while withholding the ability to read age groups, or the reverse. Any operation you do not grant is unavailable to the agent unless you add it.
For Agents
Programmatically add a web lead (post), add a web lead. Covers 3 operations with apiKey authentication.
Use for: I need to add a web lead (post), I want to add a web lead, Search for age groups, List all records from Zivvy Web Forms API
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Zivvy (powered by AddMembers/RainMaker) provides APIs for adding web leads and retrieving age groups for martial arts schools. The API exposes 3 endpoints secured with apiKey authentication.
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>