Capabilities
Useful operations, with their limits stated.
A capability is an operation your agents can request — or work Ardyn can observe — through a connection. Each answers: what it does, what you connect, what it can change, where it runs, what receipt you get and what happens when it can’t finish.
In this release
Operations you can use through the generic methods.
From the same public catalogue as Connections (catalogue/v1.json). In your workspace, the operations discovered from your own systems appear here with their source, version and activation state.
Call a tool on a connected MCP serverMCPIn hosted console
You connectOne enabled tool, arguments validated against its pinned input schema
It can changeWhatever that tool does; you classify it read or write when enabling
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 28/28 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodmcp
Read a record through an imported APIHTTPIn hosted console
You connectA GET operation from your OpenAPI document
It can changeReads only
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 19/19 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodhttp_openapi
Update a record with a version checkHTTPIn hosted console
You connectA version-bound write operation, an expected revision and an idempotency key
It can changeChanges one record; a lost response is reconciled, never resent
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 19/19 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodhttp_openapi
Reconstruct an operation that ran elsewherePassiveIn hosted console
You connectA correlation id and the stages you expect
It can changeNothing — observation only
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 23/23 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodevents
Run an operation from an installed PackPackIn hosted console
You connectAn enabled operation from a trusted publisher's Pack
It can changeWithin the Pack's declared hosts and effects
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 17/17 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodpack
Check a receiptVerifierIn hosted console
You connectAn exported receipt and the signer's trust configuration
It can changeNothing — verification never contacts the original provider
Where it runshosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request
ResultAn operation record and a signed receipt (profile ardyn-bundle/2) you can export and verify offline.
AvailabilityTested 18/18 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace
Methodverify
What happens when you use one.
1 · Discover
See what’s offered
Ardyn lists a system’s operations. Nothing runs, and nothing is enabled.
2 · Enable
Choose and classify
You enable an operation and say whether it reads or writes. Writes need an idempotency key, and version-bound writes an expected revision.
3 · Run
Bounded request
Inputs are checked against the pinned schema. Requests go only to the connection’s allowed host, never to private networks unless you run the runtime there.
4 · Receipt
Signed record
The request, the system’s answer and any gaps become a signed receipt you can export and verify offline.
When it can’t finish
Refused before sendingNot enabled, revoked, wrong workspace, invalid input or a changed schema: nothing is sent and the reason is recorded.
Target refusedThe system’s own error (for example a revision mismatch) is recorded as a failure, with its response.
Outcome unknownIf the response is lost after sending, the operation is marked unknown. Ardyn reconciles by reading the target — it never resends the change.
Missing evidenceFor observed work, a missing stage makes the result partial — never a success.
Active or passive
ActiveYour agent asks Ardyn to run the operation; Ardyn routes it, observes the result and records it.
PassiveThe work happens elsewhere; Ardyn only receives events and telemetry about it.
Implementation labels (MCP, HTTP, Passive, Pack, Verifier) are secondary details. A listed capability is not a completed execution.