> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ambient.market/llms.txt
> Use this file to discover all available pages before exploring further.

# Records and history

> Understand public activity, participant outcomes, creator records, and replay.

Ambient records every market action that reaches its application boundary.
Different readers receive different views of that history.

## Public activity

Anyone can read:

```text theme={null}
GET /v1/markets/{marketId}/activity
```

This timeline shows safe lifecycle changes, counts, market states, and public
outcomes. It does not reveal participant identities, private bids, offers or
lottery evidence, commitment IDs, authority references or payment records.
Lottery activity includes publication, cancellation, recorded deadline extensions,
anonymous entries and withdrawals, entry closure, draw and resolution. Entry and
withdrawal events show timestamps with empty data; they reveal no entry IDs,
actor IDs or evidence. Candidate promotion and review decisions are omitted.

Use public activity to display what is happening in a market. Do not treat it
as the complete audit record.

## Participant outcome

An authenticated participant or its authorized agent can read:

```text theme={null}
GET /v1/markets/{marketId}/my-outcome
```

The MCP equivalent is `get_my_market_outcome`. It returns the represented
principal's own bid receipts, offer states, lottery entries and commitments
beside the public market snapshot. It never returns another participant's
private outcome.

Use this view to recover from a lost response or discover a result produced by
a later deadline.

## Creator record

The creator can read:

```text theme={null}
GET /v1/markets/{marketId}/record
```

The MCP equivalent is `get_market_record`. The record contains:

* the current market snapshot;
* accepted and deterministically rejected commands in server order;
* accepted transition events;
* current commitments;
* private offers for request-for-offers markets;
* entries and the finalized draw for resolved lotteries; and
* integrity metadata for the returned view.

The creator record is private. It is available to the creator principal or the
original creating actor while it still has current `market:create` authority.

For an open lottery, the complete record returns HTTP 403 even to its creator.
Use `get_lottery_review` or `GET /v1/markets/{marketId}/lottery-review` for selected
candidates until resolution. The complete record then includes the seed, full
order, entry identities and review history; no future alternate order is exposed
while reviews are open.

## Replay and integrity

Ambient can independently replay direct-claim, request-for-offers and lottery
records and compare the result with stored market, participant input, draw and
commitment state. These records report `stateReconstructed: true` when that
comparison succeeds.

Sealed-auction records already contain the complete ordered history and a
content hash. Independent reconstruction of the stored auction state is not
implemented yet, so those records report `stateReconstructed: false`.

The record hash identifies the exact returned content. It is not a signature,
external timestamp, or proof against an operator able to rewrite the database
and recompute the hash.

## What a record does not prove

The record establishes what Ambient received, decided, and committed under the
published rules. It does not by itself establish that:

* a listed good or service existed;
* a participant paid;
* external fulfillment occurred;
* an attendee checked in; or
* either party completed an off-platform obligation.

Those facts require evidence from the systems that perform them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.