Claims
What your documents and your agents' work say about the people, companies and things you deal with, kept up to date, with the source of every detail.
In short
A claim is one specific detail about one thing, such as a customer's plan or a supplier's phone number, along with when it became true and where it came from. Your agent gets the claims that matter to each task, so it works from what is true now and can show its source.
What a claim is
Hyperstruck reads the documents you send and the work your agents finish, and picks out each specific detail they state about someone or something. Each detail becomes a claim, and every claim has the same parts:
| Part | What it holds |
|---|---|
| Entity | Who or what the claim is about: a person, a company, a product |
| Attribute | Which detail it is: a phone number, a plan, a delivery date |
| Value | The detail itself |
| Holds from | The date the detail became true |
| Source | The document, run or person it came from, and the exact passage |
Claims stay up to date
When a newer source clearly changes a detail, the new claim becomes the current one and the old one is kept as history, with its dates. Your agent gets the current value, and you can always see what it was before, or read everything as it stood on a past date.
When the two can't be linked, or an older source that doesn't say it replaces anything arrives after a newer one, both stay on record: the newest leads and the other reads "Also on record".
All the claims about one detail of one entity, current and earlier, are called a line. The API returns one item per line.
Most details hold one value at a time. Some hold several at once, like the languages someone speaks; for those, a new claim adds a value instead of replacing the others.
Kinds of claim
Most claims are a plain value. A few kinds behave differently:
| Kind | What it records |
|---|---|
value | A detail that holds until it changes, like a customer's plan |
reading | A measurement at a point in time, like a weekly stock count. Each one keeps its own date |
obligation | Something someone owes, usually by a date. It stays open until it is done. See Obligations |
event | Something that happened on a date, like an inspection |
view | Someone's opinion, like "the renewal is at risk". It never replaces a value |
relation | A link between two entities, like a person working at a company |
Where claims come from
- Your documents. Send them with the Documents API, and every claim points back to the passage that says it.
- Your agents' finished work. When your agent reports a finished task, what its tools returned and what it found out become claims too.
- People and API keys. Anyone with curate access on the agent can add or correct a claim, and it is recorded as theirs: "corrected by Mei Tanaka on 28 October 2026".
How your agent uses claims
- Automatically. Before each task, resolve gives your agent the claims about the people and things the task mentions.
- By searching. Claims search takes a question in plain words and returns the claims nearest it. It is free.
- By looking up. The Claims API lists claims, shows everything about one entity, or shows what changed since a date.
Claims always reach your agent marked as reference material, never as instructions, so nothing written in a document can tell your agent what to do.
When something needs a person
Hyperstruck never guesses. If it cannot tell whether a source meant to change a detail, or someone tries to change a detail you have protected (a bank account, say), both versions are kept, the line reads conflicting, and the question waits for a person to settle. A bank account or PayID never leads until a person confirms it in the dashboard. When sources disagree explains how that works. To fix a mistake, merge duplicates or remove claims, see Correct and erase claims.