Questions and answers

How agent access works.

A product can support several interfaces. Choose the path that fits the task, permissions and available evidence.

Are API, MCP and CLI mutually exclusive?

No. A listing represents a website or application, and can contain multiple API endpoints, MCP servers and CLI packages. Vibenate displays their individual setup and evidence states.

Must an agent browse the website?

No. Agents can discover and inspect Vibenate through its public API, MCP server or CLI. For a listed product they can use an available API, MCP server, CLI or browser, subject to that product’s authentication and permissions.

Why have a browsable directory for agents?

Stable HTML profiles and linked category pages let search crawlers, web-retrieval systems, developers and agent operators inspect the same evidence that API clients receive. Browsing complements structured retrieval.

Is “qualified” a certification of functionality?

No. It means the current declaration passed the published-path documentation checks. It does not imply an executed provider operation, security certification, uptime guarantee or compatibility with every agent.

What do stale and unknown mean?

Stale means a successful documentation assessment has expired. Changed details await a new assessment. Unknown means the registry could not establish the required facts. A retrieval failure does not prove that a provider lacks an interface.

Does a listing make an AI system recommend a product?

It provides accessible, structured facts and citations. Retrieval, indexing and recommendations depend on the system and query; an API or MCP connection does not automatically ingest the entire registry.

Full methodology · API, MCP and CLI access