Connections
Sign in Get started

Connections

Connect the systems you already run.

Use a ready-made integration, or connect your own system through one of four generic methods. Each one states exactly what was tested and where it stops. Nothing here is your account — you connect with your own credentials.

Connect your own system Ready-made integrations Agents & apps

Find a way to connect

Search by system, interface or operation

Connect your own system

Four generic methods. No Ardyn code needed for your system.

Each method was accepted end to end against previously unlisted, disposable services on the identified runtime build — connect, discover without side effects, run a selected operation, get a signed receipt, verify it offline. That establishes the generic method, not a live qualification of any particular vendor.

MCP server (Ardyn → your server)

In hosted console

Point Ardyn at a compatible remote MCP server. Ardyn lists its tools without calling them; you enable the ones you want; Ardyn invokes a selected tool and records a signed receipt.

Supported profileStreamable HTTP; protocol 2025-06-18 or 2025-03-26; tools/list pagination; JSON or single-message SSE responses; bearer or header credential
Modesdiscover, read, selected execution
EvidenceSOFTWARE_OBSERVED request + PROVIDER_REPORTED tool result; external effects are not independently confirmed
Accepted28/28 cases · runtime build 89fb4ba1e869
AvailabilityTested 28/28 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace

Not supported

  • stdio servers on a hosted runtime (needs a customer-resident runner)
  • server-initiated requests (sampling, elicitation, roots)
  • resource subscriptions and progress streams
Setup guide

HTTP API from an OpenAPI description

In hosted console

Upload an OpenAPI 3.0/3.1 document. Ardyn imports supported operations without calling them; reads and version-bound updates run with idempotency keys, and a lost response is reconciled by reading target state — never by replaying the write.

Supported profileOpenAPI 3.0.x / 3.1.x, JSON or YAML ≤ 2 MiB, inline upload; path/query/header parameters; application/json bodies; local $ref only; If-Match / x-ardyn-revision for version-bound writes
Modesdiscover, read, selected execution
EvidenceSOFTWARE_OBSERVED request + PROVIDER_REPORTED response with target revision when the API reports one
Accepted19/19 cases · runtime build 89fb4ba1e869
AvailabilityTested 19/19 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace

Not supported

  • Swagger 2.0
  • remote $ref
  • multipart and form bodies
  • cookie parameters
  • callbacks as operations
  • URL import on a hosted runtime
Setup guide

Events and telemetry (observe only)

In hosted console

Send signed webhooks or OpenTelemetry traces from systems you already run. Ardyn executes nothing in those systems and holds no write credential; it reconstructs an operation from what it observed and marks missing stages instead of assuming success.

Supported profileWebhook: HMAC-SHA256 over timestamp.body, ±300 s replay window, ≤ 256 KiB JSON. OTLP: HTTP JSON encoding (otlphttp exporter with encoding: json), bearer token, ≤ 4 MiB
Modesobserve
EvidencePROVIDER_REPORTED (webhook) and TELEMETRY_BACKED (spans); correlation by declared id, not proof of causation
Accepted23/23 cases · runtime build 89fb4ba1e869
AvailabilityTested 23/23 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace

Not supported

  • OTLP protobuf encoding
  • OTLP gRPC
  • metrics and logs signals (traces only)
Setup guide

Install a Pack

In hosted console

Install a signed declarative Pack written by you, a vendor or a partner against the published format. Nothing runs on install; you trust the publisher key explicitly; upgrades that ask for more access need your approval; removal keeps old receipts verifiable.

Supported profileardyn-pack/2 declarative packs (OpenAPI bindings), Ed25519 publisher signature, runtime compatibility 1.0.0
Modesdiscover, read, selected execution
Evidencesame as the HTTP method, plus pack id, version and publisher on every receipt
Accepted17/17 cases · runtime build 89fb4ba1e869
AvailabilityTested 17/17 cases · self-hosted binaries on request · running in Ardyn's hosted console · your own connection state appears only in your workspace

Not supported

  • native binary packs on a hosted runtime
  • install hooks or server-side code
  • webhook bindings inside packs (use the events method)
Setup guide

Runtime: ardyn-connect 0.1.0 — hosted in the Ardyn console (auth.ardyn.ai) for signed-in workspaces; self-hosted runtime on request; binaries provided on request (enterprise@ardyn.ai); public download awaits the publication decision for the open release. Source Kylewilson04/ardyn-evidence-runtime branch main. Machine-readable: catalogue/v1.json.

Ready-made integrations

3 of 6 packs are live-qualified today.

States come from one release manifest generated by the qualification code — not written by hand. A provider logo or name identifies the system; it is not an endorsement.

