Kno2

Kno2 provides Interoperability as a Service for healthcare - a single Communication API to SEND, RECEIVE, and FIND patient information across the healthcare ecosystem. One connection reaches Direct Secure Messaging, clinical document exchange, HL7 FHIR resources, HL7 V2.x, cloud fax, and national record location and retrieval through Kno2's private network, Carequality, eHealth Exchange, and TEFCA (Kno2 is a federally designated QHIN). API access is partner/enterprise gated - integrators are provisioned a per-subscription tenant host with OAuth2 client-credentials keys and an IP allowlist; a staging sandbox is available through the Kno2 Developer Program.

Kno2 publishes 5 APIs on the APIs.io network, including Attachments API, Authentication API, Directory API, and 2 more. Tagged areas include Healthcare Interoperability, Clinical Records, Health Information Exchange, Direct Secure Messaging, and FHIR.

Kno2’s developer surface includes authentication, documentation, API reference, support, engineering blog, signup flow, and 30 more developer resources.

🌐 Visit website 📡 Source on GitHub

39.9/100 developing ▬ flat Agent 26/100 agent aware open core · MIT Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0

AccessFreemiumSelf serve⚡ Free to try

1 APIs

Healthcare Interoperability Clinical Records Health Information ExchangeDirect Secure MessagingFHIR Clinical Documents Patient Records HealthcareHIECare Coordination QHIN TEFCA Carequality

Kin Score

Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0

Composite quality — 39.9/100 · developing

Contract Quality 10.6 / 19

Developer Ergonomics 5.8 / 15

Access Clarity 4.5 / 15

Operational Transparency 2.6 / 10

Contract Governance 0.4 / 9

Discoverability 5.7 / 8

Regulatory Posture 3.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/kno2: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 7

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

Kno2 FHIR API

HL7 FHIR (DSTU3/R4) resource query and retrieval at scale, including USCDI data classes and patient demographic search, brokered through Kno2's gateway to Carequality and nation...

Kno2 Patient Record Query API

On-demand patient record location and retrieval across national networks - Kno2's private network, Carequality, eHealth Exchange, and TEFCA (Kno2 is a designated QHIN). Find a p...

Kno2 Attachments API

Upload, retrieve, and mark clinical document attachments.

Kno2 Authentication API

OAuth2 client-credentials token issuance.

Kno2 Directory API

Validate Direct addresses and list document types.

Kno2 Intake API

RECEIVE surface - search, retrieve, and process inbound messages.

Kno2 Messaging API

SEND surface - draft, populate, attach, and send messages.

Scroll for all 7

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Kno2 Communication Attachments API

OPEN COLLECTION

Kno2 Communication Attachments Authentication API

OPEN COLLECTION

Kno2 Communication Attachments Directory API

OPEN COLLECTION

Kno2 Communication Attachments Intake API

OPEN COLLECTION

Kno2 Communication Attachments Messaging API

OPEN COLLECTION

Kno2 Communication API

OPEN COLLECTION

Scroll for all 7

Pricing Plans 1

Published pricing tiers and plan structures.

Kno2 Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Kno2 Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Kno2 Finops

FINOPS

Security Posture 2

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

Kno2 Authentication

http · 2 schemes

SECURITY

Kno2 Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Kno2 Agentic Access

12 operations · 7 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 4

Status, limits, changes, and where to get help

IssueTracker

RateLimits

Support

StatusPage

Commercial 5

Pricing, plans, and the legal terms of use

License

Plans

FinOps

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 6

Properties that don't map to a standard resource type

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: kno2
url: https://raw.githubusercontent.com/api-evangelist/kno2/refs/heads/main/apis.yml
name: Kno2
kind: company
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 17
  pass: local-v1
description: Kno2 provides Interoperability as a Service for healthcare - a single Communication API to SEND, RECEIVE, and
  FIND patient information across the healthcare ecosystem. One connection reaches Direct Secure Messaging, clinical document
  exchange, HL7 FHIR resources, HL7 V2.x, cloud fax, and national record location and retrieval through Kno2's private network,
  Carequality, eHealth Exchange, and TEFCA (Kno2 is a federally designated QHIN). API access is partner/enterprise gated -
  integrators are provisioned a per-subscription tenant host with OAuth2 client-credentials keys and an IP allowlist; a staging
  sandbox is available through the Kno2 Developer Program.
