A2A Agent Card · IntegrationOS
IntegrationOS
⚠ Agent card, not A2A. IntegrationOS serves a machine-readable agent
manifest at the A2A discovery path, but it fails a structural check in the A2A 1.0.0
AgentCard object. It is an agent card in spirit rather than in schema — useful for
discovery, but an A2A client cannot assume it will parse.
capabilities-not-objectno-protocolVersionskills-not-arrayno-defaultInputModesno-defaultOutputModesno-preferredTransportno-nameno-urlno-versionno-description
Legacy discovery path. This card is served at
/.well-known/agent.json, the
pre-0.3 location, rather than the current /.well-known/agent-card.json. Clients written
against A2A 1.0.0 will not find it.
Discovery
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://withone.ai/.well-known/agent.json
Documentation
Evidence. Fetched
2026-07-28 from https://withone.ai/.well-known/agent.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.