CATALOG DATA / TRANSPARENCY

The machine-readable catalog behind the claims.

This public source snapshot contains exactly 1,409 Agent Apps and 14,799 structured action contracts. Every app has a named provider definition, authentication model, category, and at least one described action.

DOWNLOAD JSON BROWSE CATALOG

SOURCE REVISION 4759b91c99f1ee600151eeec880fe09848f64b56 / MODIFIED 2026-08-23T16:42:28+08:00

Verified in the public snapshot

1,409 distinct provider definitions
14,799 named actions with descriptions
23 provider categories
200 quality-ranked pages in the current index rollout (limit 200)
Authentication types and provider connection guidance
Selected input fields, scopes, permissions, and risk signals
11 additional human-edited integration references

What catalog presence does not mean

Every action is enabled for every workspace or pricing plan
Every connected provider account grants every required permission
Upstream APIs behave identically across plans and regions
Name-based risk signals replace provider documentation or policy
A catalog record proves latency, reliability, adoption, or outcomes
The hosted runtime and this source snapshot update simultaneously

Counting and publication methodology

1. Agent App

One distinct provider definition with a unique service identifier, display name, category, authentication model, and one or more action contracts. Authentication variants are not counted as separate apps.

2. Action

One named provider operation with a description, machine-readable input schema, output schema, and execution mapping. Catalog search, authentication, refresh, policy rejection, and retries are not counted as provider actions.

3. Public page

Each provider becomes a canonical Agent App reference. Pages expose source-backed facts, provider-specific action descriptions, input examples, authentication guidance, risk signals, and contextual links rather than keyword-swapped marketing copy.