For your security, you were signed out after a period of inactivity. Click Stay signed in to continue where you left off.
Sign outStay signed in
Integration Products
0 results
0 published
0 claimed
Clear field
Guides
API Management is the internal API Management platform built on IBM API Management. It enables teams to publish, manage and secure REST APIs across multiple catalogs (dev, test, prod).
1
IBM API Management
The underlying gateway and developer portal. Handles lifecycle management, rate limiting, OAuth and API versioning.
2
OAuth 2.0 / Client Credentials
All pAPI subscriptions use OAuth 2.0 client credentials. Apps receive a client ID and secret to authenticate against protected endpoints.
3
Plans & Subscriptions
Products group APIs into plans with different rate limits. Consumer apps subscribe to a plan to gain access.
Close
Streamzilla is the internal event streaming platform powered by Apache Kafka (Confluent). It lets teams produce and consume real-time data streams with full ACL-based access control.
1
Apache Kafka / Confluent
Distributed, fault-tolerant event log. Topics are the core unit — producers write, consumers read at their own pace.
2
ACL-based Access Control
Every service account is granted fine-grained produce/consume ACLs per topic. Consumer group ACLs control offset coordination.
3
Schema Registry
Optional Avro/JSON schema enforcement ensures producers and consumers agree on message structure and enables schema evolution.
Close
MCP lets teams expose tools and data sources to AI agents in a standardised way. An MCP server defines callable tools that any compatible LLM client can discover and invoke.
1
Model Context Protocol (Anthropic)
Open protocol that standardises how AI models request context and invoke tools. Works with Claude, GPT-4 and any MCP-compatible host.
2
Tool Definitions
Each MCP server declares a set of typed tools (name, description, input schema). Clients call tools by name; the server executes and returns results.
3
SSE / HTTP Transport
MCP servers are hosted as HTTP services. Clients connect via Server-Sent Events (SSE) for streaming responses or plain HTTP for one-shot calls.
