TrueFoundry Docs
TrueFoundry documentation — enterprise-grade AI Gateway combining LLM, MCP, and Agent Gateways to connect, monitor, and govern agentic AI applications across providers from a unified control plane.
AgentCard object, but omits optional fields an agent may expect.
nonstandard-supportedInterfaces
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://www.truefoundry.com/
· transport supportedInterfaces
Truefoundry truefoundry
Use when deploying ML models, services, and LLM applications; building and managing AI agents; integrating with LLM providers through a unified gateway; setting up workflows and batch jobs; or managing infrastructure for AI workloads. Reach for this skill when users need to deploy code, configure resources, manage models, integrate LLMs, or build production AI systems.
2026-07-28 from https://www.truefoundry.com/.well-known/agent-card.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.