Provider / packQualificationSurfacesConnection method testedQualified
GitHub
pack github v0.1.0		Live-qualified4 tested · 0 untestedoauth (gh CLI token)2026-10-03
Cloudflare
pack cloudflare v0.1.0		Live-qualified3 tested · 0 untestedapi_credential (scoped API token)2026-10-03
OpenTelemetry (OTLP)
pack opentelemetry v0.1.0		Live-qualified3 tested · 0 untestedotlp2026-10-03
AWS
pack aws v0.1.0		Not yet qualified0 tested · 4 untested—2026-10-03
OpenAI
pack openai v0.1.0		Not yet qualified0 tested · 3 untested—2026-10-03
Raven
pack raven v0.1.0		Not yet qualified0 tested · 3 untested—2026-10-03

Source: crates/ardyn-connections-console/src/qualification.rs (emit_b9b_table()) at Kylewilson04/ardyn-evidence-runtime@d449fb89d737; report b9-live-qualification/B9_QUALIFICATION_REPORT.md.

What each pack covers — and doesn’t.

GitHub

Live-qualified

pack github · v0.1.0 · qualified 2026-10-03

Tested surfaces

  • actions workflow runs (push->run provenance, B1/B5/B6/B8/B9)
  • commit objects (provenance binding, B8/B9)
  • repository discovery incl. pagination/rename/lifecycle (B3)
  • authentication 200/401/403 distinctions + revoked handle (B2/B7)

Limitations

  • single test repository scope (Kylewilson04/ardyn-b1-live-qualification)
  • owner OAuth credential, not a customer-installation OAuth flow

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

Cloudflare

Live-qualified

pack cloudflare · v0.1.0 · qualified 2026-10-03

Tested surfaces

  • zone purge_cache receipt (harmless service effect, B5/B6/B8/B9)
  • zones list (zone id seam, B8/B9)
  • token verification + partial-permission 401/403 (B2/B7)

Limitations

  • single dev zone (ardyn.ai) within cache-purge scoped token
  • no Workers deployment or analytics surfaces exercised live
  • no 429 rate limit observed in the 120-request burst (B7)

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

OpenTelemetry (OTLP)

Live-qualified

pack opentelemetry · v0.1.0 · qualified 2026-10-03

Tested surfaces

  • OTLP/HTTP traces export via pinned otelcol v0.162.0 (B1/B4/B5/B6/B7/B8/B9)
  • fault exports: duplicate/replay/delay/reorder/400 wire rejections (B7)
  • same-trace TraceContext seam (B8/B9)

Limitations

  • self-hosted receiver only; no vendor telemetry SaaS
  • logs/metrics pipelines not exercised

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

AWS

Not yet qualified

pack aws · v0.1.0 · qualified 2026-10-03

Surfaces not yet tested

  • workload identity
  • service receipts
  • discovery
  • authentication/rotation

Limitations

  • B0 SAFETY.md: no non-production AWS sandbox account + scoped IAM credential; BLOCKED
  • fail-closed behavior proven at the shared runtime seam only; nothing simulated

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

OpenAI

Not yet qualified

pack openai · v0.1.0 · qualified 2026-10-03

Surfaces not yet tested

  • model invocation receipts
  • authentication
  • usage evidence

Limitations

  • B0 SAFETY.md: no non-production OpenAI test project API key; BLOCKED
  • fail-closed behavior proven at the shared runtime seam only; nothing simulated

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

Raven

Not yet qualified

pack raven · v0.1.0 · qualified 2026-10-03

Surfaces not yet tested

  • bounded non-prod lifecycle object
  • lifecycle receipts
  • authentication

Limitations

  • B0 SAFETY.md: no non-production Raven lifecycle-object endpoint/credential; BLOCKED
  • fail-closed behavior proven at the shared runtime seam only; nothing simulated

Qualification of the listed surfaces only — not a release and not a connected account. Ready-made Packs are not yet released for self-hosting or the hosted console; today these systems connect through the generic MCP, HTTP API or events methods.

Agents & apps

Bring the assistants and agents you already use.

This is the other direction: clients connecting into Ardyn. Assistants and custom agents reach your workspace through the existing ACTA MCP endpoint.

Client → Ardyn

ACTA MCP endpoint

Connection modes, transport and the tools a connected client can call. Client support varies by product and account tier — Ardyn does not claim every chat product connects the same way.

Read the guide → Ardyn → your MCP server

Downstream MCP

The opposite direction: Ardyn calls tools on an MCP server you run, with discovery separated from invocation.

Read the guide →

What the states mean

Live-qualifiedTested against the live provider on the listed surfaces.
Live-partialSome surfaces tested live; untested surfaces and limitations are listed.
Conformance onlyPasses the pack conformance suite; not tested against the live provider.
Not yet qualifiedNot tested: no safe credential was available. Nothing was simulated.

Method, pack and connection

Available method or packArdyn ships the code and states what it was tested against.
Your connectionYou create it with your own credentials; it can be active, degraded, expired or revoked. It never appears on this public page.
DiscoveryLists what a system offers. It never runs anything and grants no permission.
EnablingYou choose each operation and whether it reads or writes. Updates to a system’s description become a reviewable change, not a silent switch.
Observe onlyEvents and telemetry change nothing in the source system and need no write credential.