# Try it without signing up

**There is a live register you can read right now, and an agent can check an
action against it.** It belongs to an invented company, it is read-only, and
nothing in it is any real customer's.

## What it is

Quillon Workforce Analytics is a made-up mid-market workforce analytics
platform of about 600 people. Its register holds **33 claims** — prices, terms,
certifications, capabilities and roadmap dates — with owners and dates, **one
contradiction**, **two still waiting for somebody to accept them**, and **one
whose owner has left**.

**Those flaws are deliberate.** A demo where every claim is current and owned
shows you a tidy list; this one shows you what a register looks like three
months in, which is the thing worth looking at.

## Connect to it

```
endpoint   https://app.reynforce.com/t/demo/mcp
header     Authorization: Bearer <the demo key>
```

The key is published on `/docs`. **It is not a secret and we do not treat it as
one** — what keeps it harmless is the workspace it names, which no real company
can ever be given, and the two things an agent key is allowed to do.

| tool | |
|---|---|
| `search_claims` | read the register. A claim's status comes back with it, so you can tell a current claim from a stale one |
| `check_action` | ask whether an action is permitted, and get back allowed, escalate or blocked |

**There is no third tool.** Adding a claim needs `register:write`, which an
agent key cannot hold — so the demo is read-only because of how the product
works rather than because of a setting on the demo.

## What to try

1. **Search for `single sign-on`.** Two of their claims disagree about which
   plans include it, and the register holds **both** — because retiring one
   side of an argument before anybody has settled it would hide the
   disagreement rather than resolve it. Both come back `contested`, which is
   one of the three states an agent may not cite.
2. **Cite `reg_slack_digest` in a check.** Its owner has left. Nobody deleted
   the claim; it simply stopped having anyone behind it, and it comes back
   `unowned` — which is the state the register exists to make visible rather
   than one anybody chose.
3. **Check an action that cites any of those.** The answer is `escalate`, and
   the agent's instruction is to tell the buyer it is checking — never to
   answer around it.
4. **Read `not_checked` in the answer.** `allowed` with that list non-empty
   means something was not evaluated, which is not the same as passed.
5. **Try to add a claim.** You cannot, and the refusal names the scope you
   would need.

## The limits

**30 calls a minute from one caller.** It is a demonstration rather than free
infrastructure; a workspace of your own has no limit like that.

**It is read-only, so there is nothing to reset.** Nothing you do leaves a
mark on it, because the two things an agent key can do are read a claim and ask
permission — and asking permission writes a record of the asking in the demo's
own ledger, which is the product working rather than the demo leaking.

## What it is not

It is **not** a trial. A trial is your own workspace with your own claims, and
`/request-access` is one form. This is a fixed, invented company that everybody
sees the same version of — which is what makes it safe to publish a key for.