- Catalyst metrics: read and load business metrics and platform metrics for adoption and value tracking
- Deployment pipeline: upload the Mule application JAR and POM to the organisation's Maven facade on Exchange, list and read Exchange assets
- API Manager: list or create API instances per environment, apply, read and delete policies, JWT and SLA-based rate-limiting tags, tiers, policy templates
- Runtime: CloudHub v2 application by id, hybrid deployments, API proxy deployments, Runtime Fabric targets, worker-cloud agents
- Anypoint GraphQL endpoint and the OAuth2 token route; 30 routes (12 read-only) on anypoint.mulesoft.com
MuleSoft Catalyst Knowledge Hub API Connector
The Anypoint Platform routes used by MuleSoft Catalyst delivery playbooks — business and platform metrics, Maven artefact upload to Exchange, API Manager policies and SLA tiers, CloudHub v2 application reads, hybrid and proxy deployments, Runtime Fabric targets and the GraphQL endpoint — registered in Apivom Atlas as 30 routes.
What you can do
Use cases
- Value metrics in the account review — Read the business and platform metrics a Catalyst programme tracks and surface adoption and reuse figures on the customer record before each steering meeting.
- Release step from the pipeline — Publish the Mule application artefact to Exchange, create the API instance and apply the standard JWT and rate-limiting policies in one orchestrated step with the result logged in your tenant.
- Deployment evidence per environment — Read hybrid, proxy and Runtime Fabric deployments for an environment so a change record shows exactly what is running where.
MuleSoft Catalyst is the delivery methodology MuleSoft and its partners use to run an integration programme — Knowledge Hub playbooks, enablement, and metrics that prove business value. The automations those playbooks prescribe lean on a small set of Anypoint Platform routes, and that set is what Apivom Atlas catalogues here: the business- and platform-metrics endpoints Catalyst's value dashboards read and load, the Maven facade on Exchange a CI pipeline uses to publish a Mule application JAR and POM, the API Manager calls that create an API instance, apply JWT or SLA rate-limiting policies and read tiers, and the runtime reads and deployments across CloudHub v2, hybrid servers, API proxies, Runtime Fabric and worker-cloud agents — plus the GraphQL endpoint and the token route. Thirty routes, twelve of them read-only, with the same Connected App credential as the full Anypoint connector. No Apivom product workflow uses these routes today — Apivom's own integrations run on Apivom Atlas rather than on Mule runtimes — so the connector is available to tenants running a Catalyst programme who want its pipeline steps or value metrics reachable from an Apivom workflow, scoped per customer.
A Connected App on your Anypoint Platform organisation (client id + secret) with the scopes this API family needs. The caller gets a token at /accounts/api/v2/oauth2/token (client credentials) and sends it as Bearer; Apivom Atlas forwards, logs, stores nothing. Secret encrypted in your Iris tenant.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
How does this differ from the MuleSoft Anypoint Platform connector?
It is a curated subset: the 30 routes Catalyst playbooks and pipelines actually call — metrics, Maven publish, a handful of API Manager, deployment and Runtime Fabric calls. The full Anypoint connector catalogues the broad control plane with 254 routes; both share the Connected App credential model.
Is Catalyst a product I need to license?
Catalyst is MuleSoft's delivery methodology and Knowledge Hub, available to Anypoint customers and partners; the routes here are standard Anypoint Platform APIs that your existing Anypoint entitlements govern.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.