Any agent works with Provely. Every agent connects through four surfaces: the REST API, the MCP server, the CLI, and the SDKs. Each target is one profile plus guidance files.

No agent forks the core. A new agent needs a profile and rendered guidance, not code.

AgentKindMCPCLIHooksCI gateVerified on
Claude Codecoding agentSupportedSupportedSupportedyes2026-09-05
Codexcoding agentVerify at implementationSupportedVerify at implementationyes2026-09-05
Cursorcoding agentVerify at implementationSupportedVerify at implementationyes2026-09-05
Generic agentagentSupportedSupportedNot supportedyes2026-09-05
Grokautonomous agentVerify at implementationSupportedNot supportedyes2026-09-05
Hermesautonomous agentSupportedSupportedNot supportedyes2026-09-05
LangGraphagent frameworkSupportedSupportedNot supportedyes2026-09-05
OpenAI Agents SDKagent frameworkSupportedSupportedSupportedyes2026-09-05
OpenClawautonomous agentVerify at implementationSupportedNot supportedno2026-09-05
picoding agentNot supportedSupportedVerify at implementationyes2026-09-05

What does every agent do, on every surface?

  1. begin(contract, input) returns an operation id and the correlation and idempotency metadata.
  2. The agent does the side-effecting action with that metadata.
  3. action_result(operation_id) submits the provider acknowledgement.
  4. verify(operation_id) returns VERIFIED, PENDING, CONTRADICTED, FAILED, or UNVERIFIABLE.
  5. status and receipt resume the operation later and fetch the signed receipt.

The agent is untrusted. An agent report is E0, which is never sufficient. No surface gives an agent the verifier credentials.