# DeskCrew Get Ticket Context

> DeskCrew Get Ticket Context is a paid API for AI agents from deskcrew.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-31).

Retrieves full context for a support ticket, including history, metadata, and related information, from the DeskCrew agent-native helpdesk.

## Facts

- Endpoint: POST https://deskcrew.io/api/x402/tools/deskcrew/get_ticket_context?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/deskcrew-get-ticket-context-13397b66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RCU2bZD821NKvRytAnxIF

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability deskcrew-get-ticket-context-13397b66 -d '<json body>'
```

Example prompt: Can you pull the full context for the support ticket I'm working on right now — I need the conversation history, status, and any relevant metadata from DeskCrew before I draft a reply?

## When to prefer this

Use this endpoint when an AI agent or human operator needs to understand the full background of a support ticket before taking action — such as drafting a reply, escalating an issue, or performing a human-in-the-loop approval step. Prefer this over generic helpdesk APIs when your workflow is agent-native and operates across site, Slack, and Discord channels within the DeskCrew ecosystem.

## Known failure modes

- Missing or invalid ticket identifier results in a not-found or bad-request error
- Malformed request body causes a validation error
- Unauthorized access if payment or authentication headers are missing (x402 payment required at $0.02 USDC)
- Ticket does not exist, returning an empty or null result
- Network timeout if the DeskCrew backend is temporarily unavailable

## How this service works

DeskCrew is the agent-native helpdesk: one support desk for your site, Slack, and Discord, with an x402 agent door and human-in-the-loop approval.

## Output

Returns a JSON object containing the full context for the requested support ticket, including conversation history, ticket status, metadata, and any related information stored in DeskCrew. The exact fields depend on the ticket, but the response is returned directly with no envelope wrapper.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "bodyType": {
     "enum": [
      "json",
      "formData",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "The tool's JSON output, returned directly with no envelope."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/deskcrew-get-ticket-context-13397b66/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from deskcrew.io](https://www.zero.xyz/host/deskcrew.io/llms.txt)