Install Jentic One Beta

Connect the Tall Bob API to your agent

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

Send Chat SMS

Create New Contact

View Contact Details

Delete Contact

Find Contact By External ID

GET STARTED

Start building with Tall Bob API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Tall Bob API for, with concrete tasks.

★ CRM Operations

Use the Tall Bob API to perform crm operations programmatically. The API provides 48 endpoints covering core functionality including send chat sms, create new contact, view contact details.

Call POST /v2/chat/send/sms to send chat sms

Automated Account Management

Automate account operations by combining multiple Tall Bob API endpoints. Agents can create new contact and then view contact details in a single workflow.

Call POST /v2/contacts to create new contact, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tall Bob 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 basic tokens manually.

Search Jentic for 'send chat sms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

48 endpoints — tall bob sms, mms, and messaging api for sending and managing communications, contacts, campaigns, and webhooks.

METHOD

PATH

DESCRIPTION

POST

/v2/chat/send/sms

Send Chat SMS

POST

/v2/contacts

Create New Contact

GET

/v2/contacts/{contact_id}

View Contact Details

DELETE

/v2/contacts/{contact_id}

Delete Contact

POST

/v2/contacts/find

Find Contact By External ID

GET

/v2/contacts/

List Contacts

GET

/v2/contacts/{contact_id}/campaigns

List Contact Campaigns

PUT

/v2/contacts/{contact_id}/metadata

Upsert Contact Metadata

POST

/v2/chat/send/sms

Send Chat SMS

POST

/v2/contacts

Create New Contact

GET

/v2/contacts/{contact_id}

View Contact Details

DELETE

/v2/contacts/{contact_id}

Delete Contact

POST

/v2/contacts/find

Find Contact By External ID

GET

/v2/contacts/

List Contacts

GET

/v2/contacts/{contact_id}/campaigns

List Contact Campaigns

PUT

/v2/contacts/{contact_id}/metadata

Upsert Contact Metadata

Why Jentic?

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

Setup

Wiring the Tall Bob API by hand means setting up HTTP basic auth with your API username and key, sending it on every call, and threading contact ids through nested campaign and metadata routes yourself. Through Jentic you install once, import the Tall Bob API from the API Directory, store the basic credential once, and your agent calls it.

Permission scoping

Tall Bob puts the contact id in the URL path (/v2/contacts/{contact_id}/...), so a rule can pin your agent to one contact: it can read that contact and its campaigns and nothing else. You choose the operations it may call, so deleting a contact or sending SMS is not included unless you add it.

Credential isolation

Your Tall Bob basic credential 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 'send an SMS' or 'find a contact', and Jentic returns the matching Tall Bob operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tall Bob API through Jentic.

What authentication does the Tall Bob API use?

The Tall Bob API uses HTTP Basic authentication with username and password. 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 send chat sms with the Tall Bob API?

Yes. Use the POST /v2/chat/send/sms endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tall Bob 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 send chat sms through Jentic?

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

How many endpoints does the Tall Bob API have?

The Tall Bob API exposes 48 endpoints covering account, chat, contact lists operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Tall Bob operations and credentials the agent may use. Since the contact id sits in the URL path (/v2/contacts/{contact_id}/...), you can pin the agent to a single contact so it only reads that contact and its campaigns and nothing else. Operations like deleting a contact or sending an SMS via POST /v2/chat/send/sms are not available to the agent unless you explicitly add them.

Tall Bob API

Name: Tall Bob API
Brand: Tall Bob API
Availability: InStock

Official vendor OpenAPI document · agent-readyCRMContact Managementbasic48 EndpointsREST

For Agents

Programmatically send chat sms, create new contact. Covers 48 operations with basic authentication.

Use for: I need to send chat sms, I want to new contact, Search for view contact details, Find all contact

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

Tall Bob SMS, MMS, and messaging API for sending and managing communications, contacts, campaigns, and webhooks. The API exposes 48 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Tall Bob API to your agent

Capabilities

Start building with Tall Bob API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tall Bob API