Install Jentic One Beta

Connect the solidtime API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the solidtime 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%2Fsolidtime.io%2Fsolidtime" | sh

Step 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%2Fsolidtime.io%2Fsolidtime" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with solidtime API.

Create project

Get projects

Update project

Delete project

Monitor solidtime API operational status and events

Use Cases

GET STARTED

Start building with solidtime API

Explore with Jentic One

View OpenAPI Document

Automated Organization Management

Automate organization operations by combining multiple solidtime API endpoints. Agents can get projects and then get project in a single workflow.

Call GET /v1/organization/{organization}/projects to get projects, then verify the result

AI Agent Integration via Jentic

AI agents discover and call solidtime 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 oauth2 tokens manually.

Search Jentic for 'create project', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — solidtime.

METHOD

PATH

DESCRIPTION

POST

/v1/organization/{organization}/projects

Create project

GET

/v1/organization/{organization}/projects

Get projects

GET

/v1/organization/{organization}/projects/{project}

Get project

PUT

/v1/organization/{organization}/projects/{project}

Update project

DELETE

/v1/organization/{organization}/projects/{project}

Delete project

POST

/v1/organization/{organization}/time-entries

Create time entry

GET

/v1/organization/{organization}/time-entries

Get time entries

PUT

/v1/organization/{organization}/time-entries/{timeEntry}

Update time entry

POST

/v1/organization/{organization}/projects

Create project

GET

/v1/organization/{organization}/projects

Get projects

GET

/v1/organization/{organization}/projects/{project}

Get project

PUT

/v1/organization/{organization}/projects/{project}

Update project

DELETE

/v1/organization/{organization}/projects/{project}

Delete project

POST

/v1/organization/{organization}/time-entries

Create time entry

GET

/v1/organization/{organization}/time-entries

Get time entries

PUT

/v1/organization/{organization}/time-entries/{timeEntry}

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the solidtime API by hand means running its OAuth2 flow, choosing between the production app.solidtime.io host and the staging host, and threading the organization id through every projects and time-entries call yourself. Through Jentic you install once, import the solidtime API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The solidtime API puts resource ids in the URL path (/v1/organization/{organization}/projects/{project}, /v1/organization/{organization}/time-entries/{timeEntry}), so a rule can pin your agent to one organization and its projects: it can create and read there and nothing else. You choose the operations it may call, so destructive ones like deleting a project are not included unless you add them.

Credential isolation

Your solidtime 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 'create a project' or 'log a time entry', and Jentic returns the matching solidtime API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using solidtime API through Jentic.

What authentication does the solidtime API use?

The solidtime API uses OAuth 2.0 for authorization. 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 create project with the solidtime API?

Yes. Use the POST /v1/organization/{organization}/projects endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the solidtime 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 create project through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create project'. Jentic returns the matching solidtime API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the solidtime API have?

The solidtime API exposes 9 endpoints covering organization operations.

Can I limit what my agent is allowed to do with the solidtime API?

Yes. Because you self-host Jentic One, your own rules decide which solidtime operations and credentials the agent may use. Since the API carries resource ids in the URL path, such as /v1/organization/{organization}/projects/{project} and /v1/organization/{organization}/time-entries/{timeEntry}, you can pin the agent to a single organization and let it create and read projects and time entries there and nothing else. You choose the operations it may call, so destructive ones like deleting a project stay off unless you explicitly add them.

solidtime API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controloauth29 EndpointsREST

For Agents

Programmatically create project, get projects. Covers 9 operations with oauth2 authentication.

Use for: I need to project, I want to projects, Search for project, Find all project

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

solidtime.io/main version 0.0.1. The API exposes 9 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

90%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

44%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

69%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the solidtime API to your agent

Capabilities

Use Cases

Start building with solidtime API

Key Endpoints

Why Jentic?

Related APIs

FAQs

solidtime API

Jentic AI Readiness Score

solidtime API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness