> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/about-xyo/core-paradigms-of-xyo/xyo-schema/example-test-payload-with-schema.md).

# Example: Test Payload with Schema

## Using a Test Payload with a Schema in XYO Development

When developing and testing modules in the XYO ecosystem (such as Sentinels, Archivists, or Diviners), developers often use **custom test schemas**.

**This allows them to safely validate system behavior without affecting real production data.**

### What Is a Test Payload?

A **Test Payload** is a simple payload structure created with:

* A custom schema (e.g., `network.xyo.test`)
* Test data values
* Minimal required fields for storage, retrieval, or query operations

This enables developers to focus on testing the **system flow** (insert ➔ retrieve ➔ validate) without needing a real-world schema like `network.xyo.transfer`.

### Example Test Payload

Here’s what a simple **Test Payload** might look like:

```typescript
const NETWORK_XYO_TEST = 'network.xyo.test' as const;

const testPayloads = [
  {
    schema: NETWORK_XYO_TEST,
    value: 1,
  },
  {
    schema: NETWORK_XYO_TEST,
    value: 2,
  },
];
```


---

# 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.xyo.network/about-xyo/core-paradigms-of-xyo/xyo-schema/example-test-payload-with-schema.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.