Install Jentic One Beta

Connect the Climbo API to your agent

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

Add a client to your Climbo account and retrieve its profile by client id

Move a client onto a different plan with the change-plan operation

Activate or pause a client by changing its status

List every client in the account and look up the plans available to it

Subscribe a webhook for review and client events, and unsubscribe it by id

GET STARTED

Start building with Climbo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Climbo API for, with concrete tasks.

★ AI agent client onboarding

An AI agent onboards a new customer end to end: it adds the client to Climbo, assigns a plan, and subscribes a webhook so downstream systems hear about new reviews. Through Jentic the agent finds these operations by intent and calls them with the account's stored API key, without hand-wiring the client id path for each call.

Add a client named 'Acme Dental', assign a plan returned by the plans endpoint, and subscribe a webhook for review events

Review reputation monitoring

Agencies watching client reputation subscribe a webhook to receive review events as they arrive, then react without polling. Climbo delivers the events to the endpoint you register and lets you unsubscribe by webhook id when a client churns.

Subscribe a webhook pointing at the reporting service and confirm it was registered

Client plan and status changes

When a client upgrades, downgrades, or stops paying, the account operator changes the plan or status on that client record. Climbo exposes dedicated change-plan and change-status operations keyed by client id, so a billing workflow can apply the change directly.

Change the plan of client 12345 to the annual plan and verify the update

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for climbo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/client

Add a client

GET

/clients

List clients

POST

/client/{client_id}/change-plan

Change a client's plan

POST

/client/{client_id}/change-status

Change a client's status

GET

/plans

List plans

POST

/webhook/subscribe

Subscribe a webhook

POST

/client

Add a client

GET

/clients

List clients

POST

/client/{client_id}/change-plan

Change a client's plan

POST

/client/{client_id}/change-status

Change a client's status

GET

/plans

List plans

POST

/webhook/subscribe

Subscribe a webhook

Why Jentic?

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

Setup

Wiring the Climbo API by hand means creating an x-api-key header, matching each call to the right client id in the path, and handling webhook subscription yourself. Through Jentic you install once, import Climbo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Climbo puts the client id in the URL path (/client/{client_id}), so a rule can pin your agent to the read and update operations and leave deletion out. You choose the operations it may call, so destructive ones like deleting a client or unsubscribing a webhook are not included unless you add them.

Credential isolation

Your Climbo 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 client' or 'subscribe a review webhook', and Jentic returns the matching Climbo operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Climbo API through Jentic.

Why is there no official OpenAPI spec for Climbo API?

Climbo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Climbo API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Climbo MCP server?

You don't need an MCP server to connect your agent to the Climbo API. Jentic connects it directly from the API Directory: import Climbo, store your API key once, and your agent calls its client, plan, and webhook operations on demand.

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

Yes. Write a rule that allows only the add-client, list-clients, and change-plan operations, so the agent can onboard and update clients but cannot delete a client or remove a webhook. Climbo carries the client id in the URL path, and every call the agent makes is logged.

What authentication does the Climbo API use?

The Climbo API authenticates with an API key sent in the x-api-key request header, per its OpenAPI spec. Through Jentic the key is stored once by your self-hosted instance and injected at call time, so it never reaches the agent's context.

Can I change a client's plan with the Climbo API?

Yes. The change-plan operation takes a client id in the path and moves that client onto a different plan, and a matching change-status operation activates or pauses the client. Use the plans endpoint first to find the plan you want to assign.

What are the rate limits for the Climbo API?

The OpenAPI spec does not specify rate limits. Check the Climbo documentation at climbo.readme.io for current limits before running high-volume jobs.

How do I add a client to Climbo through Jentic?

Search Jentic for 'add a client to Climbo' and it returns the add-client operation with its input schema. Your agent calls it with the client details, then assigns a plan and subscribes a webhook, all with the API key injected at execution time.

Climbo API

Name: Climbo API
Brand: Climbo
Availability: InStock

Agent-ready OpenAPI document · curated by JenticCRMContact ManagementapiKey10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Add and look up Climbo clients, change their plan or status, list available plans, and subscribe webhooks for review and client events.

Use for: Add a new client to my Climbo account, Change a client's subscription plan, Pause a client that has not paid, List all clients in my account

Not supported: Does not handle payment collection, invoicing, or review content moderation. Use for Climbo client, plan, and webhook management only.

Jentic publishes the only available OpenAPI specification for Climbo API, keeping it validated and agent-ready. The Climbo API adds and retrieves client records, moves clients between subscription plans, and subscribes webhooks for a reputation management platform. It exposes client, plan, and webhook operations so an agency can wire client onboarding and review notifications into its own systems.

Jentic One on Github View OpenAPI Document

Connect the Climbo API to your agent

Capabilities

Start building with Climbo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Climbo API