Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Serio Verify 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%2Fserioverify.com%2Fserioverify" | 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%2Fserioverify.com%2Fserioverify" | 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 Serio Verify API.
Authenticate and get JWT token
Get available countries
Add a Zapier webhook URL
Delete a Zapier webhook URL
Monitor Serio Verify API operational status and events
GET STARTED
Patterns agents use Serio Verify API for, with concrete tasks.
★ Developer Tools Operations
Use the Serio Verify API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including authenticate and get jwt token, get available countries, get available campaigns for a country.
Call POST /api/authenticate to authenticate and get jwt token
Automated Authentication Management
Automate authentication operations by combining multiple Serio Verify API endpoints. Agents can get available countries and then get available campaigns for a country in a single workflow.
Call GET /api/zapier/Countries/ to get available countries, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Serio Verify 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 bearer tokens manually.
Search Jentic for 'authenticate and get jwt token', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — serio verify api for managing campaigns, sources, countries, and zapier webhooks.
METHOD
PATH
DESCRIPTION
/api/authenticate
Authenticate and get JWT token
/api/zapier/Countries/
Get available countries
/api/zapier/campaigns/{country}
Get available campaigns for a country
/api/zapier/sources/{country}
Get available sources for a country
/api/zapier/collectionField/{campaignId}
Get collection fields for a campaign
/api/zapier/addZapierHookUrl
Add a Zapier webhook URL
/api/zapier/deleteZapierHookUrl/{id}
Delete a Zapier webhook URL
/api/zapier/getPerformList/{campaignId}
Get sample perform data for a campaign
/api/authenticate
Authenticate and get JWT token
/api/zapier/Countries/
Get available countries
/api/zapier/campaigns/{country}
Get available campaigns for a country
/api/zapier/sources/{country}
Get available sources for a country
/api/zapier/collectionField/{campaignId}
Get collection fields for a campaign
/api/zapier/addZapierHookUrl
Add a Zapier webhook URL
/api/zapier/deleteZapierHookUrl/{id}
Delete a Zapier webhook URL
/api/zapier/getPerformList/{campaignId}
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Serio Verify by hand means calling /api/authenticate to get a JWT, refreshing it as it expires, and attaching it to every Zapier-hook and campaign call yourself. Through Jentic you install once, import Serio Verify from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Serio Verify puts the campaign id and hook id in the URL path (/api/zapier/collectionField/{campaignId}, /api/zapier/deleteZapierHookUrl/{id}), so a rule can pin your agent to reading a specific campaign's fields. You choose the operations it may call, so hook deletion is not included unless you add it.
Credential isolation
Your Serio Verify credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'authenticate and get a token' or 'list campaigns for a country', and Jentic returns the matching Serio Verify 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 Serio Verify API through Jentic.
What authentication does the Serio Verify API use?
The Serio Verify API uses a Bearer token in the Authorization header. 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 authenticate and get jwt token with the Serio Verify API?
Yes. Use the POST /api/authenticate endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Serio Verify 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 authenticate and get jwt token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and get jwt token'. Jentic returns the matching Serio Verify API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Serio Verify API have?
The Serio Verify API exposes 8 endpoints covering authentication, campaigns, countries operations.
Can I limit what my agent is allowed to do with the Serio Verify API?
Yes. Because you run Jentic One yourself, your own rules decide which Serio Verify operations and credentials the agent may use. Serio Verify puts the campaign id and hook id in the URL path, such as GET /api/zapier/collectionField/{campaignId} and DELETE /api/zapier/deleteZapierHookUrl/{id}, so you can pin the agent to reading one specific campaign's fields. You choose the operations it may call, so deleting a Zapier webhook is not available unless you explicitly allow that operation.
For Agents
Programmatically authenticate and get jwt token, get available countries. Covers 8 operations with bearer authentication.
Use for: I need to authenticate and get jwt token, I want to available countries, Search for available campaigns for a country, Find all available sources for a country
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Serio Verify API for managing campaigns, sources, countries, and zapier webhooks. The API exposes 8 endpoints secured with bearer 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.
Get sample perform data for a campaign
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>