Curbi / Evidence and limits
Inspect the record.
Know its limits.
Curbi makes agent action evidence portable and integration failures replayable. Each result has a scope: a configured rule check, a local regression, or a signature checked against keys you trust.
Available today.
| Surface | What runs | Boundary |
|---|---|---|
| Check API | Public HTTP checks replies against configured policy and supplied records. | A pass means no configured rule fired. It is not permission to act or independent confirmation of a provider write. |
| Hosted MCP | Read-only public access: six read-only tools | No provider mutations, private project access, deployments or production receipt signing. Client compatibility is listed on the MCP page. |
| Repair Lab and MCP Chaos | Local fixture replays, documented fault cases and runnable downloads. | Bounded examples with stand-in services. They do not repair arbitrary integrations or demonstrate a real payment provider outcome. |
| Curbi Proof and offline verifier | Open draft format, signature and Merkle proof verification, published conformance vectors. | Examples use test keys. Production signing is off, the published key set must be checked for current keys and validity dates, and the reference log is in memory. |
Read the validation, not a headline count.
The machine-readable release record names the release, API version and bounded validation scope. The changelog links the accompanying release notes. Earlier v28 validation recorded 122 checks; that is a baseline for that release, not a count of production guarantees or proof of the current release by itself.
Proof vectors can be run in your browser or checked from the standalone verifier download. A matching conformance result demonstrates behavior on those inputs. It does not establish every provider, model or framework combination.
What a verified bundle establishes.
A selected trusted key signed the included records, and inclusion proofs place those records under the signed checkpoint. Valid consistency proofs establish a prefix relationship with the compared earlier heads. A missing or invalid proof leaves that relationship unproven; it does not automatically establish issuer misconduct.
A signature authenticates the issuer’s statement. It does not independently prove a refund reached a customer, a door opened, or a calendar accepted a booking. The evidence source and your choice of trusted keys remain part of the trust boundary.
What still needs production evidence.
Public verification keys are published. Production signing is off. Durable public log evidence, witness comparisons and independently authenticated live provider results still require qualification. Public examples use labeled test evidence.
Run a check. Keep the result.
Check a reply Connect your agent →A pass means no configured rule fired. It grants no execution authority or provider-completion proof.