AI Catalog manifest · Bizzabo

Bizzabo

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

Open the live manifest → Bizzabo 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:bizzabo.com — 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.
2 entries
2 media types
10 representative queries
0 trust manifests
Host identifier: did:web:bizzabo.com

What this manifest advertises

Bizzabo Public API

urn:air:bizzabo.com:api:public-api

REST API for the Bizzabo Event Experience OS. Programmatic access to events, registrations, contacts, orders, agenda/sessions, speakers, partners, and webhooks. OAuth 2.0 client-credentials auth.

application/vnd.oai.openapi+json;version=3.0 artifact →

Bizzabo Marketing Content

urn:air:bizzabo.com:server:marketing-mcp

Read-only MCP server over Bizzabo's published marketing content — blog posts, Event Experience Podcast episodes, customer case studies, guides, reports and product comparisons. Returns clean markdown with citable URLs. No credentials required.

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

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.