Core

Name: Core API
Brand: Core
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey30 EndpointsREST

For Agents

Programmatically retryevent, listexecutions. Covers 30 operations with apiKey authentication.

Use for: I need to retryevent, I want to listexecutions, Search for retryexecutions, Find all getexecution

Connect the Core to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Core, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Core API.

RetryEvent

ListExecutions

RetryExecutions

GetExecution

ListExecutionFaults

GET STARTED

Start building with Core API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Core API for, with concrete tasks.

★ Developer Tools Operations

Use the Core to perform developer tools operations programmatically. The API provides 30 endpoints covering core functionality including retryevent, listexecutions, retryexecutions.

Call POST /events/{eventId}/retry to retryevent

Automated Events Management

Automate events operations by combining multiple Core endpoints. Agents can listexecutions and then retryexecutions in a single workflow.

Call GET /executions to listexecutions, then verify the result

AI Agent Integration via Jentic

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

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

Key Endpoints

30 endpoints — stedi.

METHOD

PATH

DESCRIPTION

POST

/events/{eventId}/retry

RetryEvent

GET

/executions

ListExecutions

POST

/executions/retry

RetryExecutions

GET

/executions/{executionId}

GetExecution

GET

/executions/{executionId}/faults

ListExecutionFaults

GET

/executions/{executionId}/input

GetExecutionInputDocument

GET

/executions/{executionId}/input-url

GetExecutionInputDocumentUrl

GET

/executions/{executionId}/metadata

GetExecutionMetadataDocument

POST

/events/{eventId}/retry

RetryEvent

GET

/executions

ListExecutions

POST

/executions/retry

RetryExecutions

GET

/executions/{executionId}

GetExecution

GET

/executions/{executionId}/faults

ListExecutionFaults

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Core apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'retryevent') and Jentic returns the matching Core operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Core integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Core API through Jentic.

What authentication does the Core use?

The Core uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I retryevent with the Core?

Yes. Use the POST /events/{eventId}/retry endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Core?

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 retryevent through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'retryevent'. Jentic returns the matching Core operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Core have?

The Core exposes 30 endpoints covering events, executions, fragments operations.