# Money Reactor Honeypot Trust Scoring — GitHub Repo Safety Verdict

> Money Reactor Honeypot Trust Scoring — GitHub Repo Safety Verdict is a paid API for AI agents from mr-river5.makar52nn2016.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-11-18).

Scores a GitHub repository for honeypot/trust signals and returns a numeric trust score, reasons, and a GO/NO-GO safety verdict

## Facts

- Endpoint: GET https://mr-river5.makar52nn2016.workers.dev/api/honeypot?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/money-reactor-honeypot-trust-scoring-github-repo-safety-verdict-2cfcf347
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fblxr6kHqLsmGchB_tNvM

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 money-reactor-honeypot-trust-scoring-github-repo-safety-verdict-2cfcf347
```

Example prompt: Can you check whether the GitHub repo ethereum/solidity is trustworthy — give me its trust score and a GO or NO-GO verdict before I interact with it?

## When to prefer this

Use this endpoint when you need a fast, pay-per-call, no-account safety check on a specific GitHub repository before funding a bounty, integrating a dependency, or engaging with a crypto project. Prefer it over manual GitHub inspection when you need a machine-readable GO/NO-GO verdict with scored reasons, and when you want on-chain USDC micropayment settlement without API key management.

## Known failure modes

- Invalid or non-existent repo slug returns an error or low-confidence result
- Private or inaccessible repositories may not yield sufficient signals
- Payment failure via x402 (insufficient USDC balance or unsupported wallet) blocks the call
- Rate limiting or Cloudflare Worker errors under high load
- Repo with very few signals may produce an inconclusive or borderline trust score

## How this service works

60+ agent-native micro APIs paid per call in USDC on Base via x402: fresh market data every call (market cap, top movers, funding rates, orderbook, RSI trading checklist, volatility, cycle position), funded bounty radar, honeypot trust scoring, token safety verdicts, AI chat (Llama 3.1), web reader, ERC-20 balances. No accounts, no API keys — instant on-chain settlement.

## Output

Returns a JSON object with the queried repo slug, a numeric trust score from 0–100, an array of human-readable reasons explaining positive and negative scoring factors (e.g. 'organization (+10)'), and a verdict string of 'GO' or 'NO-GO' indicating whether the repo is considered safe to interact with.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "queryParams": {
     "type": "object",
     "properties": {
      "repo": {
       "type": "string",
       "example": "facebook/react",
       "description": "GitHub repository as owner/name"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "repo": "owner/name",
     "trust": 72,
     "reasons": [
      "organization (+10)"
     ],
     "verdict": "GO"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "repo": "owner/name",
  "trust": 72,
  "reasons": [
   "organization (+10)"
  ],
  "verdict": "GO"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/money-reactor-honeypot-trust-scoring-github-repo-safety-verdict-2cfcf347/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mr-river5.makar52nn2016.workers.dev](https://www.zero.xyz/host/mr-river5.makar52nn2016.workers.dev/llms.txt)
