> For the complete documentation index, see [llms.txt](https://docs.libum.io/nexum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libum.io/nexum/changelog.md).

# Changelog

## June 2026

* Added a protected MCP server at <mark style="color:purple;">`/mcp/`</mark> for agent-based NaaS and SymXchange workflows
* Added MCP discovery tools for capabilities, configured Syms, SymXchange services, record types, and compact operation schemas
* Added MCP read tools for getting, listing, and searching SymXchange records
* Added MCP FindBy support for global account searches such as last-name, SSN, MICR, and other <mark style="color:purple;">`findBy*`</mark> operations
* Added MCP PowerOn execution support, including standard and MCW PowerOn operations when write tools are enabled
* Added MCP transaction workflows for posting, reversing, and transaction lookups when enabled for the deployment
* Added MCP domain tools for user management, ECAA authentication, file upload/download, batch jobs, balancing, credit reports, and cash-machine operations
* Added MCP NaaS utility tools for health, keep-alive, host configs, connection status, and supported services
* Added optional MCP write tools for create, update, and delete record workflows when explicitly enabled
* Added SymXchange credential forwarding for MCP via <mark style="color:purple;">`X-NaaS-SymX-Credentials`</mark>
* Added configurable MCP enablement and write gating through NaaS configuration

## December 2025

* Added WSDL caching and SymXchange type generation
* Added generated types for all SymXchange `2022.01` services
* Added generated types for SymXchange `2018.01` through `2021.01` services
* Added generated types for persistent SymXchange endpoints
* Added typed OpenAPI response models for utility endpoints
* Added dynamic type registry support with service discovery

## August 2025

* Improved logging and request diagnostics
* Tuned health check thresholds and ALB health behavior

## July 2025

* Added the main API key requirement
* Added passthrough request tests and message ID logging
* Added passthrough authentication fixes
* Fixed protocol selection for passthrough routes
* Improved preflight request handling and logging

## June 2025

* Added retry logic for initialization and service calls
* Added unique instance ID checks during startup

## May 2025

* Added recurring health check jobs
* Updated health check behavior
* Added runtime identifiers to logs for better traceability

## March 2025

* Added Fargate execution support for NaaS
* Added container health checks and request-count based autoscaling
* Added support for running warmers across execution types

## December 2024

* Added retries for SOAP client creation
* Added a default timeout for SOAP client creation
* Added a custom logger with trace-level logging
* Improved stack trace logging for uncaught exceptions
* Reduced SOAP client creation log noise

## August 2024

* Switched to REST API Gateway
* Added custom HTTP client timeout support
* Added SymXchange connection status checks
* Improved invoke and passthrough error messaging
* Added API key generation image support

## July 2024

* Added supported-services route
* Added self-hosted image generation for multiple architectures
* Added logging for passthrough requests
* Added default tenant identifier handling for passthrough routes
* Added support for switching SymXchange calls to HTTP where required
* Patched SOAP parsing for SymXchange `Version_` elements
* Improved traceback and error logging

## June 2024

* Rebuilt NaaS on the Python/FastAPI runtime
* Added direct SymXchange connection support
* Added async request handling
* Added case-insensitive routes
* Added correlation IDs, timing middleware, and structured error handlers
* Added CORS headers to SymXchange responses
* Added passthrough routes
* Added Form URLEncoded request support
* Added custom field support
* Added <mark style="color:purple;">`/health`</mark> endpoint for NaaS status
* Added auth to passthrough routes
* Added support for <mark style="color:purple;">`/persistent`</mark> SymX services
* Fixed dynamic namespacing for recursive child elements
* Improved Datadog logging and health invocation handling

## March 2024

* Added support for Dynamic Custom Logging fields
* Updated default response formatting

## February 2024

* Added more performance improvements
* Improved graceful logging behavior

## January 2024

* Added major performance improvements
* Added asymmetric API key verification
* Added request ID logging on errors

## October 2023

* Added Form URLEncoded content-type support to NaaS
* Added support for nested fields in Form URLEncoded requests
* Added SymXchange native passthrough mode to capture external vendor logs


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.libum.io/nexum/changelog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.