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

# Validate

Task version: 1.0.0

Required Frends version: 5.5+

Required .NET version: 6.0

Compatible Agents: Crossplatform

Source code: <https://github.com/FrendsPlatform/Frends.JSON2>

## Task Parameters

{% tabs %}
{% tab title="Input" %}

| Name                  | Description                                                                                                                                                                              |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Json : `Object`       | <p>Json input needs to be of type string or JToken.</p><p><br>Default: <code>-</code><br>Example: <code>{"key":"value"}</code></p>                                                       |
| JsonSchema : `String` | <p>Json Schema to validate to. Uses Newtonsoft JsonSchema</p><p><br>Default: <code>-</code><br>Example: <code>{"type": "object", "properties": {"name": {"type":"string"} } }</code></p> |
| {% endtab %}          |                                                                                                                                                                                          |

{% tab title="Options" %}

| Name                           | Description                                                                                                                                      |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| ThrowOnInvalidJson : `Boolean` | <p>A flag to indicate whether an error should be thrown if JSON was invalid.</p><p><br>Default: <code>-</code><br>Example: <code>true</code></p> |
| {% endtab %}                   |                                                                                                                                                  |
| {% endtabs %}                  |                                                                                                                                                  |

## Task Result

| Name                     | Description                                                                            |
| ------------------------ | -------------------------------------------------------------------------------------- |
| Success : `Boolean`      | <p>Operation complete without errors.<br>Example: <code>true</code></p>                |
| IsValid : `Boolean`      | <p>JSON was valid.<br>Example: <code>true</code></p>                                   |
| Errors : `IList<String>` | <p>List of errors.<br>Example: <code>{ An error occured..., Another error }</code></p> |

## Task Changelog

Changelog for Task Frends.JSON.Validate.

### \[1.0.0] - 2023-06-15

#### Added

* Initial implementation


---

# 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.frends.com/tasks/tasks/json/validate.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.
