Install Jentic One Beta

Connect the RAIDLOG API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RAIDLOG 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%2Fraidlog.com%2Fraidlog" | 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%2Fraidlog.com%2Fraidlog" | 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 RAIDLOG API.

Logout

Get user profile

Replace user profile

Partial update user profile

GET STARTED

Start building with RAIDLOG API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use RAIDLOG API for, with concrete tasks.

★ Productivity Operations

Use the RAIDLOG API to perform productivity operations programmatically. The API provides 28 endpoints covering core functionality including login, logout, get user profile.

Call POST /users/login to login

Automated Users Management

Automate users operations by combining multiple RAIDLOG API endpoints. Agents can logout and then get user profile in a single workflow.

Call POST /users/logout to logout, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RAIDLOG 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 'login', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

28 endpoints — restful api for managing raidlog workspaces, projects, risks, actions, issues, decisions, and more.

METHOD

PATH

DESCRIPTION

POST

/users/login

POST

/users/logout

Logout

GET

/users

Get user profile

PUT

/users

Replace user profile

PATCH

/users

Partial update user profile

GET

/workspaces

List workspaces

GET

/workspaces/{uuid}

Get workspace by ID

PUT

/workspaces/{uuid}

Update workspace

POST

/users/login

POST

/users/logout

Logout

GET

/users

Get user profile

PUT

/users

Replace user profile

PATCH

/users

Partial update user profile

GET

/workspaces

List workspaces

GET

/workspaces/{uuid}

Get workspace by ID

PUT

/workspaces/{uuid}

Update workspace

Why Jentic?

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

Setup

Wiring the RAIDLOG API by hand means learning its bearer auth, choosing between the api.us.raidlog.com and api.eu.raidlog.com hosts, and handling retries across its user and workspace operations yourself. Through Jentic you install once, import RAIDLOG from the API Directory, store the token once, and your agent calls it.

Permission scoping

RAIDLOG puts the workspace uuid in the URL path (/workspaces/{uuid}), so a rule can pin your agent to one workspace: it reads and updates that workspace and nothing else. You choose the operations it may call, so a write like updating users is not included unless you add it.

Credential isolation

Your RAIDLOG 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 a workspace by id' or 'list workspaces', and Jentic returns the matching RAIDLOG operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RAIDLOG API through Jentic.

What authentication does the RAIDLOG API use?

The RAIDLOG 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 login with the RAIDLOG API?

Yes. Use the POST /users/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RAIDLOG 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 login through Jentic?

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

How many endpoints does the RAIDLOG API have?

The RAIDLOG API exposes 28 endpoints covering users, workspaces, tenants operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which RAIDLOG operations and credentials the agent may use. Because RAIDLOG carries the workspace uuid in the URL path (/workspaces/{uuid}), you can pin the agent to a single workspace so it reads and updates that one and nothing else. You also choose the exact operations it may call, so a write such as replacing a user profile via PUT /users stays out of reach unless you explicitly allow it.

RAIDLOG API

Name: RAIDLOG API
Brand: RAIDLOG API
Availability: InStock

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCollaborationbearer28 EndpointsREST

For Agents

Programmatically login, logout. Covers 28 operations with bearer authentication.

Use for: I need to login, I want to logout, Search for user profile, Find all replace user profile

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

RESTful API for managing RAIDLOG workspaces, projects, risks, actions, issues, decisions, and more. The API exposes 28 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

61%

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

75%

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: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RAIDLOG API to your agent

Capabilities

Start building with RAIDLOG API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

RAIDLOG API

Jentic AI Readiness Score

RAIDLOG 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