Progress Corticon Decision Service API
✓ Official Vendor SpecDeveloper ToolsSource Controlbasic12 EndpointsREST
For Agents
Programmatically execute a decision service, execute batch decision service. Covers 12 operations with basic authentication.
Use for: I need to execute a decision service, I want to execute batch decision service, Search for deployed decision services, Find all decision service details
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Progress Corticon exposes business rules as RESTful decision services. The API allows execution of decision services, management of rule assets, and monitoring of decision service deployments. Corticon Server provides a REST endpoint for invoking decision services deployed as web services. The API exposes 12 endpoints secured with basic authentication.
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.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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
Deploy a decision service
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
POST
/server/deploy
Deploy a decision service
GET
/server/status
Get server status
GET
/server/ruleflows
List available ruleflows
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Progress Corticon Decision Service API basic 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., 'execute a decision service') and Jentic returns the matching Progress Corticon Decision Service API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Progress Corticon Decision Service API 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
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED