Any agent works with Provely, through four surfaces: the REST API, the MCP server, the CLI, and the SDKs. A new agent needs a profile and rendered guidance, never a fork of the core.

Each row below states the date a person last checked that host. Agent products change monthly, so re-verify a row before you build against it.

AgentKindMCPCLIHooksCI gateVerified on
Claude Codecoding agentSupportedSupportedSupportedyes2026-09-12
Codexcoding agentSupportedSupportedVerify at implementationyes2026-09-12
Cursorcoding agentSupportedSupportedSupportedyes2026-09-12
Generic agentagentSupportedSupportedNot supportedyes2026-09-08
GitHub Actionsworkflow toolNot supportedSupportedNot supportedyes2026-09-10
Grokautonomous agentSupportedSupportedVerify at implementationyes2026-09-08
Hermesautonomous agentVerify at implementationSupportedVerify at implementationyes2026-09-08
LangChainagent frameworkSupportedSupportedSupportedyes2026-10-10
LangGraphagent frameworkSupportedSupportedSupportedyes2026-09-08
OpenAI Agents SDKagent frameworkSupportedSupportedSupportedyes2026-09-08
OpenClawautonomous agentSupportedSupportedVerify at implementationno2026-09-08
picoding agentNot supportedSupportedVerify at implementationyes2026-09-08
Vercel AI SDKagent frameworkSupportedSupportedSupportedyes2026-10-06
the promptthe agenttool callStripe200 pendingthe agent reads the status code and stops“Done. The customer has beenrefunded $142.”an agent assertion is evidence level E0E0 is never sufficient on its ownNobody compares the claim with the record, so nobody finds the difference.
The agent sees its own tool call succeed. It never sees the outcome.
In words
  • A person asks the agent to perform the action.
  • The agent calls the provider and reads a success response.
  • The agent reports the task as done.
  • The provider state is still not the promised outcome.

What is an Agent Skill, and what is an integration?

An Agent Skill is a SKILL.md file that an agent loads and follows. Provely ships one for each host above, so your agent knows to verify before it claims done. An integration is the signed package that Provely compiles for one service, and it holds the completion contracts of that service.

Each integration also ships an Agent Skill of its own, so an agent knows how to call that one service. Read the integrations.

What does every agent do, on every surface?

begincontract + inputactthe agent, with the keyaction_resultthe acknowledgement (E1)verifyreadback, event (E2, E3)receiptEd25519 signedthe agent does step 2 · the runtime does steps 4 and 5
The same five calls, whichever agent host you use.
In words
  • begin: the host opens an operation and receives the idempotency key.
  • act: the agent performs the side-effecting action with that key.
  • action_result: the host submits the provider acknowledgement.
  • verify: the runtime observes the provider and returns a verdict.
  • receipt: the runtime signs what it observed.

Five calls, in the same order on every surface. An operation outlives the session that opened it, so an agent that exits loses nothing.

Explain: the five calls and what each returns
  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.