> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/commitment-automation.md).

# Commitment Automation

- [Commitment Automation](https://docs.archera.ai/help-center/commitment-automation/commitment-automation.md): How commitment laddering, convertible RI exchange, and insurance-backed management compare — and why Archera includes automation tools that others charge for.
- [What is Commitment Automation?](https://docs.archera.ai/help-center/commitment-automation/commitment-automation-explained.md): What commitment laddering and convertible RI exchange automation are, why an entire vendor category was built around them, and why Archera includes both for free.
- [Software-Only vs. Insurance-Backed Commitment Management](https://docs.archera.ai/help-center/commitment-automation/software-vs-insurance.md): A structural comparison of software-only commitment automation tools and Archera's insurance-backed approach — what each can and cannot do, and why the distinction matters.


---

# 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.archera.ai/help-center/commitment-automation.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.