deliveryModel:
  model: open-core
  license: MIT
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/kno2.png
tags:
- Healthcare Interoperability
- Clinical Records
- Health Information Exchange
- Direct Secure Messaging
- FHIR
- Clinical Documents
- Patient Records
- Healthcare
- HIE
- Care Coordination
- QHIN
- TEFCA
- Carequality
created: '2026-07-12'
modified: '2026-08-14'
specificationVersion: '0.23'
apis:
- aid: kno2:kno2-fhir-api
  name: Kno2 FHIR API
  tags:
  - FHIR
  - USCDI
  - Clinical Records
  - Patient Facing
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://kno2.com/connectivity/
  baseURL: https://{subscription}.kno2fy.com
  properties:
  - url: https://kno2.com/wp-content/uploads/2022/09/Kno2-Connectivity-FHIR-2.1.pdf
    type: Documentation
  description: HL7 FHIR (DSTU3/R4) resource query and retrieval at scale, including USCDI data classes and patient demographic
    search, brokered through Kno2's gateway to Carequality and national FHIR endpoints. MODELED - Kno2 documents FHIR as a
    product capability of the Communication API but the FHIR base URL and resource paths are partner-provisioned and not publicly
    documented.
- aid: kno2:kno2-record-query-api
  name: Kno2 Patient Record Query API
  tags:
  - Health Information Exchange
  - QHIN
  - TEFCA
  - Carequality
  - Care Coordination
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://kno2.com/networks/
  baseURL: https://{subscription}.kno2fy.com
  properties:
  - url: https://kno2.com/api/
    type: Documentation
  description: On-demand patient record location and retrieval across national networks - Kno2's private network, Carequality,
    eHealth Exchange, and TEFCA (Kno2 is a designated QHIN). Find a patient, query participating organizations, and retrieve
    complete records on demand. MODELED - a documented product capability of the Communication API; the specific query/retrieve
    endpoint paths are partner-provisioned and not publicly documented.
- aid: kno2:kno2-attachments-api
  name: Kno2 Attachments API
  description: Upload, retrieve, and mark clinical document attachments.
  humanURL: https://developer.kno2.com
  baseURL: https://{subscription}.kno2fy.com
  tags:
  - Attachments
  properties:
  - type: OpenAPI
    url: openapi/kno2-attachments-api-openapi.yml
  - type: Documentation
    url: https://kno2.com/api/
  - type: APIReference
    url: https://developer.kno2.com
  - type: SourceCode
    url: https://github.com/Kno2/Kno2.ApiTestClient
  - type: PostmanCollection
    url: collections/kno2.postman_collection.json
  - type: OpenCollection
    url: collections/kno2.opencollection.json
- aid: kno2:kno2-authentication-api
  name: Kno2 Authentication API
  description: OAuth2 client-credentials token issuance.
  humanURL: https://developer.kno2.com
  baseURL: https://{subscription}.kno2fy.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/kno2-authentication-api-openapi.yml
  - type: Documentation
    url: https://kno2.com/api/
  - type: APIReference
    url: https://developer.kno2.com
  - type: SourceCode
    url: https://github.com/Kno2/Kno2.ApiTestClient
  - type: PostmanCollection
    url: collections/kno2.postman_collection.json
  - type: OpenCollection
    url: collections/kno2.opencollection.json
- aid: kno2:kno2-directory-api
  name: Kno2 Directory API
  description: Validate Direct addresses and list document types.
  humanURL: https://developer.kno2.com
  baseURL: https://{subscription}.kno2fy.com
  tags:
  - Directory
  properties:
  - type: OpenAPI
    url: openapi/kno2-directory-api-openapi.yml
  - type: Documentation
    url: https://kno2.com/api/
  - type: APIReference
    url: https://developer.kno2.com
  - type: SourceCode
    url: https://github.com/Kno2/Kno2.ApiTestClient
  - type: PostmanCollection
    url: collections/kno2.postman_collection.json
  - type: OpenCollection
    url: collections/kno2.opencollection.json
