canonical: https://jentic.com/apis/progress.com/progress

# Progress Corticon Decision Service API

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.

## For AI agents

Programmatically execute a decision service, execute batch decision service. Covers 12 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Execute a decision service
- List deployed decision services
- Get decision service details
- Undeploy a decision service
- Deploy a decision service

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Decision Execution** — Operations related to Decision Execution
- **Monitoring** — Operations related to Monitoring
- **Rules** — Operations related to Rules
- **Server Management** — Operations related to Server Management

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.