# AgentRXI GitHub Issue Search

> AgentRXI GitHub Issue Search is a paid API for AI agents from agentrxi.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-15).

Searches GitHub issues for a given error message or problem, returning titles, repos, statuses, comment counts, labels, links, and excerpts sorted by most-discussed first.

## Facts

- Endpoint: GET https://agentrxi.com/v1/github/issues?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentrxi-github-issue-search-af71b285
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fyVCwas15z_3zbz0KxTAT

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 agentrxi-github-issue-search-af71b285
```

Example prompt: Search GitHub issues for 'TypeError: Cannot read properties of undefined (reading map)' and show me the most-discussed results — check both open and closed issues.

## When to prefer this

Use this endpoint when an AI agent or developer needs to quickly determine whether a specific error or bug has been reported and discussed on GitHub, especially before filing a new issue or when debugging. It is preferable to a generic web search when you want structured, ranked issue data from GitHub specifically, and ideal for developer-facing workflows where source code repositories are the authoritative discussion venue.

## Known failure modes

- No matching issues found for the query — returns empty results
- Rate limiting or GitHub API unavailability causing errors
- Overly broad query returning too many irrelevant results
- Exact-phrase match finds nothing, falls back to keyword search which may reduce precision
- Invalid repo format for the repo parameter causing a bad request error

## How this service works

Has anyone hit this error? Searches GitHub issues for an error message (exact phrase first, then keywords): title, repo, open or closed, comments, labels, link and an excerpt, most-discussed first.

## Output

A ranked list of GitHub issues (most-commented first by default) matching the error query, each including the issue title, repository name, open/closed state, comment count, labels, a direct link, and a text excerpt from the issue body.

## 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": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "q"
     ],
     "properties": {
      "q": {
       "type": "string",
       "description": "Error message or problem"
      },
      "repo": {
       "type": "string",
       "description": "Limit to owner/name"
      },
      "sort": {
       "type": "string",
       "description": "comments (default) or recent"
      },
      "limit": {
       "type": "integer"
      },
      "state": {
       "type": "string",
       "description": "open or closed"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentrxi-github-issue-search-af71b285/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentrxi.com](https://www.zero.xyz/host/agentrxi.com/llms.txt)