# ForgeMesh GitHub Repository Signal Intelligence Scanner

> ForgeMesh GitHub Repository Signal Intelligence Scanner is a paid API for AI agents from anomaly.forgemesh.io, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-13).

Analyzes a GitHub repository for momentum signals, novelty, and activity anomalies using sequence scoring algorithms

## Facts

- Endpoint: POST https://anomaly.forgemesh.io/api/repo-scan
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-github-repository-signal-intelligence-scanner-00956002
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2-Wy9QLn-ta1W3GqaJG6K

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 forgemesh-github-repository-signal-intelligence-scanner-00956002 -d '<json body>'
```

Example prompt: Can you scan the vercel/ai GitHub repo and tell me if it's showing any unusual momentum — like fork surges or hot repo signals — and give me its sequence score and novelty rating?

## When to prefer this

Use this endpoint when you need quantified anomaly scoring and momentum signals for a specific GitHub repository, particularly to detect fork surges, star velocity anomalies, or emerging hot repos. Prefer this over manual GitHub API queries when you want a pre-computed sequence score and narrative classification in a single call, especially in automated pipelines that monitor open source project health.

## Known failure modes

- Invalid repo format (not owner/repo) — likely 400 or validation error
- Repo not found or private — likely 404 or empty metrics
- Payment failure via x402 micropayment — 402 response requiring USDC payment
- Rate limiting or quota exceeded — 429 or similar
- GitHub API upstream unavailability causing stale or missing data

## How this service works

Deep anomaly scan for a single GitHub repository — velocity, fork ratio, issue flood, overnight explosion signals

## Output

Returns a JSON object containing the repo identifier, a narrative story label (e.g. 'Strong Momentum'), a domain classification, quantitative metrics (stars, age in days, language, fork ratio, stars per day), a novelty rating (low/medium/high), an array of peak window signal tags (e.g. HOT_REPO, FORK_SURGE), and an integer sequence score.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "repo": {
   "type": "string",
   "description": "GitHub repo in owner/repo format, e.g. vercel/ai"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "repo": "vercel/ai",
  "story": "Strong Momentum",
  "domain": "creator",
  "metrics": {
   "stars": 12500,
   "age_days": 365,
   "language": "TypeScript",
   "fork_ratio": 0.18,
   "stars_per_day": 34.2
  },
  "novelty": "medium",
  "peak_window": [
   "HOT_REPO",
   "FORK_SURGE"
  ],
  "sequence_score": 44
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-github-repository-signal-intelligence-scanner-00956002/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from anomaly.forgemesh.io](https://www.zero.xyz/host/anomaly.forgemesh.io/llms.txt)