Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Streak CRM 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%2Fstreak.com%2Fstreak" | 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%2Fstreak.com%2Fstreak" | 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 Streak CRM API.
Get current user
List teams
Update pipeline
Query and filter Streak CRM API records by parameters
Monitor Streak CRM API operational status and events
GET STARTED
Patterns agents use Streak CRM API for, with concrete tasks.
★ CRM Operations
Use the Streak CRM API to perform crm operations programmatically. The API provides 35 endpoints covering core functionality including get current user, get user, list teams.
Call GET /users/me to get current user
Automated Boxes Management
Automate boxes operations by combining multiple Streak CRM API endpoints. Agents can get user and then list teams in a single workflow.
Call GET /users/{userKey} to get user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Streak CRM 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 'get current user', load the operation schema, and execute with Jentic-managed credentials
35 endpoints — streak crm api for managing pipelines, boxes, stages, fields, and email threads in gmail.
METHOD
PATH
DESCRIPTION
/users/me
Get current user
/users/{userKey}
Get user
/teams
List teams
/teams/{teamKey}
Get team
/pipelines
List pipelines
/pipelines/{pipelineKey}
Update pipeline
/pipelines/{pipelineKey}
Get pipeline
/pipelines/{pipelineKey}
Delete pipeline
/users/me
Get current user
/users/{userKey}
Get user
/teams
List teams
/teams/{teamKey}
Get team
/pipelines
List pipelines
/pipelines/{pipelineKey}
Update pipeline
/pipelines/{pipelineKey}
Get pipeline
/pipelines/{pipelineKey}
Delete pipeline
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Streak CRM by hand means setting up its HTTP basic auth with your API key as the username, then managing pagination across pipelines, boxes, and teams yourself. Through Jentic you install once, import the Streak CRM API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Streak puts the pipeline key in the URL path (/pipelines/{pipelineKey}), so a rule can pin your agent to one pipeline: it can read and update that pipeline and nothing else. You choose the operations it may call, so destructive ones like deleting a pipeline are not included unless you add them.
Credential isolation
Your Streak basic 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 the current user' or 'list pipelines', and Jentic returns the matching Streak 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 Streak CRM API through Jentic.
What authentication does the Streak CRM API use?
The Streak CRM 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 get current user with the Streak CRM API?
Yes. Use the GET /users/me endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Streak CRM 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 current user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current user'. Jentic returns the matching Streak CRM API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Streak CRM API have?
The Streak CRM API exposes 35 endpoints covering boxes, fields, files operations.
Can I limit what my agent is allowed to do with the Streak CRM API?
Yes. Because Jentic One is self-hosted, your own rules decide which Streak operations and credentials the agent may use. Since Streak puts the pipeline key in the URL path (/pipelines/{pipelineKey}), you can pin the agent to a single pipeline so it only reads and updates that one and nothing else. You choose the exact operations it may call, so destructive actions like DELETE /pipelines/{pipelineKey} stay out of reach unless you explicitly grant them.
For Agents
Programmatically get current user, get user. Covers 35 operations with basic authentication.
Use for: I need to current user, I want to user, Search for teams, Find all team
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Streak CRM API for managing pipelines, boxes, stages, fields, and email threads in Gmail. The API exposes 35 endpoints secured with basic authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>