Preview and verify

Preview shows the exact payload an agent receives — assembled by the same engine, against a real record, as you.

Run a preview

In the entity builder, click Preview in the header. Or, from the Entities page, 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
ViewFormatted · Markdown · JSON

The three views are three readings of the same payload. Formatted renders the markdown for the human doing the reviewing — 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 encoding. The same viewer serves brief and skill previews and the catalog preview, so every “what does the agent get” surface reads the same way.

Changing record or level re-assembles against the live database, with a token estimate alongside. Preview remembers your last level, view, and record per user; a deleted record is replaced with a recent one.

Where you launch from matters:

  • From the builder, preview shows the draft — including unsaved edits, flagged with an Includes unsaved changes badge. 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. A field with no value isn’t included in the output — if a curated field isn’t showing, the record is blank there, the field is below the requested level, or 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.

Understanding entity assembly

Preview is the fastest way to build a feel for how a payload comes together. Things that surprise people the first time:

  • Metrics have a minimum level. Below it, a metric is skipped. 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 list curation — to change the columns, edit the child entity.
  • Enrichments that fail are dropped, not shown as errors. Issues records an element_failure naming the element.
  • Preview runs as you. A curated field you can’t access won’t appear — and a colleague with different permissions gets a different payload from the same entity.

What’s next