For Agents
Programmatically get user profile, get accounts. Covers 15 operations with apiKey authentication.
Use for: I need to user profile, I want to accounts, Search for calendars, Find all contact
Not supported: Does not handle payments, communications, or crm - use for productivity only.
Terros API for managing accounts, calendars, contacts, dispositions, evaluations, locations, reports, tasks, teams, users, imports, and exports. The API exposes 15 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Terros 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%2Fterros.com%2Fterros" | 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%2Fterros.com%2Fterros" | 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 Terros API.
Get user profile
Create contact
Integrate Terros API into automated workflows
Query and filter Terros API records by parameters
Monitor Terros API operational status and events
Patterns agents use Terros API for, with concrete tasks.
★ Productivity Operations
Use the Terros API to perform productivity operations programmatically. The API provides 15 endpoints covering core functionality including get user profile, get accounts, get calendars.
Call POST /user/get to get user profile
Automated account Management
Automate account operations by combining multiple Terros API endpoints. Agents can get accounts and then get calendars in a single workflow.
Call GET /account to get accounts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Terros 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 apiKey tokens manually.
Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials
15 endpoints — terros api for managing accounts, calendars, contacts, dispositions, evaluations, locations, reports, tasks, teams, users, imports, and exports.
METHOD
PATH
DESCRIPTION
/user/get
Get user profile
/account
Get accounts
/calendar
Get calendars
/contact
Create contact
/contact
Get contacts
/disposition
Get dispositions
/evaluation
Get evaluations
/location
Get locations
/user/get
Get user profile
/account
Get accounts
/calendar
Get calendars
/contact
Create contact
/contact
Get contacts
/disposition
Get dispositions
/evaluation
Get evaluations
/location
Get locations
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Terros API by hand means learning its ApiKey Authorization header auth against the api.terros.com host and coding each account, contact, and calendar call yourself. Through Jentic you install once, import the Terros API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Terros carries its lookup and record details in request bodies and query parameters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as reading a user profile or listing contacts. You choose the operations it may call, so creating a contact is not included unless you add it.
Credential isolation
Your Terros 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 'get a user profile' or 'list contacts', and Jentic returns the matching Terros API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Terros API through Jentic.
What authentication does the Terros API use?
The Terros API uses an API key passed in the `Authorization` header. 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 get user profile with the Terros API?
Yes. Use the POST /user/get endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Terros 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 get user profile through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user profile'. Jentic returns the matching Terros API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Terros API have?
The Terros API exposes 15 endpoints covering account, calendar, contact operations.
GET STARTED