Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Infinity 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%2Fstartinfinity.com%2Fstartinfinity" | 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%2Fstartinfinity.com%2Fstartinfinity" | 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 Infinity API.
Get user profile
List workspaces
Create board
Query and filter Infinity API records by parameters
Monitor Infinity API operational status and events
GET STARTED
Patterns agents use Infinity API for, with concrete tasks.
★ Productivity Operations
Use the Infinity API to perform productivity operations programmatically. The API provides 42 endpoints covering core functionality including get user profile, list workspaces, create board.
Call GET /api/v2/profile to get user profile
Automated Profile Management
Automate profile operations by combining multiple Infinity API endpoints. Agents can list workspaces and then create board in a single workflow.
Call GET /api/v2/workspaces to list workspaces, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Infinity 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 bearer tokens manually.
Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials
42 endpoints — the infinity api allows you to interact with your infinity workspaces, boards, items, and more.
METHOD
PATH
DESCRIPTION
/api/v2/profile
Get user profile
/api/v2/workspaces
List workspaces
/api/v2/workspaces/{workspace}/boards
Create board
/api/v2/workspaces/{workspace}/boards
List boards
/api/v2/workspaces/{workspace}/boards/{board}
Get board
/api/v2/workspaces/{workspace}/boards/{board}/attributes
Create attribute
/api/v2/workspaces/{workspace}/boards/{board}/attributes
List attributes
/api/v2/workspaces/{workspace}/boards/{board}/attributes/{attribute}
Get attribute
/api/v2/profile
Get user profile
/api/v2/workspaces
List workspaces
/api/v2/workspaces/{workspace}/boards
Create board
/api/v2/workspaces/{workspace}/boards
List boards
/api/v2/workspaces/{workspace}/boards/{board}
Get board
/api/v2/workspaces/{workspace}/boards/{board}/attributes
Create attribute
/api/v2/workspaces/{workspace}/boards/{board}/attributes
List attributes
/api/v2/workspaces/{workspace}/boards/{board}/attributes/{attribute}
Get attribute
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Infinity API by hand means setting up its bearer auth, sending the required X-API-Version header on every request, and threading workspace and board ids through the boards and attributes calls yourself. Through Jentic you install once, import the Infinity API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Infinity puts the workspace and board ids in the URL path (/api/v2/workspaces/{workspace}/boards/{board}/...), so a rule can pin your agent to one board: it can read and manage attributes on that board and nothing else. You choose the operations it may call, so board creation is not included unless you add it.
Credential isolation
Your Infinity 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 'get the user profile' or 'list boards in a workspace', and Jentic returns the matching Infinity 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 Infinity API through Jentic.
What authentication does the Infinity API use?
The Infinity API uses a Bearer token 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 Infinity API?
Yes. Use the GET /api/v2/profile endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Infinity 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 Infinity API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Infinity API have?
The Infinity API exposes 42 endpoints covering profile, workspaces, boards operations.
Can I limit what my agent is allowed to do with the Infinity API?
Yes. Because you run Jentic One yourself, your own rules decide which Infinity operations and credentials the agent may use. Infinity puts the workspace and board ids in the URL path, such as /api/v2/workspaces/{workspace}/boards/{board}/attributes, so you can pin the agent to a single board and let it only read and manage attributes there. You choose the operations it may call, so board creation stays off limits unless you explicitly allow it.
For Agents
Programmatically get user profile, list workspaces. Covers 42 operations with bearer authentication.
Use for: I need to user profile, I want to workspaces, Search for board, Find all boards
Not supported: Does not handle payments, communications, or crm - use for productivity only.
The Infinity API allows you to interact with your Infinity workspaces, boards, items, and more. Build integrations to automate your project management workflows. The API exposes 42 endpoints secured with bearer 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>