AI Catalog manifest · FluentEDI

FluentEDI

FluentEDI serves an AI Catalog manifest at /.well-known/ai-catalog.json on fluentedi.com, declaring 4 agentic resources that a discovery service can index without asking anyone’s permission.

Open the live manifest → FluentEDI provider profile
Structural grade · AI Catalog 1.0
Near-Conformant
Correctly shaped — every hard check passes — but optional affordances are missing.
ARD conformance-test v0.9.1 (ards-project/ard-spec)
PASS
Run against this exact body with the project’s own conformance CLI.
Discovery path
predecessor
Answered only at /.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.
Declared spec version
1.0
The specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
4 entries
3 media types
10 representative queries
0 trust manifests
Host identifier: fluentedi.com

What this manifest advertises

FluentEDI MCP server

urn:air:fluentedi.com:mcp:tools

Deterministic tools for AI agents. No key, no signup, no SDK.

application/mcp-server-card+json artifact →

FluentEDI REST API

urn:air:fluentedi.com:api:rest

OpenAPI 3.1 description of all 49 tools. No authentication.

application/json artifact →

FluentEDI agent reference

urn:air:fluentedi.com:docs:llms

Every tool, parameter and worked example in one file.

text/plain artifact →

Tool registry

urn:air:fluentedi.com:registry:tools

Machine-readable index of every tool and its endpoint.

application/json artifact →

How it is served

The publishing guide asks for three things at the transport layer, because a crawler is the consumer that matters and a crawler is a browser-shaped client.
Evidence. Fetched https://fluentedi.com/.well-known/ai-catalog.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the FluentEDI repository as ai-catalog/fluentedi-ai-catalog.json. Nothing on this page is derived or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not exist, which makes it — like an A2A Agent Card — one of the few agent artifacts that cannot be produced on a provider’s behalf. Grades are recomputed on every build; the specification is a v0.9 draft and these verdicts will move when it does.

Work with this as data

Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agent discovery

3 MCP tools reach this
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
Search the catalog 
curl "https://apis.io/api/v1/search?q=fluentedi&limit=10"
Everything under a tag 
curl "https://apis.io/api/v1/tags/fluentedi"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.