ProvelyStart with the quick start. It takes one Stripe refund from begin to a signed receipt. Then pick the surface your agent uses: the SDK, the CLI, the MCP server, or the REST API.
| Page | Purpose |
|---|---|
| Quick start | First verified outcome in under ten minutes. |
| Intent compilation | From an agent prompt to a signed completion contract. |
| Verdicts and retries | What each verdict means and what the agent may do next. |
| Integration compiler | How one vendor becomes one signed skill, in six stages. |
| SDKs | The TypeScript and Python SDKs and the canonical model. |
| CLI | The provely binary: scan, verify, status, receipt validate, mcp, init. |
| MCP server | The four tools: begin, verify, status, receipt. |
| API reference | The /v1 control plane endpoints. |
| Version support | How Provely tracks provider API, event, SDK, protocol, and agent host versions. |
| Security | The credential boundary: the agent writes, the verifier reads. |
What is the one loop every surface implements?
1. begin(contract, input) -> operation_id + correlation/idempotency metadata
2. act() -> the AGENT does the side-effecting action
3. action_result(operation_id) -> submit the provider acknowledgement
4. verify(operation_id) -> VERIFIED | PENDING | CONTRADICTED | FAILED | UNVERIFIABLE
5. status / receipt -> poll later; fetch the signed receipt