Install Jentic One Beta

Connect the VOMO Client API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VOMO Client 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%2Fvomo.org%2Fvomo" | sh

Step 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%2Fvomo.org%2Fvomo" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with VOMO Client API.

List campaigns

Get campaign

Create group

Query and filter VOMO Client API records by parameters

Monitor VOMO Client API operational status and events

GET STARTED

Start building with VOMO Client API

Explore with Jentic One

View OpenAPI Document

Automated campaigns Management

Automate campaigns operations by combining multiple VOMO Client API endpoints. Agents can get campaign and then list projects in a single workflow.

Call GET /campaigns/{id} to get campaign, then verify the result

AI Agent Integration via Jentic

AI agents discover and call VOMO Client 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 'list campaigns', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — rest-based api for querying and managing volunteer data in vomo.

METHOD

PATH

DESCRIPTION

GET

/campaigns

List campaigns

GET

/campaigns/{id}

Get campaign

GET

/projects

List projects

GET

/projects/{id}

Get project

POST

/groups

Create group

GET

/groups

List groups

GET

/groups/{id}

Get group

PUT

/groups/{id}

Update group

GET

/campaigns

List campaigns

GET

/campaigns/{id}

Get campaign

GET

/projects

List projects

GET

/projects/{id}

Get project

POST

/groups

Create group

GET

/groups

List groups

GET

/groups/{id}

Get group

PUT

/groups/{id}

Update group

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring VOMO by hand means handling its JWT bearer token against api.vomo.org and managing the campaign, project, and group calls yourself. Through Jentic you install once, import VOMO Client from the API Directory, store the token once, and your agent calls it.

Permission scoping

VOMO puts the resource id in the URL path (/groups/{id}, /projects/{id}), so a rule can pin your agent to reading one project or group. You choose the operations it may call, so group updates via the PUT are not included unless you add them.

Credential isolation

Your VOMO bearer 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 'list campaigns' or 'read a group', and Jentic returns the matching VOMO operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using VOMO Client API through Jentic.

What authentication does the VOMO Client API use?

The VOMO Client 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 list campaigns with the VOMO Client API?

Yes. Use the GET /campaigns endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the VOMO Client 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 list campaigns through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list campaigns'. Jentic returns the matching VOMO Client API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the VOMO Client API have?

The VOMO Client API exposes 15 endpoints covering campaigns, certificates, forms operations.

Can I limit what my agent is allowed to do with the VOMO Client API?

Yes. Because Jentic One is self-hosted, you write the rules that decide which VOMO operations and credentials your agent may use. Since VOMO puts the resource id in the URL path, such as /projects/{id} and /groups/{id}, you can pin the agent to reading a single project or group. You also choose the exact operations it may call, so an action like the PUT /groups/{id} group update stays out of reach unless you explicitly grant it.

VOMO Client API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer15 EndpointsREST

For Agents

Programmatically list campaigns, get campaign. Covers 15 operations with bearer authentication.

Use for: I need to campaigns, I want to campaign, Search for projects, Find all project

Not supported: Does not handle payments, communications, or crm - use for marketing only.

REST-based API for querying and managing volunteer data in VOMO. The API provides access to campaigns, projects, organizations, groups, forms, and certifications. The API exposes 15 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

43%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

59%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

63%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the VOMO Client API to your agent

Capabilities

Start building with VOMO Client API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

VOMO Client API

Jentic AI Readiness Score

VOMO Client API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness