AgenTrux
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://api.agentrux.com/a2a
· transport JSONRPC
Publish Event publish_event
Publish an inline JSON event (≤256 KiB) to an AgenTrux topic.
pubsubpublishRead Events read_events
Read events from a topic with cursor pagination and optional event_type filter.
pubsubreadcursorGet Event get_event
Fetch a single event by event_id.
pubsubreadList Topics list_topics
List topics accessible to the connected workspace Alias.
discoveryList Grants list_grants
List grants (Topic role assignments) associated with the connected Script.
discovery2026-11-01 from https://api.agentrux.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.