AI Catalog manifest · Yasmina

Yasmina

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

Open the live manifest → Yasmina 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)

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

0.1

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.

host-no-identifier

Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.

content-type-not-ai-catalog-json

9 entries

5 media types

23 representative queries

0 trust manifests

Host identifier: none

What this manifest advertises

Yasmina API documentation

urn:air:yasmina.ai:docs:api-reference

Integration guides and endpoint reference for quoting, issuing policies, and webhooks.

text/html artifact →

“How do I integrate Yasmina insurance into my checkout?”
“What endpoints does the Yasmina API expose?”
“How do I issue a motor insurance policy through Yasmina?”
“How do Yasmina webhooks report policy status changes?”

API authentication and registration

urn:air:yasmina.ai:auth:credentials-guide

How an organization obtains OAuth 2.0 client credentials and exchanges them for an access token.

text/markdown artifact →

“How do I authenticate with the Yasmina API?”
“How do I get a Yasmina client_id and client_secret?”
“Which OAuth grant type does Yasmina use?”

API catalog (RFC 9727)

urn:air:yasmina.ai:catalog:api-catalog

Linkset naming Yasmina's API documentation resources.

application/linkset+json artifact →

“Where is the Yasmina API catalog?”
“What APIs does Yasmina publish?”

Protected resource metadata (RFC 9728)

urn:air:yasmina.ai:auth:protected-resource-metadata

Names the partner API as the protected resource, its authorization server, and that tokens are sent in the Authorization header.

application/json artifact →

“Which authorization server issues tokens for the Yasmina API?”
“How does an agent discover Yasmina's OAuth configuration?”

MCP server

urn:air:yasmina.ai:mcp:server

Model Context Protocol server over Streamable HTTP. Public tools read the site as structured text; one authenticated tool reports whether a partner access token is accepted by the partner API.

application/json artifact →

“Does Yasmina have an MCP server?”
“Which MCP tools does Yasmina expose?”

Agent skills index

urn:air:yasmina.ai:skills:discovery-index

Published skills covering API authentication, integrating embedded insurance, and reading this site as Markdown. Each entry carries a sha256 digest of the SKILL.md it names.

application/json artifact →

“What agent skills does Yasmina publish?”
“Is there a skill for authenticating with the Yasmina API?”

Site overview for language models

urn:air:yasmina.ai:site:llms-txt

Structured summary of Yasmina, its insurance products, industries, and canonical page URLs.

text/plain artifact →

“What is Yasmina?”
“Which insurance products does Yasmina offer?”
“Which industries does Yasmina serve?”

Partner portal

urn:air:yasmina.ai:portal:partner-portal

Where partners register, complete onboarding, and manage API credentials, policies, and payouts. Human sign-in required.

text/html artifact →

“Where do I sign up as a Yasmina partner?”
“Where do I manage my Yasmina API credentials?”

Commercial model

urn:air:yasmina.ai:site:pricing

Revenue-share model: partners pay nothing to integrate, hold no insurance license, and carry no claims liability.

text/html artifact →

“How much does Yasmina cost?”
“How does Yasmina revenue share work?”
“Do I need an insurance license to use Yasmina?”

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.

HTTPS only — yes (HTTP 200)
Content-Type: application/json — yes
Access-Control-Allow-Origin: * — yes

Evidence. Fetched https://yasmina.ai/.well-known/ai-catalog.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the Yasmina repository as ai-catalog/yasmina-holdings-limited-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=yasmina-holdings-limited&limit=10"

Everything under a tag

curl "https://apis.io/api/v1/tags/yasmina-holdings-limited"

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.