How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Verified Digital Agents (VDA) .well Known API

The .well Known API from Verified Digital Agents (VDA) — 6 operation(s) for .well known.

Verified Digital Agents (VDA) .well Known API is one of 27 APIs that Verified Digital Agents (VDA) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include .well Known. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 6 paths. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://acp.getvda.ai, https://hitl.getvda.ai.

6 operations 6 paths 0 schemas 6 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://witness.getvda.ai
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Verified Digital Agents (VDA) .well Known API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (wtn..) (witness_bearer). It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — Contract A: a Witness Bearer (wtn. . ) validated by HITL via Witness GET /whoami. Authorization header only. This authenticates the CALLING account; the human…

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.

.well Known 6
GET
/.well-known/agent-card.json
A2A agent card
getWellKnownAgentCardJson → 200
GET
/.well-known/did.json
DID document
getWellKnownDidJson → 200404
GET
/.well-known/agent-card-public-key.pem
Agent Card Public Key
agent_card_public_key__well_known_agent_card_public_key_pem_get → 200
GET
/.well-known/jwks.json
Jwks
jwks__well_known_jwks_json_get → 200
GET
/.well-known/ai-catalog.json
Ard Catalog
ard_catalog__well_known_ai_catalog_json_get → 200
GET
/.well-known/agent.json
Agent Card
agent_card__well_known_agent_json_get → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

getvda-ai-well-known-api-openapi.yml Raw ↑

Other APIs Verified Digital Agents (VDA) publishes across the network.

VDA Onboarding Agent
Verified Digital Agents (VDA) Agents API
Verified Digital Agents (VDA) Bundles API
Verified Digital Agents (VDA) C2MD Edge API
Verified Digital Agents (VDA) Copilot Studio.yaml API
Verified Digital Agents (VDA) Environments API
Verified Digital Agents (VDA) Genesis API
Verified Digital Agents (VDA) GOSCE Portfolio API
Verified Digital Agents (VDA) Governance.md API
Verified Digital Agents (VDA) Health API
Verified Digital Agents (VDA) Healthz API
Verified Digital Agents (VDA) Livez API
Where this information came from

This is an independent, third-party profile of Verified Digital Agents (VDA) .well Known API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.