Card snapshot

This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.

{
  "name": "Tenderly",
  "description": "Tenderly developer documentation \u2014 Virtual Environments, Node RPC, Simulation API, Debugger, Monitor, Alerts, Web3 Actions, and more.",
  "url": "https://docs.tenderly.co/",
  "version": "1.0.0",
  "protocolVersion": "0.3",
  "preferredTransport": "HTTP+JSON",
  "supportedInterfaces": [
    {
      "url": "https://docs.tenderly.co/",
      "protocolBinding": "HTTP+JSON",
      "protocolVersion": "0.3"
    }
  ],
  "provider": {
    "url": "https://docs.tenderly.co/",
    "organization": "Tenderly"
  },
  "documentationUrl": "https://docs.tenderly.co/",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false
  },
  "defaultInputModes": [
    "text/plain"
  ],
  "defaultOutputModes": [
    "text/plain"
  ],
  "skills": [
    {
      "id": "tenderly",
      "name": "Tenderly",
      "description": "Use when simulating transactions before sending them onchain, debugging failed transactions, testing smart contracts in production-like environments, monitoring onchain events, or building serverless automation for Web3 systems. Agents should reach for Tenderly when users need to preview transaction outcomes, understand why a transaction failed, test contracts in isolated environments, set up monitoring and alerts, or integrate blockchain operations into their development workflow.",
      "tags": [],
      "url": "https://docs.tenderly.co/.well-known/agent-skills/tenderly/skill.md"
    }
  ]
}