Crucible

Name: Crucible API
Brand: Crucible
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlsession79 EndpointsREST

For Agents

List projects, browse repositories, create code reviews, post review comments, and manage Crucible review lifecycles on a local Crucible instance.

Install Jentic One Beta

Connect the Crucible to your agent

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

List projects and repositories on the Crucible instance

Browse repository content, change history, and individual revisions

Create code reviews and attach changesets, files, or patches to a review

Post general or line-anchored comments on a review and reply within threads

GET STARTED

Start building with Crucible API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Crucible API for, with concrete tasks.

★ Automated Review Creation from CI

Open a Crucible review automatically when a CI build attaches the relevant changeset by calling POST /rest-service/reviews-v1 to create the review and POST /rest-service/reviews-v1/{id}/addChangeset to attach the changes. Engineering teams using Crucible alongside an on-prem build pipeline use this so every release branch produces a review record without a developer creating it by hand. POST /rest-service/reviews-v1/{id}/close finishes it once approvals land.

Create a Crucible review titled 'Release 2.4 hotfix' and attach changeset CR-1234 to it via /addChangeset

Review Comment Aggregation

Pull every review's comments into a reporting database by listing reviews via /rest-service/reviews-v1/filter, then calling /rest-service/reviews-v1/{id}/comments per review. Engineering management teams use this to surface review velocity, blockers, and outstanding comment threads without depending on the Crucible UI.

List reviews matching the 'open' filter and pull every comment from each via /reviews-v1/{id}/comments

Repository Browsing and History

Surface repository content and change history outside Crucible's UI by calling /rest-service/repositories-v1/browse/{repository}/{path}, /content/{repository}/{revision}/{path}, and /history/{repository}/{revision}/{path}. This is useful when integrating Crucible's view of the source tree into another tool or chat surface.

Browse the contents of repository core at path src/main/java and list the files at HEAD

AI Agent Review Triage

An AI agent triages a backlog of open Crucible reviews through Jentic. The agent searches for the crucible_filter_reviews operation, executes against the user's vaulted Crucible session credentials, and produces a ranked list of reviews most in need of attention based on age, comment count, and reviewer load. Jentic isolates the session credential so the agent never sees the raw login.

Use the Jentic SDK to log in to Crucible, list open reviews, and rank them by oldest unanswered comment

Key Endpoints

79 endpoints — crucible is atlassian's on-premise code review product, used by teams that hold their source control inside the firewall.

METHOD

PATH

DESCRIPTION

POST

/rest-service/auth-v1/login

Establish a Crucible session

POST

/rest-service/reviews-v1

Create a new code review

POST

/rest-service/reviews-v1/{id}/addChangeset

Attach a changeset to a review

POST

/rest-service/reviews-v1/{id}/addFile

Attach a file to a review

POST

/rest-service/reviews-v1/{id}/comments

Why Jentic?

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

Setup

Wiring Crucible by hand means running its /rest-service/auth-v1/login exchange, holding the session for reuse, and posting review, changeset, and comment payloads yourself. Through Jentic you install once, import Crucible from the API Directory, store the username and password once, and your agent calls it.

Permission scoping

Crucible puts the review id in the URL path (/rest-service/reviews-v1/{id}/...), so a rule can pin your agent to one review: it can add changesets, files, and comments to that review and nothing else. You choose the operations it may call, so closing a review is not included unless you add it.

Credential isolation

Your Crucible username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time, including the login exchange. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Crucible review' or 'list open reviews', and Jentic returns the matching Crucible operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Crucible API through Jentic.

What authentication does the Crucible API use?

Crucible uses session-based authentication. Clients call POST /rest-service/auth-v1/login with username and password and reuse the resulting session cookie on subsequent requests. Through Jentic the username and password are held encrypted in the vault and Jentic handles the login exchange so the agent never sees the credentials.

Can I create a code review through the API?

Yes. POST /rest-service/reviews-v1 creates a review, and follow-up calls to /rest-service/reviews-v1/{id}/addChangeset, /addFile, or /addPatch attach the actual code under review. POST /rest-service/reviews-v1/{id}/close ends the review once it is approved.

How do I filter reviews by repository or status?

GET /rest-service/reviews-v1/filter accepts filter parameters and returns matching reviews; /filter/{filter} returns the reviews under a saved filter, and /search/{repository} narrows by repository. The /details variants return enriched review payloads.

How do I create a review through Jentic?

Search Jentic for 'create a Crucible review', load the operation schema for POST /rest-service/reviews-v1, and execute with the project key, title, and reviewer list. Jentic handles the login session so the agent doesn't need to manage cookies.

How many endpoints does the Crucible API expose?

Seventy-nine endpoints across authentication, projects, repository browsing, reviews, review actions and comments, and review search and filter operations.

Can I post a comment on a specific line of a review?

Yes. POST /rest-service/reviews-v1/{id}/comments creates a comment, and the /comments/versioned endpoint exposes file-and-line-anchored comments so an agent can attach feedback to specific code lines.

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

Yes. Because your Jentic One instance is self-hosted, your own rules decide which Crucible operations the agent may call and which credentials it may use. Since Crucible puts the review id in the URL path (/rest-service/reviews-v1/{id}/...), you can pin the agent to a single review so it can add changesets, files, and comments to that review and nothing else. Closing a review via /rest-service/reviews-v1/{id}/close is not included unless you explicitly allow it.

Crucible

Connect the Crucible to your agent

Capabilities

Start building with Crucible API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs