agent-ready-api-catalog

Publish an RFC 9727 API catalog at /.well-known/api-catalog.

47|4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/fabricioctelles/skills --skill agent-ready-api-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-ready-api-catalog
Source: https://github.com/fabricioctelles/skills/tree/main/skills/agent-ready-cloudflare/api-catalog
Command: npx skills add https://github.com/fabricioctelles/skills --skill agent-ready-api-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps make APIs discoverable by automated agents and clients through a standardized API catalog endpoint.

Core Features & Use Cases

  • RFC 9727 Compliance: Defines a linkset-based API catalog at the standardized well-known location.
  • API Metadata Publishing: Documents API anchors, OpenAPI specifications, human-readable documentation, and optional health endpoints.
  • Use Case: Use this Skill to expose multiple site APIs in a machine-readable catalog so AI agents can locate their specifications and documentation automatically.

Quick Start

Use the agent-ready API catalog skill to implement and validate a RFC 9727 catalog for the APIs on my site.

Frequently Asked Questions about agent-ready-api-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an API catalog and how does automated API discovery work?

An API catalog is a machine-readable directory that exposes multiple APIs for automated discovery. It uses a standardized endpoint so AI agents and automated clients can locate OpenAPI specifications, documentation, and health endpoints without manual intervention.

How do I make my APIs discoverable by AI agents using RFC 9727?

To make APIs discoverable by AI agents, implement a /.well-known/api-catalog endpoint returning HTTP 200 with application/linkset+json. This RFC 9727-compliant linkset publishes API anchors, OpenAPI specifications, and documentation links for automated clients.

Does my website need a specific format to expose an API catalog for automated clients?

Yes, your website must serve a /.well-known/api-catalog endpoint returning HTTP 200 with the application/linkset+json content type. The response must contain RFC 9727-compliant linkset entries for automated clients to parse the API catalog successfully.

What's the best way to publish OpenAPI specifications for AI agent discovery?

Publishing OpenAPI specifications for AI agent discovery is best achieved through an RFC 9727-compliant linkset catalog. This standardized approach exposes API anchors, documentation links, and health endpoints in a machine-readable format at a well-known location.

When do I need a linkset-based API catalog instead of standard API documentation?

You need a linkset-based API catalog when AI agents and automated clients must locate your APIs without human intervention. If your platform exposes multiple APIs requiring automated discovery of OpenAPI specifications and health endpoints, standard human-readable documentation is insufficient.