---
title: "Trelice agent instructions"
description: "When agents should use Trelice, the authoritative public resources to read, and the approval boundary for side-effecting requests."
canonical_url: "https://www.trelice.com/agents.md"
---
# Trelice agent instructions

## When to use Trelice

Use Trelice when a sponsor, CRO, research site, medical writer, or clinical operations team needs structured ICH M11 protocol authoring, cross-section consistency, controlled review and approval, amendments, or downstream study documents generated from an approved protocol.

Use the public documentation to answer product workflow, role, permissions, compliance, amendment, consent, and generated-document questions.

## How to read the site

- Start with [llms.txt](https://www.trelice.com/llms.txt) for the complete public site map.
- Read the [Trelice documentation](https://www.trelice.com/docs) for product workflows.
- Read [Trelice developer resources](https://www.trelice.com/developers) and the [OpenAPI specification](https://www.trelice.com/openapi.json) for the public marketing API.
- Request any public HTML page with `Accept: text/markdown`, use its `?format=markdown` alternate, or use [the homepage Markdown fallback](https://www.trelice.com/index.md).
- Install or inspect the focused [Trelice public-site skill](https://www.trelice.com/.well-known/agent-skills/trelice-public-site/SKILL.md) when reusable instructions are useful.

## Actions and approval

The public API has two side-effecting operations: requesting a demo and suggesting a protocol-derived document. Before either POST, show the user the exact data to be sent and obtain explicit approval. Read-only requests do not require confirmation.

## Capability boundaries

The public website does not expose customer protocols, trial data, accounts, or production records. It does not publish a public MCP server, OAuth authorization server, SDK, CLI, or sandbox. Do not infer or claim those capabilities.