WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources

What is API Gateway federation? A guide to centralized API Management

What Is API Gateway Federation?

API gateway federation refers to the integration and management of multiple API gateways within a unified control plane. This approach allows organizations to use different API gateways, which may be from various vendors or tailored to specific environments (e.g., cloud-based, on-premises), while centrally managing their configurations, policies, and monitoring.


Figure 1: API gateway federation with a unified control plane

CMS interoperability: empowering providers with seamless access to patient data

Introduction

The Provider Access API enables seamless access to patient health data for providers who have both a contractual relationship with the payer and a treatment relationship with the patient. Under the CMS-0057-F Final Rule, impacted payers are required to make the following data available through this API: claims, encounters, and prior authorization information similar to what is shared via the Patient Access API.

Subscribe to