Progress Corticon Decision Service API

Name: Progress Corticon Decision Service API
Brand: Progress Corticon Decision Service API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbasic12 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Progress Corticon Decision Service API to your agent

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

Execute a decision service

List deployed decision services

Get decision service details

Undeploy a decision service

GET STARTED

Start building with Progress Corticon Decision Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Progress Corticon Decision Service API for, with concrete tasks.

★ Developer Tools Operations

Use the Progress Corticon Decision Service API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including execute a decision service, execute batch decision service, list deployed decision services.

Call POST /execute to execute a decision service

Automated Decision Execution Management

Automate decision execution operations by combining multiple Progress Corticon Decision Service API endpoints. Agents can execute batch decision service and then list deployed decision services in a single workflow.

Call POST /batch to execute batch decision service, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Progress Corticon Decision Service 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 basic tokens manually.

Search Jentic for 'execute a decision service', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

12 endpoints — progress corticon exposes business rules as restful decision services.

METHOD

PATH

DESCRIPTION

POST

/execute

Execute a decision service

POST

/batch

Execute batch decision service

GET

/server/decisionservices

List deployed decision services

GET

/server/decisionservices/{serviceName}

Get decision service details

DELETE

/server/decisionservices/{serviceName}

Undeploy a decision service

POST

/server/deploy

Deploy a decision service

GET

/server/status

Get server status

GET

/server/ruleflows

List available ruleflows

POST

/execute

Execute a decision service

POST

/batch

Execute batch decision service

GET

/server/decisionservices

List deployed decision services

GET

/server/decisionservices/{serviceName}

Get decision service details

DELETE

/server/decisionservices/{serviceName}

Undeploy a decision service

Why Jentic?

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

Setup

Wiring the Progress Corticon Decision Service API by hand means setting Basic auth, assembling the templated host and port (/{host}:{port}/axis/corticon), and mapping execute, deploy, and decision service calls yourself. Through Jentic you install once, import the Progress Corticon Decision Service API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Corticon puts the decision service name in the URL path (/server/decisionservices/{serviceName}), so a rule can pin your agent to a specific decision service. You choose the operations it may call, so a destructive one like DELETE on a service or a deploy is not included unless you add it.

Credential isolation

Your Progress Corticon Basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'execute a decision service' or 'check server status', and Jentic returns the matching Corticon operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 Progress Corticon Decision Service API through Jentic.

What authentication does the Progress Corticon Decision Service API use?

The Progress Corticon Decision Service API uses HTTP Basic authentication with username and password. 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 execute a decision service with the Progress Corticon Decision Service API?

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

What are the rate limits for the Progress Corticon Decision Service 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 execute a decision service through Jentic?

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

How many endpoints does the Progress Corticon Decision Service API have?

The Progress Corticon Decision Service API exposes 12 endpoints covering decision execution, monitoring, rules operations.

Can I limit what my agent is allowed to do with the Progress Corticon Decision Service API?

Yes. Because you run Jentic One yourself, your own rules decide which Corticon operations and credentials the agent may use. Since the decision service name sits in the URL path (/server/decisionservices/{serviceName}), you can pin the agent to a specific decision service and choose the exact operations it may call. That lets you allow read and execute calls like GET /server/decisionservices and POST /execute while withholding destructive ones such as DELETE on a service or POST /server/deploy unless you add them.