# Provely > Provely verifies that an AI agent action reached the promised outcome before the agent reports success. The agent does the action. A separate verifier reads the provider and signs an Ed25519 receipt. Canonical site: https://provely.sh Last reviewed: 2026-09-05 Every page has a Markdown twin at the same path with the .md suffix. The full text of the key pages is in /llms-full.txt. The machine-readable claims are in /facts. ## Product - [Provely: outcome verification for AI agents](https://provely.sh/index.md): An agent says "done" when it is not. Provely checks the outcome against the provider before the agent reports success, and signs a receipt. - [How Provely verifies an agent action](https://provely.sh/how-it-works.md): Provely keeps intent, action, acknowledgement, outcome, and completion apart, runs one frozen state machine, and ranks evidence from E0 to E5. - [Completion contracts: the definition of done](https://provely.sh/contracts.md): A completion contract is a versioned document that states which evidence proves one outcome. Read the schema and a worked Stripe refund example. - [Evidence receipts: signed proof of a verdict](https://provely.sh/receipts.md): A receipt names the contract, its version and hash, the evidence, the observations, and the verdict. It is signed with Ed25519. Validate it offline. - [The false-completion benchmark](https://provely.sh/benchmark.md): The benchmark lists the cases where an agent action looks done and is not. Every skill must pass all of them with zero false VERIFIED before it ships. - [Provely pricing: plans per verified action](https://provely.sh/pricing.md): Every plan carries every feature. Developer is free with 1,000 verified actions a month. Startup is $99, Pro is $249, Team is $499. - [Provely changelog](https://provely.sh/changelog.md): What changed in Provely, newest first: the public website, the platform shell, the engines, and the core model. Subscribe with the RSS feed. - [About Provely and Macleod Labs](https://provely.sh/about.md): Macleod Labs builds Provely, a workflow verifier for AI agents. This page names the company and the one contact address. - [Provely terms of service](https://provely.sh/terms.md): The agreement between Macleod Labs and the customer who uses Provely. It covers accounts, credentials, fees, and liability. - [Provely privacy policy](https://provely.sh/privacy.md): What personal data Provely collects, why it collects it, how long it keeps it, who it shares it with, and how to exercise your rights. - [Sign in to Provely](https://provely.sh/signin.md): Sign in with Google or GitHub to verify your first workflow. The free plan verifies 1,000 actions and needs no card. ## Verified services - [Verified services: Stripe, Shopify, Resend](https://provely.sh/verify.md): One page for each service Provely verifies. Each page comes from the signed skill manifest: the completion levels, the lifecycle, the certification. - [Verify Resend actions with Provely](https://provely.sh/verify/resend.md): Was the email sent, or was it delivered? The 4 completion levels, the Resend lifecycle, and the evidence Provely reads. Certification Community. - [Verify Shopify Admin API actions with Provely](https://provely.sh/verify/shopify.md): Does a Shopify Refund object mean the money went back? The 2 completion levels, the Shopify Admin API lifecycle, and the evidence Provely reads. - [Verify Stripe actions with Provely](https://provely.sh/verify/stripe.md): Does a Stripe refund object mean the money moved? The 2 completion levels, the Stripe lifecycle, and the evidence Provely reads. Certification Community. ## Contracts - [resend.email.accepted: the accepted contract](https://provely.sh/verify/resend/resend.email.accepted.md): Prove that Resend accepted the email request. Version 1.0.0, certification Community. Every condition and timing rule of the signed Resend skill. - [resend.email.bounced: the bounced contract](https://provely.sh/verify/resend/resend.email.bounced.md): Prove that the recipient mail server rejected the email. Version 1.0.0, certification Community. - [resend.email.delivered: the delivered contract](https://provely.sh/verify/resend/resend.email.delivered.md): Prove that the recipient mail server accepted the email. Version 1.0.0, certification Community. - [resend.email.sent: the sent contract](https://provely.sh/verify/resend/resend.email.sent.md): Prove that Resend handed the email to its sending infrastructure. Version 1.0.0, certification Community. - [shopify.refund.created: the created contract](https://provely.sh/verify/shopify/shopify.refund.created.md): Prove that Shopify holds a Refund record for the order. Version 1.0.0, certification Community. - [Contract: shopify.refund.financially_completed](https://provely.sh/verify/shopify/shopify.refund.financially_completed.md): Prove that the refund transaction succeeded at the gateway. Version 1.0.0, certification Community. - [stripe.refund.created: the created contract](https://provely.sh/verify/stripe/stripe.refund.created.md): Prove that Stripe holds a refund for the charge. Version 1.0.0, certification Community. Every condition and timing rule of the signed Stripe skill. - [stripe.refund.succeeded: the succeeded contract](https://provely.sh/verify/stripe/stripe.refund.succeeded.md): Prove that the refund reached the succeeded state. Version 1.0.0, certification Community. Every condition and timing rule of the signed Stripe skill. ## Agent integrations - [Agent integrations: Claude Code, Cursor, Codex](https://provely.sh/agents.md): Provely works with any agent through four surfaces: REST API, MCP server, CLI, and SDKs. One page per agent, with its guidance files and enforcement. - [Verify Claude Code actions with Provely](https://provely.sh/agents/claude-code.md): Connect Claude Code to Provely through the MCP server, the CLI, the REST API. The guidance files, the hooks, and the CI gate. - [Verify Codex actions with Provely](https://provely.sh/agents/codex.md): Connect Codex to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05. - [Verify Cursor actions with Provely](https://provely.sh/agents/cursor.md): Connect Cursor to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05. - [Verify Generic agent actions with Provely](https://provely.sh/agents/generic.md): Connect Generic agent to Provely through the MCP server, the CLI, the SDK, the REST API. The guidance files, the hooks, and the CI gate. - [Verify Grok actions with Provely](https://provely.sh/agents/grok.md): Connect Grok to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05. - [Verify Hermes actions with Provely](https://provely.sh/agents/hermes.md): Connect Hermes to Provely through the MCP server, the CLI, the SDK, the REST API. The guidance files, the hooks, and the CI gate. - [Verify LangGraph actions with Provely](https://provely.sh/agents/langgraph.md): Connect LangGraph to Provely through the MCP server, the CLI, the SDK, the REST API. The guidance files, the hooks, and the CI gate. - [Verify OpenAI Agents SDK actions with Provely](https://provely.sh/agents/openai-agents.md): Connect OpenAI Agents SDK to Provely through the MCP server, the CLI, the SDK, the REST API. The guidance files, the hooks, and the CI gate. - [Verify OpenClaw actions with Provely](https://provely.sh/agents/openclaw.md): Connect OpenClaw to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05. - [Verify pi actions with Provely](https://provely.sh/agents/pi.md): Connect pi to Provely through the CLI, the REST API. The guidance files, the hooks, and the CI gate. The profile was verified on 2026-09-05. ## Documentation - [Provely documentation](https://provely.sh/docs.md): The quick start, the TypeScript and Python SDKs, the provely CLI, the MCP server, and the REST API reference. Every page answers first. - [Quick start: verify a Stripe refund](https://provely.sh/docs/quick-start.md): Open an operation against stripe.refund.succeeded, make the refund call with the idempotency key, submit the result, and verify. Ten minutes. - [Intent compilation: prompt to contract](https://provely.sh/docs/intent-compilation.md): You pass the prompt, the context and the tools. Provely compiles a completion contract, you confirm it, and the receipt binds the ask to the promise. - [Verdicts, retries, and directives](https://provely.sh/docs/verdicts.md): What each verdict means and what an agent may do next. PENDING waits. FAILED retries with the first idempotency key. CONTRADICTED stops for a person. - [Integration compiler: one signed skill](https://provely.sh/docs/integration-compiler.md): The compiler reads a vendor schema, its documents, its events and its sandbox behaviour, then signs one skill. Six stages and six confidence dimensions. - [SDKs: TypeScript and Python](https://provely.sh/docs/sdks.md): The Provely SDKs are thin translators into one model: operation, contract, action result, verification, receipt. The types come from the schemas. - [CLI reference: the provely binary](https://provely.sh/docs/cli.md): provely is one static binary: verify and status drive an operation, receipt validate checks a receipt offline, and mcp serves the tools over stdio. - [MCP server: begin, verify, status, receipt](https://provely.sh/docs/mcp.md): The MCP server exposes four tools. Hosted mode uses HTTP with a bearer token. Local mode runs provely mcp over stdio. No tool takes an API key. - [API reference: the /v1 control plane](https://provely.sh/docs/api.md): The REST API is the only place verification happens: operations, action results, verify, receipts, events, contracts, skills, and usage under /v1. - [Version support: five version dimensions](https://provely.sh/docs/version-support.md): Provely tracks the provider API version, the event payload version, the SDK version, the protocol version, and the agent host version, each on its own. - [Security: the credential boundary](https://provely.sh/docs/security.md): The agent holds the action credentials. Provely holds read-only verifier credentials. No surface mixes them or returns a credential to an agent. ## Glossary - [Provely glossary](https://provely.sh/glossary.md): One-sentence definitions of the Provely terms: intent, action, acknowledgement, outcome, completion, correlation, idempotency, evidence level, verdict. - [Intent: Provely glossary](https://provely.sh/glossary/intent.md): What the user asked for, stated before any action. The Provely definition, with an example. - [Action: Provely glossary](https://provely.sh/glossary/action.md): What the agent attempted against the provider. The Provely definition, with an example. - [Acknowledgement: Provely glossary](https://provely.sh/glossary/acknowledgement.md): What the provider returned at once, such as HTTP 200 and an object. The Provely definition, with an example. - [Outcome: Provely glossary](https://provely.sh/glossary/outcome.md): The observable resulting state in the real system. The Provely definition, with an example. - [Completion: Provely glossary](https://provely.sh/glossary/completion.md): The outcome satisfies the completion contract. The Provely definition, with an example. - [Completion contract: Provely glossary](https://provely.sh/glossary/completion-contract.md): A machine-readable, versioned, hashable definition of done for one operation. The Provely definition, with an example. - [Completion level: Provely glossary](https://provely.sh/glossary/completion-level.md): One named promise of a service, proven by one contract. The Provely definition, with an example. - [Correlation: Provely glossary](https://provely.sh/glossary/correlation.md): The binding of evidence to the exact operation through keys such as a resource id. The Provely definition, with an example. - [Idempotency: Provely glossary](https://provely.sh/glossary/idempotency.md): The property that a retried request creates no second side effect. The Provely definition, with an example. - [Evidence level: Provely glossary](https://provely.sh/glossary/evidence-level.md): The rank of a piece of evidence by its independence from the action path, E0 to E5. The Provely definition, with an example. - [Verdict: Provely glossary](https://provely.sh/glossary/verdict.md): The result of one verification attempt: VERIFIED, PENDING, CONTRADICTED, FAILED, or UNVERIFIABLE. The Provely definition, with an example. - [PENDING: Provely glossary](https://provely.sh/glossary/pending.md): The verdict while an operation can still make progress. The Provely definition, with an example. - [UNVERIFIABLE: Provely glossary](https://provely.sh/glossary/unverifiable.md): The verdict when the evidence never became sufficient. The Provely definition, with an example. - [CONTRADICTED: Provely glossary](https://provely.sh/glossary/contradicted.md): The verdict when the evidence shows a different outcome than the intent. The Provely definition, with an example. - [False VERIFIED: Provely glossary](https://provely.sh/glossary/false-verified.md): A VERIFIED verdict for an outcome that did not happen. The highest-severity defect. The Provely definition, with an example. - [Evidence receipt: Provely glossary](https://provely.sh/glossary/receipt.md): A signed, machine-readable record of what was verified and how. The Provely definition, with an example. - [Service verification skill: Provely glossary](https://provely.sh/glossary/skill.md): A signed package of contracts, lifecycles, evidence channels, and tests for one provider. The Provely definition, with an example. - [Conformance: Provely glossary](https://provely.sh/glossary/conformance.md): The mandatory test matrix a skill must pass before certification. The Provely definition, with an example. - [Intent compilation: Provely glossary](https://provely.sh/glossary/intent-compilation.md): The step that turns a task in natural language into a completion contract. The Provely definition, with an example. - [Intent fidelity: Provely glossary](https://provely.sh/glossary/intent-fidelity.md): The agreement between what the user asked for and what the contract checks. The Provely definition, with an example. - [REQUIRES_REVIEW: Provely glossary](https://provely.sh/glossary/requires-review.md): The mark on a part of a task that no contract can check. The Provely definition, with an example. - [Drift: Provely glossary](https://provely.sh/glossary/drift.md): A change in a provider schema, docs, or behaviour that can change a contract. The Provely definition, with an example. ## Comparisons - [Comparisons: verification against other tools](https://provely.sh/compare.md): Honest comparisons of outcome verification with observability, LLM evaluation, and testing. Each answers a different question. Provely adds the verdict. - [Outcome verification against observability](https://provely.sh/compare/verification-vs-observability.md): Observability shows what your system did. Outcome verification decides whether the provider reached the promised state. They answer two questions. - [Outcome verification against LLM evaluation](https://provely.sh/compare/verification-vs-evaluation.md): LLM evaluation scores a model output against a rubric or a judge. Outcome verification reads the real state after a side effect. A judge is no proof. - [Outcome verification against testing](https://provely.sh/compare/verification-vs-testing.md): A test runs before release against fixtures and mocks. Outcome verification runs after each production action against the real provider. Use both. ## Machine surfaces - [Facts](https://provely.sh/facts): the contracts, levels, and certifications as JSON-LD. - [Sitemap](https://provely.sh/sitemap.xml): every route, once. - [Changelog feed](https://provely.sh/changelog.xml): the RSS feed.