AI Catalog manifest · Yuno

Yuno

Yuno serves an AI Catalog manifest at /.well-known/ard.json on y.uno, declaring 2 agentic resources that a discovery service can index without asking anyone’s permission.

Open the live manifest → Yuno provider profile
Structural grade · AI Catalog 1.0
Flavored
Fails a hard check in the data model. A catalog in spirit rather than in schema.
ARD conformance-test v0.9.1 (ards-project/ard-spec)
FAIL
Run against this exact body with the project’s own conformance CLI — 5 critical errors.
Discovery path
ard.json
Served at /.well-known/ard.json — the path ARD v0.91 says a consumer MUST fetch.
Declared spec version
none
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.
⚠ Hard checks failed. An ARD client cannot assume this manifest parses to the model the specification defines.

The urn:ai: prefix is not sloppiness — it is the identifier scheme ARD itself specified until ADR-0009 moved the namespace identifier from ai to air for URN validity. This publisher implemented against the earlier draft.

Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
2 entries
2 media types
6 representative queries
0 trust manifests
Host identifier: none

What this manifest advertises

Yuno Payments API

urn:ai:y.uno:api:payments

Payment orchestration REST API. One integration to accept payments across 1,000+ payment methods in 190+ countries, route transactions to the best provider, run payouts, and manage subscriptions. Machine-readable OpenAPI 3.1 spec at the url.

application/rest-api+json artifact →

Yuno MCP server

urn:ai:y.uno:mcp:yuno-mcp

Official MCP server exposing the Yuno API as Model Context Protocol tools. Distributed as the npm package @yuno-payments/yuno-mcp and run locally by the MCP client; there is no hosted MCP endpoint.

application/mcp-server-card+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://y.uno/.well-known/ard.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the Yuno repository as ai-catalog/yuno-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=yuno&limit=10"
Everything under a tag 
curl "https://apis.io/api/v1/tags/yuno"

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.