# Catalog Feeds

# Catalog feeds

Two machine-readable [APIs.json](https://apisjson.org) indexes remain published as static
documents, separately from the [Network API](/api). They describe *collections of APIs*, which is
a different job from serving research content, and APIs.json is the format built for it.

| Index | URL | What it holds |
| --- | --- | --- |
| **APIs** | [`apis.apievangelist.com/apis.json`](https://apis.apievangelist.com/apis.json) | Individual API resources tracked across the network |
| **Companies** | [`providers.apievangelist.com/apis.json`](https://providers.apievangelist.com/apis.json) | Every company tracked across the network |

Both are `application/json`, unauthenticated, and safe to poll politely.

## The provider profile

API Evangelist's own APIs.json profile — the index describing *this* provider, its APIs, and every
machine-readable artifact attached to them — is served from this portal:

**[`developer.apievangelist.com/apis.yml`](/apis.yml)**

It is mirrored from
[the canonical copy in the repository](https://github.com/api-evangelist/api-evangelist/blob/main/apis.yml)
on every portal build, and carries `x-canonical-profile` so the mirror can never be mistaken for
the original.

## What was retired

The other per-collection static feeds (`posts.json`, `rules.json`, `policies.json` and siblings)
were retired in favour of the [Network API](/api) and the [MCP server](/mcp-server) — one base
URL, real paging, real search, and a single contract instead of seventeen files. See the
[deprecation policy](/deprecation) for how retirement is handled.

The retired `/feeds/*` documentation paths redirect here rather than 404.