Tall Bob API

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.