- aid: kno2:kno2-intake-api
  name: Kno2 Intake API
  description: RECEIVE surface - search, retrieve, and process inbound messages.
  humanURL: https://developer.kno2.com
  baseURL: https://{subscription}.kno2fy.com
  tags:
  - Intake
  properties:
  - type: OpenAPI
    url: openapi/kno2-intake-api-openapi.yml
  - type: Documentation
    url: https://kno2.com/api/
  - type: APIReference
    url: https://developer.kno2.com
  - type: SourceCode
    url: https://github.com/Kno2/Kno2.ApiTestClient
  - type: PostmanCollection
    url: collections/kno2.postman_collection.json
  - type: OpenCollection
    url: collections/kno2.opencollection.json
- aid: kno2:kno2-messaging-api
  name: Kno2 Messaging API
  description: SEND surface - draft, populate, attach, and send messages.
  humanURL: https://developer.kno2.com
  baseURL: https://{subscription}.kno2fy.com
  tags:
  - Messaging
  properties:
  - type: OpenAPI
    url: openapi/kno2-messaging-api-openapi.yml
  - type: Documentation
    url: https://kno2.com/api/
  - type: APIReference
    url: https://developer.kno2.com
  - type: SourceCode
    url: https://github.com/Kno2/Kno2.ApiTestClient
  - type: PostmanCollection
    url: collections/kno2.postman_collection.json
  - type: OpenCollection
    url: collections/kno2.opencollection.json
common:
- type: CapabilityMap
  url: capabilities/kno2-capability-edges.yml
  name: Kno2 Business Capability Map
- type: IssueTracker
  url: https://github.com/Kno2/Kno2.ApiTestClient/issues
- type: License
  name: MIT
  url: https://github.com/Kno2/Kno2.ApiTestClient/blob/master/LICENSE
- type: AgenticAccess
  url: agentic-access/kno2-agentic-access.yml
- type: DomainSecurity
  url: security/kno2-domain-security.yml
- type: Authentication
  url: authentication/kno2-authentication.yml
- type: GitHubOrganization
  url: https://github.com/Kno2
- type: LinkedIn
  url: https://www.linkedin.com/company/kno2
- type: Website
  url: https://kno2.com
- type: Documentation
  url: https://developer.kno2.com
- type: Plans
  url: plans/kno2-plans-pricing.yml
- type: RateLimits
  url: rate-limits/kno2-rate-limits.yml
- type: FinOps
  url: finops/kno2-finops.yml
- type: DeveloperPortal
  url: https://developer.kno2.com
- type: APIReference
  url: https://developer.kno2.com
- type: Support
  url: https://kno2.com/contact/
- type: Blog
  url: https://kno2.com/resources/blog/
- type: TermsOfService
  url: https://kno2.com/terms/
- type: PrivacyPolicy
  url: https://kno2.com/privacy-policy/
- type: SignUp
  url: https://kno2.com/request-a-demo/
- type: Packages
  url: packages/kno2-packages.yml
- type: X-MCPServerCandidate
  url: mcp/kno2-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/kno2-llms.txt
- type: Overlay
  name: Attachments overlay
  url: overlays/kno2-attachments-api-overlay.yaml
- type: Overlay
  name: Authentication overlay
  url: overlays/kno2-authentication-api-overlay.yaml
- type: Overlay
  name: Directory overlay
  url: overlays/kno2-directory-api-overlay.yaml
- type: Overlay
  name: Intake overlay
  url: overlays/kno2-intake-api-overlay.yaml
- type: Overlay
  name: Messaging overlay
  url: overlays/kno2-messaging-api-overlay.yaml
- type: Conformance
  url: conformance/kno2-conformance.yml
- type: ErrorCatalog
  url: errors/kno2-problem-types.yml
- type: Lifecycle
  url: lifecycle/kno2-lifecycle.yml
- type: StatusPage
  url: https://status.kno2.com
- type: Conventions
  url: conventions/kno2-conventions.yml
- type: DataModel
  url: data-model/kno2-data-model.yml
- type: AgentSkill
  name: Send a message via Kno2 Direct Secure Messaging
  url: skills/kno2-send-a-message.md
- type: AgentSkill
  name: Process an inbound Kno2 message
  url: skills/kno2-process-inbound-message.md
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/kno2"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/kno2/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/kno2/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.