✨ API and MCP Endpoint Configuration
Configure and manage API, MCP, and LogX integrations across the enterprise. Create, update, and maintain configurations with centralized control over endpoints, tools, servers, and operational intelligence.
API Existing Configurations
For API Actions Endpoint
Select the server where this API endpoint is hosted and managed.
Provide a business-friendly description of the endpoint.
This description should align with the Event Description and
AI functional behavior.
Enter the base API URL without parameters.
Example:
/api/manual_settle
Enter the API endpoint URL that will be invoked when the
selected action is executed.
Specify the action performed by this endpoint such as
create, update, retrieve, cancel, approve, settle, etc.
Determines how input parameters are passed to the API:
Path Parameters, Query Parameters, or Request Body.
Define all parameters required by the endpoint.
Example: trade_id, account_id, trade_date, settlement_date.
LogX Existing Configurations
Only if Log Based Exception Management is Needed
Select the server whose logs will be monitored for
exception detection and troubleshooting.
Describe the event or business process that should
trigger log analysis and exception monitoring.
Specify the log search query or pattern used to locate
relevant log entries. Use default to apply the
server's predefined search configuration.
Defines how far back LogX should search logs.
Example: 60 means logs from the last 60 minutes
will be analyzed.
Optional direct URL to the log management platform.
Users can navigate to this URL for detailed log
investigation and troubleshooting.
MCP Existing Configurations
For MCP Tool Actions
Select the server where the MCP tools and associated APIs
are hosted and executed.
Choose one or more MCP tools that can assist the AI in
processing requests, retrieving data, or executing actions.
Describe the MCP-enabled endpoint and the business function
it supports. This should align with the Event Description.
Enter the API endpoint URL that will be invoked when the
selected MCP tool executes an action.
Specify the operation performed by this endpoint such as
validation, lookup, retrieval, settlement, monitoring,
reconciliation, or execution.
Defines how request parameters are passed to the endpoint:
Path Parameters, Query Parameters, or Request Body.
Define the input parameters required by the MCP-enabled
endpoint. Examples include trade_date, account_id,
settlement_id, transaction_id, etc.