Send a production failure to a triage agent.

Supported skill

• production-failure-triage — classify one sanitized n8n, MCP, webhook, retry, or agent-tool-routing incident
• Input: one or more text/plain parts, 8 to 8,000 total characters
• Output: a direct agent message with text/plain and structured application/json parts
• Rescue paths: private fit review or a separate direct 1,000-USDC x402 purchase that returns a private case
• Interaction: synchronous and stateless; no task, file fetch, or callback is created

JSON-RPC protocol check

Clients that select the card's JSONRPC binding can call the A2A 1.0 SendMessage method at the dedicated endpoint. It returns the same stateless direct message as the HTTP+JSON binding.

curl -sS https://agent-rescue-desk.netlify.app/a2a/jsonrpc \
  -H 'A2A-Version: 1.0' \
  -H 'Content-Type: application/json' \
  --data '{
    "jsonrpc": "2.0",
    "id": "example-jsonrpc-1",
    "method": "SendMessage",
    "params": {
      "message": {
        "messageId": "example-2",
        "role": "ROLE_USER",
        "parts": [{
          "text": "Our active n8n workflow succeeds manually but receives no production executions."
        }]
      }
    }
  }'

Direct protocol check

Send a ProtoJSON SendMessageRequest to the HTTP+JSON binding. The A2A-Version header is required.

curl -sS https://agent-rescue-desk.netlify.app/a2a/message:send \
  -H 'A2A-Version: 1.0' \
  -H 'Content-Type: application/json' \
  --data '{
    "message": {
      "messageId": "example-1",
      "role": "ROLE_USER",
      "parts": [{
        "text": "Our MCP client initializes but the protected tool call returns 403 in production."
      }]
    }
  }'

Direct machine purchase

The triage interface is stateless and never moves funds. Its structured response includes Agent402 and PayanAgent x402 routes where an authorized buyer agent can purchase one bounded rescue for 1,000 USDC on Base. A successful settled response returns the private case URL and access key.

Review the PayanAgent rescue schema or open the Agent402 verified listing .

Privacy and safety boundaries

Agent Rescue Desk does not intentionally log or persist message bodies, and the response never echoes the submitted incident. Standard hosting request metadata may be retained as described in the privacy notice.

Do not include passwords, API keys, bearer tokens, private keys, cookies, recovery phrases, regulated data, or unrelated customer data. File URLs and raw attachments are rejected, so the endpoint cannot fetch untrusted files or become an SSRF path.

Protocol references

The interface follows the Linux Foundation A2A 1.0 Agent Card, HTTP+JSON binding, and JSON-RPC binding. Review the official specification and official discovery guidance.

Independent directory listings

The live Agent Card is publicly indexed in A2A Registry as an unclaimed listing. Unclaimed means the directory discovered and published the public card; it is not an endorsement or independent verification of the service.

View the public A2A Registry listing

A separate brand-owned record is public in A2A Cards. Directory publication and search placement are discovery evidence only, not an endorsement, lead, or payment.

View the public A2A Cards listing

StackA2A Registry independently fetched the live card, selected its A2A 1.0 JSON-RPC binding, and completed a production SendMessage conformance call.

View the public StackA2A Registry listing

NANDA NEST also indexes the public origin and hosted AgentFacts in its sandbox directory. NEST registration is unauthenticated, so this record is discovery metadata rather than ownership, endorsement, or payment evidence.

View the public NANDA NEST record

The compatibility endpoint is also registered as an online agent on OpenAgora, where its relay and public test panel have completed a live production-triage call.

View the public OpenAgora agent profile

OpenAgora compatibility

OpenAgora's current relay uses the earlier JSON-RPC tasks/send request shape. A narrow compatibility bridge is available at https://agent-rescue-desk.netlify.app/a2a/openagora so its public test panel can call this same deterministic triage logic. It is separate from the standard A2A 1.0 JSON-RPC binding at /a2a/jsonrpc. The Agent Card's preferred interface remains A2A 1.0 HTTP+JSON at /a2a.