# RobinX Deployer Score

> RobinX Deployer Score is a paid API for AI agents from api.robinx.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns an on-chain performance score for a deployer address on Robinhood Chain (chain 4663), showing how many of their token launches survived vs died and their overall credibility grade.

## Facts

- Endpoint: GET https://api.robinx.io/deployer/%7Baddress%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinx-deployer-score-5beae36a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mENbvijw4jNEIFzEpEztv

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 robinx-deployer-score-5beae36a
```

Example prompt: Can you pull the RobinX deployer score for 0xAbCd1234... on Robinhood Chain and tell me how many of their token launches are still alive versus dead?

## When to prefer this

Use this endpoint when you need objective, on-chain graded reputation data for a specific deployer address on Robinhood Chain (chain 4663) — particularly when you want to verify track records beyond follower counts or social signals. Prefer this over general blockchain explorers when you specifically need a credibility score based on token survival rates.

## Known failure modes

- Invalid or malformed wallet address returns an error or empty result
- Address not found on Robinhood Chain (chain 4663) — no deployment history
- Payment failure via x402 protocol blocks the response
- Chain data unavailable or indexer lag causes stale or missing scores

## How this service works

RobinX grades every X (Twitter) caller and every deployer on Robinhood Chain (chain 4663) against real on-chain price since genesis — who called it early, who chased, whose launches survive. Receipts, not follower counts. Per call over x402, or one line of MCP.

## Output

A JSON object with the deployer's aggregate score (0-100), total tokens launched, count of surviving ('real') tokens, count of dead tokens, and a signal label identifying the entity type as 'deployer'.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "dead": 9,
   "real": 3,
   "score": 78,
   "launched": 12
  },
  "signal": "deployer"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinx-deployer-score-5beae36a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.robinx.io](https://www.zero.xyz/host/api.robinx.io/llms.txt)