Install Jentic One Beta

Connect the JobBooker API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JobBooker 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%2Fjobbooker.ai%2Fjobbooker" | 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%2Fjobbooker.ai%2Fjobbooker" | 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 JobBooker API.

Hand JobBooker a lead event such as a new Yelp lead or a customer message, with fields like consumer_name, job_names, postal_code, and availability_dates, and receive the drafted reply

Detect replayed new-lead events: JobBooker returns the earlier reply flagged with duplicate: true instead of answering twice

Subscribe a REST hook to a hooks.zapier.com target_url for the reply_ready or owner_alert event

List the business's hook subscriptions and unsubscribe one by its id or target_url

GET STARTED

Start building with JobBooker API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use JobBooker API for, with concrete tasks.

★ Agent-Driven Lead Response via Jentic

An AI agent watching a home-service business's lead inbox forwards each new lead to the JobBooker lead event operation with the customer's name, requested job, postal code, and availability. Through Jentic the agent finds the operation by intent and calls it with the stored business key, then relays the reply JobBooker writes back to the lead source, so the lead gets an answer in the owner's voice without the agent drafting it.

Send a new-lead event with id, consumer_name 'Dana Ruiz', job_names ['Water heater repair'], and postal_code '94110' to JobBooker, then return the reply text it drafts

Zapier Instant Triggers for Replies and Alerts

A Zapier integration subscribes a hooks.zapier.com target_url to the reply_ready event so drafted replies are pushed out as soon as they are ready, and to owner_alert so the business owner hears about leads that need attention. When the Zap is turned off, the hook is removed by its subscription id or target URL.

Subscribe a hooks.zapier.com target_url to the owner_alert event, list subscriptions to confirm it is active, and later unsubscribe it by its id

Building and Testing a Lead Flow Before Go-Live

Before any real lead has arrived, an automation builder pulls sample payloads for reply_ready, or for owner_alert with the event query parameter, shaped exactly like live hook deliveries. That lets the downstream steps be mapped and tested, and a quick key check confirms which business the connection is for.

Verify the API key returns the expected business, then fetch the sample owner_alert payload and list the fields a downstream step should map

Key Endpoints

7 endpoints — the jobbooker api hands jobbooker the leads and messages that arrive at a home-service business's lead sources and returns the replies it writes in the owner's voice.

METHOD

PATH

DESCRIPTION

POST

/api/webhooks/zapier

Process a lead event and get the reply

POST

/api/zapier/hooks

Subscribe a REST hook

GET

/api/zapier/hooks

List subscriptions

DELETE

/api/zapier/hooks

Unsubscribe a REST hook

GET

/api/zapier/hooks/sample

Get sample hook payloads

GET

/api/zapier/me

Test the API key

POST

/api/webhooks/zapier

Process a lead event and get the reply

POST

/api/zapier/hooks

Subscribe a REST hook

GET

/api/zapier/hooks

List subscriptions

DELETE

/api/zapier/hooks

Unsubscribe a REST hook

GET

/api/zapier/hooks/sample

Get sample hook payloads

GET

/api/zapier/me

Test the API key

Why Jentic?

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

Setup

Wiring JobBooker by hand means sending its `x-jobbooker-key` header, shaping lead events in the Yelp-through-Zapier format, and handling the two response paths: a reply in the body or a 202 when a Reply Ready hook takes over. Through Jentic you install once, import JobBooker from the API Directory, store the key once, and your agent calls it.

Permission scoping

JobBooker carries the business, lead, and subscription details inside the request body, so rules bound which operations your agent may call, such as sending lead events or listing subscriptions, not which lead or hook. You choose the operations it may call, so changes like subscribing or unsubscribing hooks are not included unless you add them.

Credential isolation

Your JobBooker business 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 'reply to a new lead' or 'subscribe to owner alerts', and Jentic returns the matching JobBooker operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using JobBooker API through Jentic.

What authentication does the JobBooker API use?

The JobBooker API authenticates with the business's API key sent in the `x-jobbooker-key` header, per its OpenAPI spec; the key is shown in the JobBooker dashboard under Settings, Connect, and the spec notes a ?key= query parameter is also accepted. The describe-endpoint call (GET /api/webhooks/zapier) is open and needs no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Is there a JobBooker MCP server?

You don't need an MCP server to give your agent JobBooker. Jentic connects it directly from the API Directory: import it, store your business key once, and your agent can hand off leads and manage hook subscriptions. Operations are discovered on demand, so no extra server's tool definitions are loaded into your agent's context.

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

Yes. For example, write a rule that allows only the lead event operation and the subscription list, so an agent can forward leads and see which hooks exist but cannot subscribe or remove hooks. JobBooker carries the business and subscription details in the request body, so the rule bounds which operations the agent may call rather than which subscription, and every call is logged.

What happens if the same lead is sent to JobBooker twice?

A new-lead event replayed for a lead that was already answered returns the earlier reply with duplicate: true, so the customer is not answered twice. If a Reply Ready subscription exists, the lead event call returns 202 with accepted: true and the reply arrives through the hook instead of in the response.

What are the rate limits for the JobBooker API?

Per the JobBooker OpenAPI spec, the lead event operation is limited to 60 requests per minute per business, and subscribing a REST hook is limited to 30 per minute. The spec does not list limits for the other operations.

How do I send a lead to JobBooker through Jentic?

Search Jentic for an intent like 'reply to a new home service lead', import JobBooker from the API Directory, and store your business key once. Your agent then calls POST /api/webhooks/zapier with the lead's id and details such as consumer_name and job_names, and reads the drafted reply from the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.

JobBooker API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsChat MessagingapiKey7 EndpointsREST

For Agents

Send a home-service lead or customer message to JobBooker and get back the reply it writes, or subscribe a hook to receive replies and owner alerts. Covers lead events, REST hook subscriptions, and sample payloads.

Use for: I need to send a new Yelp lead to JobBooker and get a reply, Forward a customer's follow-up message so JobBooker can answer it, Subscribe my webhook to JobBooker owner alerts, List all of my JobBooker hook subscriptions

Not supported: Does not handle calendar booking calls, payment collection, or contact record editing through this API. Use for handing lead events to JobBooker and receiving its replies and alerts only.

The JobBooker API hands JobBooker the leads and messages that arrive at a home-service business's lead sources and returns the replies it writes in the owner's voice. A lead event can be a new lead, a customer message, a message the business sent itself, or a shared phone number; JobBooker classifies it and either returns the reply directly or pushes it through a Reply Ready subscription. Automation tools subscribe REST hooks for the reply_ready and owner_alert events, list and remove those subscriptions, and pull sample payloads to build a flow before any real lead arrives. Yelp through Zapier is the first supported lead source.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

60%

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.

46%

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: DSignals: 4

31%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

86%

OperationId Quality

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

64%

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: C-Signals: 1

50%

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: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the JobBooker API to your agent

Capabilities

Start building with JobBooker API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

JobBooker API

Jentic AI Readiness Score

JobBooker 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