Confrere

Confrere is a privacy-first, embeddable video-consultation platform (now a Compodium product) built in the Nordics for healthcare providers, therapists, consultants, tutors, and sales teams who need secure, encrypted video meetings that clients join from any modern browser with no download. Its server-side API mints single-use, one-minute room URLs that redirect a participant into a Confrere video room, and lets integrators invalidate a room or eject a specific user. Reliability is advertised at 99% across more than one million completed meetings. Backed by Point Nine.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

How we profile Confrere

Each block below is one kind of artifact we hold for Confrere. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 2

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Confrere Room API

The Room API from Confrere — 2 operation(s) for room.

Confrere Token API

The Token API from Confrere — 1 operation(s) for token.

Arazzo Workflows 2

Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

Confrere — start and end a video session

Mint a single-use room URL for a participant, then end the session by invalidating the room.

ARAZZO

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

confrere-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Confrere Authentication

http/apiKey · 3 schemes

SECURITY

Confrere Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Confrere Agentic Access

3 operations · 3 acting

3 operations · 3 acting

AGENTIC

Resources

Every other property we hold for Confrere — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/confrere · machine-readable index on apis.io