Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blue REST 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%2Fblue.cc%2Fblue" | 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%2Fblue.cc%2Fblue" | 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 Blue REST API.
Create records, move them between lists, and search or count them in a workspace
Organise work into workspaces, lists, and custom databases with typed fields
Add comments to records and read their activity and field history
Build dashboards, charts, and reports over record data
Run automations with triggers and actions on a database
GET STARTED
Upload files to records through a presigned upload flow
Invite users to a workspace and manage their roles and assignments
Patterns agents use Blue REST API for, with concrete tasks.
★ Agent Record Management
An AI agent connected through Jentic keeps a Blue workspace tidy: it creates records from incoming requests, searches for duplicates before adding one, moves records between lists as their status changes, and adds a comment summarising what it did. Every operation is available as a single RPC call, so the agent chains them without learning resource-route conventions.
Search a workspace for an existing record, create one if none matches, move it to the 'In progress' list, and add a comment
Reporting and Dashboards
An operations team turns Blue records into live reporting by building charts on a dashboard and aggregating report data over a field. The Blue REST API exposes report, chart, and dashboard operations plus metric series, so an agent can assemble a status view without exporting data to a separate BI tool.
Create a chart on a dashboard from a database's records and aggregate a report over a chosen field
Database Automation
A team removes manual steps by configuring custom database fields and wiring an automation with a trigger and actions. When a record changes, Blue runs the automation, and the API also manages the fields, options, and views the automation depends on. An agent can set this up end to end from the field configuration through the automation.
Create a database field, then create an automation that fires when that field changes and performs an action
123 endpoints — the blue rest api manages work across workspaces, lists, records, and custom databases.
METHOD
PATH
DESCRIPTION
/list-workspaces
List workspaces
/create-record
Create a record
/search-records
Search records in a workspace
/move-record
Move a record to another list
/add-comment
Add a comment to a record
/aggregate-report
Aggregate a report over a field
/create-automation
Create an automation
/list-databases
List databases in a workspace
/list-workspaces
List workspaces
/create-record
Create a record
/search-records
Search records in a workspace
/move-record
Move a record to another list
/add-comment
Add a comment to a record
/aggregate-report
Aggregate a report over a field
/create-automation
Create an automation
/list-databases
List databases in a workspace
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Blue REST API by hand means managing a Personal Access Token, sending the `blue-org-id` scope header on every call, and learning both the RPC and resource-style routes plus the presigned upload flow. Through Jentic you install once, import the Blue REST API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Blue offers every operation as an RPC call that carries the workspace and record ids in the request body, so a rule bounds which operations your agent may call, not which workspace. You choose the operations it may call, so destructive ones like delete-record, remove-workspace-member, and manage-automation are not included unless you add them.
Credential isolation
Your Blue Personal Access Token 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 'create a record' or 'search a workspace', and Jentic returns the matching Blue 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 Blue REST API through Jentic.
What authentication does the Blue REST API use?
The Blue REST API authenticates with a bearer Personal Access Token in the Authorization header, and requests are scoped with the `blue-org-id` header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context.
Can I search and move records with the Blue REST API?
Yes. You can search records within a workspace, count them, create and update them, and move a record between lists. Each is available as a single RPC call, so an agent can find a record, reposition it, and comment on it in sequence.
What are the rate limits for the Blue REST API?
The OpenAPI spec does not specify numeric rate limits for the Blue REST API. Check https://blue.cc for the current limits that apply to your plan before running bulk record or report operations.
Is there a Blue MCP server?
You don't need an MCP server to give your agent the Blue REST API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls it. Operations are discovered on demand, so your agent's context stays lean instead of loading a separate server's tool definitions.
Can I limit what my agent is allowed to do with the Blue REST API?
Yes. Write a rule that allows only the read operations, such as listing and searching records and reading reports, and leave out destructive ones like delete-record, remove-workspace-member, and manage-automation. The agent can then report on a workspace without changing it, and every call it makes is logged.
How do I create a record through Jentic?
Import the Blue REST API from the Jentic API Directory, store your Personal Access Token once, and have your agent search Jentic for 'create a record'. Jentic returns the create-record operation with its input schema so the agent sends the `workspaceId` and `title` and reads back the new record. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Manage Blue work: create, move, and search records across workspaces and lists, add comments, configure databases and custom fields, build reports and charts, run automations, and upload files.
Use for: Create a record titled 'Launch checklist' in a workspace, Move a record to another list, Search a workspace for records matching a query, Add a comment to a record
Not supported: Does not handle billing, time tracking, or video calls. Use for managing records, workspaces, databases, and reports in Blue only.
The Blue REST API manages work across workspaces, lists, records, and custom databases. It creates records, moves them between lists, searches and counts them, and tracks their comments, activity, and field history. Beyond individual records it builds dashboards, charts, and reports over record data, configures custom fields and typed database fields, runs automations with triggers and actions, and handles file uploads through a presigned flow. Every operation is available as an RPC call, and core resources also expose resource-style routes.
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>