Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Genaya 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%2Fgenaya.com%2Fgenaya" | 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%2Fgenaya.com%2Fgenaya" | 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 Genaya API.
Create and update clients and contacts in your Genaya organization
Book, reschedule, and cancel appointments for a client
Issue estimates, mark them sent, and convert an accepted one into an invoice
Capture leads into a lead table and add a contact to a campaign audience
Create and track tasks and reminders for your team
GET STARTED
Receive outbound webhook events on your server as they happen
Patterns agents use Genaya API for, with concrete tasks.
★ Agent-Run Client Scheduling
An AI agent connected through Jentic creates a client record and books their appointment in one flow, so intake and scheduling happen without a person at the front desk. Because the agent works against the same client, contact, and appointment resources the Genaya app uses, the booking shows up for the team immediately.
Create a client, then book an appointment for them at the requested time and confirm it was created
Estimate-to-Invoice Billing
A workflow issues an estimate for a job, marks it as sent to the client, and converts it into an invoice once the client accepts, keeping the quote and the bill tied together. This moves a service business from quote to billing without re-entering line items by hand.
Create an estimate, mark it as sent, and convert it to an invoice once the client accepts
Lead Capture into Marketing Audiences
An intake form or agent captures a new lead into a Genaya lead table and pushes the lead's contact into a campaign audience, so a sign-up flows straight into marketing without a manual export. The lead and the audience membership stay in the same organization the rest of the data lives in.
Create a lead in the lead table and add the lead's contact to a campaign audience
152 endpoints — the genaya api lets you build on top of a genaya organization, reading and writing the clients, contacts, and appointments that a service business runs on.
METHOD
PATH
DESCRIPTION
/clients
Create a client
/clients
List clients
/appointments
Create an appointment
/estimates/{id}/convert-to-invoice
Convert an estimate to an invoice
/invoices
Create an invoice
/lead-tables/{tableId}/leads
Create a lead in a lead table
/audiences/{audienceId}/contacts
Add a contact to a campaign audience
/tasks
Create a task
/clients
Create a client
/clients
List clients
/appointments
Create an appointment
/estimates/{id}/convert-to-invoice
Convert an estimate to an invoice
/invoices
Create an invoice
/lead-tables/{tableId}/leads
Create a lead in a lead table
/audiences/{audienceId}/contacts
Add a contact to a campaign audience
/tasks
Create a task
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Genaya API by hand means handling its bearer-token keys, keeping live and test keys straight against the same organization data, and subscribing to its outbound webhooks yourself. Through Jentic you install once, import Genaya from the API Directory, store the key once, and your agent calls it.
Permission scoping
Genaya scopes each key to a single organization, so your agent can never reach another organization's data, and on top of that you choose which operations it may call. Allow creating clients and booking appointments while leaving deletes out, so destructive operations like deleting a client or an invoice are not included unless you add them.
Credential isolation
Your Genaya 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 'book a client appointment' or 'convert an estimate to an invoice', and Jentic returns the matching Genaya operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Genaya API through Jentic.
Is there a Genaya MCP server?
You don't need an MCP server to give your agent the Genaya API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can create clients, book appointments, and issue invoices straight away, with no extra server to run and no tool definitions to load into the agent's context.
Can I limit what my agent is allowed to do with the Genaya API?
Yes. Write a rule that allows only the operations the agent needs, such as creating clients and booking appointments, so it can run intake without touching invoices or deleting records. Destructive operations like deleting a client or an invoice are not included unless you add them, and every call the agent makes is logged.
What authentication does the Genaya API use?
The Genaya API authenticates with a bearer token: a Genaya-issued API key sent in the Authorization header, per its OpenAPI spec. Keys come in live and test modes that operate on the same organization data. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.
Can I convert an estimate into an invoice with the Genaya API?
Yes. You create an estimate, mark it as sent, and then call the convert-to-invoice operation to turn an accepted estimate into an invoice without re-entering the line items. The resulting invoice lives in the same organization as the estimate it came from.
What are the rate limits for the Genaya API?
The OpenAPI spec does not state a per-second rate limit; Genaya allocates a pool of requests per billing period that varies by plan, and API access requires a paid plan. For current allowances, see the Genaya developer documentation at https://developer.genaya.com.
How do I book a client appointment through Jentic?
Import the Genaya API from the Jentic API Directory, then have your agent issue a request such as 'create a client and book their appointment'. Jentic matches the intent to the create-client and create-appointment operations and returns their input schema so the agent fills in the right fields, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Create and update clients, contacts, and appointments, issue estimates and invoices, and capture leads in a Genaya organization. Authenticates with a bearer token.
Use for: Create a new client and book their first appointment, Add a contact to a campaign audience, Convert an accepted estimate into an invoice, List all open invoices for my organization
Not supported: Does not handle payroll, general-ledger accounting, or ad-campaign buying. Use for managing your Genaya organization's clients, scheduling, estimates, and invoices only.
The Genaya API lets you build on top of a Genaya organization, reading and writing the clients, contacts, and appointments that a service business runs on. It also covers the money side, with estimates that can be sent and converted into invoices, plus expenses, and the pipeline side, with lead tables, campaign audiences, tasks, and reminders. Outbound webhooks push events to your server as they happen, and everything is scoped to one organization by the API key you use.
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>