# DeskCrew Link Issue

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

Links or associates a support issue with another resource, ticket, or entity within the DeskCrew helpdesk system

## Facts

- Endpoint: POST https://deskcrew.io/api/x402/tools/deskcrew/link_issue?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/deskcrew-link-issue-092d22b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_D8hguL0KJjjUOsjG-x0Fd

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-link-issue-092d22b4 -d '<json body>'
```

Example prompt: Link issue #4521 to issue #4499 in DeskCrew so they're associated as related support tickets — use a POST request with the issue IDs in the body.

## When to prefer this

Use this endpoint when you need to programmatically create associations between support issues in DeskCrew, especially in agentic workflows where tickets arriving from multiple channels (site, Slack, Discord) need to be related to each other or to a parent issue. Prefer this over manual helpdesk UI actions when automating triage or deduplication pipelines.

## Known failure modes

- Invalid or non-existent issue ID returns an error response
- Missing required 'type' or 'method' fields in input causes a 400-level validation error
- Incorrect HTTP method (e.g. GET instead of POST/PUT/PATCH) results in rejection
- Insufficient permissions or authentication failure returns an auth error
- Payment failure via x402 protocol prevents the call from completing

## 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 confirming the link was created between issues, including the result of the association operation as returned directly by the DeskCrew tool with no envelope wrapping.

## 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-link-issue-092d22b4/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)