Authologic API
urn:air:developer.authologic.com:api:authologic-api
Identity verification, AML screening, and user authentication platform.
application/openapi+json
artifact →
AI Catalog manifest · Authologic
Authologic
Authologic serves an AI Catalog
manifest at /.well-known/ai-catalog.json on developer.authologic.com, declaring
1 agentic resource
that a discovery service can index without asking anyone’s permission.
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.
content-type-not-ai-catalog-jsoncors-not-readable-cross-originentry-no-representativeQuerieshost-identifier-not-did-web
What this manifest advertises
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— yesAccess-Control-Allow-Origin: *— no — header absent
Evidence. Fetched
https://developer.authologic.com/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Authologic repository
as ai-catalog/authologic-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.