AI Catalog manifest · Duvo Ai

Duvo

Duvo Ai serves an AI Catalog manifest at /.well-known/ard.json on duvo.ai, declaring 5 agentic resources that a discovery service can index without asking anyone’s permission.

Open the live manifest → Duvo Ai 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.

Declared identity

404

did:web:duvo.ai — resolving it returns 404. A did:web: that does not resolve is a string, not an identity, and does not earn the identity affordance here.

Discovery path

ard.json

Served at /.well-known/ard.json — the path ARD v0.91 says a consumer MUST fetch.

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.

content-type-not-ai-catalog-json
did-web-does-not-resolve

5 entries

4 media types

16 representative queries

0 trust manifests

Host identifier: did:web:duvo.ai

What this manifest advertises

Duvo MCP

urn:air:duvo.ai:mcp:duvo

Hosted Duvo MCP server card, listed in the official MCP Registry as io.github.duvoai/duvo. Approved workspaces use it to start runs and respond to approval gates before write-back. The MCP endpoint is https://api.duvo.ai/v2/mcp.

application/mcp-server+json artifact →

“audit all carrier invoices against the freight contract before we pay”
“find overcharges on supplier invoices before the payables run”
“run grocery inbound exceptions across WMS and ERP and ask for approval before write-back”
“connect to the Duvo MCP server to start a freight audit run”

Duvo agent discovery

urn:air:duvo.ai:agent:discovery

Duvo agent discovery manifest. It lists capabilities, auth, OpenAPI, MCP, and the A2A card for freight audit, payables audit, and grocery or retail work across WMS, ERP, and TMS.

application/json artifact →

“discover Duvo agent capabilities and authentication”
“where is the Duvo OpenAPI spec and MCP server card”
“how does an agent connect to Duvo for payables audit”

Duvo A2A agent card

urn:air:duvo.ai:a2a:duvo

Duvo A2A agent card. It describes operational runs, case queues, and human approval before write-back into the systems of record the business already runs.

application/a2a-agent-card+json artifact →

“Duvo A2A card for freight audit with human approval”
“hand a retail OTIF dispute to Duvo for write-back to the TMS”
“route a payables exception through Duvo case queues”

Duvo OpenAPI

urn:air:duvo.ai:api:openapi

Live OpenAPI for the Duvo public API. Clients use it to start runs, create queue cases, and inspect outcomes after write-back.

application/vnd.oai.openapi+json artifact →

“create a Duvo API case for a freight overcharge claim”
“approve a Duvo human request before write-back to ERP”
“inspect a completed Duvo payables audit run”

Duvo public skills

urn:air:duvo.ai:skills:index

Index of public Duvo skills on this host: duvo-cli, duvo-job-debugger, and duvo-sop-writer.

application/json artifact →

“install the Duvo CLI skill to script runs and approvals”
“debug a failed Duvo freight audit job from the transcript”
“write a Duvo SOP for payables audit across ERP and supplier portals”

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://duvo.ai/.well-known/ard.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the Duvo Ai repository as ai-catalog/duvo-ai-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=duvo-ai&limit=10"

Everything under a tag

curl "https://apis.io/api/v1/tags/duvo-ai"

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.