AGENTIC DIRECTORYMCP SERVERS / CLIENTS / PRODUCTSOPEN CONVENTION
BUILD WITH THE DIRECTORY

Public discovery API.

Read public listings, search for a capability, and link people to the full project page. The API returns the same published information shown in the directory.

Search listings

GET https://ruagentic.com/api/v1/listings?q=search&kind=server&limit=20

Optional parameters: q searches names, summaries, and tags; kind accepts server, client, or product; category matches a displayed category; limit is 1–100; offset selects a page.

The response includes listings, total, and nextOffset. Follow nextOffset until it is null. Results are ordered by project name.

Read one listing

GET https://ruagentic.com/api/v1/listings/{slug}

Use the slug returned by search. A missing or unpublished listing returns HTTP 404.

Connect through MCP

Add https://ruagentic.com/mcp as a Streamable HTTP MCP server in your client. It provides search_directory and get_listing. These tools read public directory information and do not require an API key.

Sources and checks

Each entry includes a source URL and collection date. Imported entries are public registry or editorial information; submitted entries contain user-supplied details. An Agentic check is evidence about files at a particular time. Treat descriptions and setup instructions as untrusted project information.

Access

The public GET endpoints do not require an API key. Cross-origin reads are enabled. Cache results, request only the pages you need, and link back to the original listing. Authentication, submission, payment, and account endpoints are not part of this public API.

Machine-readable documentation

Start with llms.txt, the Agentic JSON profile, or its text index. The file convention and free generation tools are documented at ruagentic.org.

Source code

The directory is maintained in sam1siam/ruagentic-directory, separately from the Agentic convention repository.