# Signalbound Intel API

> Signalbound Intel API is a paid API for AI agents from api.signalbound.art, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-18).

Returns reveal-aware metadata, rarity tier, traits, and agent-readable intelligence for a Signalbound NFT token by ID.

## Facts

- Endpoint: POST https://api.signalbound.art/intel?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signalbound-intel-api-d64554f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qc97t-A01UvJEQeclKqF8

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 signalbound-intel-api-d64554f2 -d '<json body>'
```

Example prompt: Can you pull the full intel on Signalbound token 420 — I want to see its rarity tier, traits, and brief description?

## When to prefer this

Use this endpoint when you need structured, agent-ready intelligence for a specific Signalbound NFT token — including reveal-aware metadata, rarity scoring, and trait breakdown. Prefer this over generic NFT metadata APIs when working specifically with the Signalbound collection (token IDs 1–6666) and needing ERC-8004-compatible or holder-gated data.

## Known failure modes

- Invalid tokenId outside range 1-6666 returns an error
- Unrevealed token may return limited or placeholder metadata if reveal has not occurred
- Payment failure via x402 returns 402 status blocking access
- Missing required tokenId field returns a 400 validation error
- Holder-gated routes return restricted data if caller does not hold the token

## How this service works

Signalbound API for agent metadata, reveal-aware token reads, ERC-8004 registration files, and holder-gated tool routes.

## Output

A JSON object containing the token's name, rarity tier (e.g. common/rare/legendary), numeric rarity score, trait map (key-value pairs), a brief agent-readable description, edition label, and the caller's address if holder-gated access applies.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "tokenId"
 ],
 "properties": {
  "tokenId": {
   "type": "integer",
   "description": "Signalbound token ID (1-6666)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "tokenId",
  "name",
  "rarity_tier",
  "traits",
  "brief"
 ],
 "properties": {
  "name": {
   "type": "string"
  },
  "brief": {
   "type": "string"
  },
  "caller": {
   "type": "string"
  },
  "traits": {
   "type": "object",
   "additionalProperties": {
    "type": "string"
   }
  },
  "edition": {
   "type": "string"
  },
  "tokenId": {
   "type": "integer"
  },
  "rarity_tier": {
   "type": "string"
  },
  "rarity_score": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signalbound-intel-api-d64554f2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.signalbound.art](https://www.zero.xyz/host/api.signalbound.art/llms.txt)