# What should an agent trust in a passing result?

Trust the result only within the submitted policy and documented checker behavior. Supplied records are unverified; receipt verification depends on configured keys and its stated scope. Production signing is off in this release. The checker does not persist request bodies, but that does not mean hosting-level request metadata is absent. No SLA is included.

- [Limits and errors](https://curbi.io/developers/#limits)
- [Public verification keys](https://curbi.io/.well-known/curbi-receipt-keys.json)

Updated 2026-10-27. Public access.

## Try a configured check

This public example checks a reply against a configured price; it does not authorize an action or establish a provider outcome.

```sh
curl -sS https://api.curbi.io/v1/check \
  -H 'Content-Type: application/json' \
  -d '{"policy":{"prices":[{"item":"Starter","amount":49}]},"reply":"Starter is $99."}'
```

Expect `pass: false` with `price:mismatch`.

Next: [install a framework adapter](https://curbi.io/connect/) or [start with a working policy](https://curbi.io/policies/).