> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/sdks/features-overview.md).

# Features Overview

Purpose: provide or link to a document that lists features and which SDK(s) support each feature.

{% hint style="info" %}
This page is a placeholder that should either include the features document or link to it. Do not add feature data here unless it exists in the source document.
{% endhint %}

How to add the features document to this page:

* If the document exists as another GitBook page, include it with a content include (recommended for syncing across pages).
* If the document is an external URL or a downloadable file, add a link or embed it.
* If you want a simple reference, add a link to the document with query parameters preserved.

Examples

Include another GitBook page (replace the path with the actual page path):

```
{% include "/path-to-features-document" %}
```

Embed an external URL (e.g., a public document or page — replace URL with the actual link):

{% embed url="<https://example.com/path-to-features-document>" %}

Link to an external document (keeps all query parameters intact):

[Features and SDK support — external document](https://example.com/path-to-features-document?keep=params)

If you prefer to keep the content on this page, add the feature list in a clear structure such as a table:

```
| Feature | Supported SDK(s) |
|---------|------------------|
| <Feature name> | <SDK A>, <SDK B> |
```

Or use headings per feature with SDK details underneath:

```
## Feature name

Supported SDK(s):
- SDK A
- SDK B
```

Next steps

{% stepper %}
{% step %}

### Add an include

1. Create or locate the document that lists features and SDK mappings.
2. Place it in the desired GitBook path.
3. Replace the include path above with the real path.
   {% endstep %}

{% step %}

### Or add an external link/embed

1. Verify the external URL and query parameters.
2. Replace the embed or link example above with the real URL.
   {% endstep %}
   {% endstepper %}

FAQ

<details>

<summary>What if I only have a spreadsheet?</summary>

You can export the spreadsheet to Markdown or a public URL and then use one of the methods above (include, embed, or link).

</details>

<details>

<summary>Can I convert a numbered list of steps to a stepper?</summary>

Yes — long numbered steps are better represented with the stepper block. Use the stepper examples above.

</details>


---

# 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.licensespring.com/sdks/features-overview.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.