Preview and verify

Preview shows the exact payload an agent receives. The same engine assembles it, against a real record, running as you.

Run a preview

In the entity builder, click Preview in the header. Or, on Studio → Entities, choose Preview from an entity’s action menu.

ControlWhat it does
RecordSearch by name, or leave blank to preview a recent record of this object
LevelList · Standard · Detailed (360)
ViewFormatted · Markdown · JSON

The three views are three readings of the same payload. Formatted renders the markdown for the person reviewing it, and is the default. Markdown is the verbatim payload, byte for byte what the agent receives — whitespace, escaping and all. JSON is the same content in the JSON format, which is what a programmatic caller gets.

Changing the record or the level re-assembles against the live database and re-estimates the tokens. Preview remembers your last level and view, and remembers the record per object, so two entities on Opportunity both open on the record you were just looking at.

Where you launch from matters:

  • From the builder, preview shows the draft — including unsaved edits, badged Includes unsaved changes. Nothing is written until you Save, and nothing reaches agents until you Activate.
  • From the Entities page, preview shows the active version — exactly what agents receive right now.

NOTE

Preview runs as you, so your permissions shape it. A colleague with narrower access gets a thinner payload from the same entity — see Security.

What to check

  • Read it as the agent would — top to bottom, knowing nothing about your org. Is there enough to answer a real question?
  • Check every level. list is the most likely to be wrong: it’s also the columns this record shows as inside other payloads. Could someone identify the record from it?
  • Look for missing fields. The payload leaves out a field with no value, so a curated field that isn’t showing means the record is blank there, the field sits below the requested level, or your permissions stripped it.
  • Look for values you can’t interpret. If a picklist value or score needs explaining, add a field instruction.
  • Check the size. A detailed Account 360 is typically 400–900 tokens. Well past that, look for an unfiltered related list or a high Max Rows.

Notes

Why a payload looks the way it does:

  • Metrics have a minimum level. Below it, assembly skips the metric. The metric’s Available for also has to include this object.
  • Related lists render at detailed only.
  • A related list’s columns come from the child entity’s curation, at the level the list’s Columns setting names — list until you change it. To change the columns, edit the child entity.
  • An enrichment that fails drops out rather than showing as an error. Issues records an element_failure naming the element.

What’s next