# 100BTC Identity Resolve

> 100BTC Identity Resolve is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Resolves a Base chain Ethereum address to aggregated on-chain identity data using web3.bio and Basenames sources

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/identity/resolve?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-identity-resolve-852e102e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Kvnp4yoQVCe-CZh_VCrRL

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 100btc-identity-resolve-852e102e -d '<json body>'
```

Example prompt: Can you resolve the Base chain address 0x1234567890abcdef1234567890abcdef12345678 and tell me what on-chain identities are linked to it — check both web3.bio and Basenames?

## When to prefer this

Choose this endpoint when you need to resolve a Base chain (chain ID 8453) Ethereum address to human-readable on-chain identities using both web3.bio and Basenames as sources. Prefer it over generic ENS resolvers when the target address is on Base and you want multi-source aggregation with conflict detection. It is read-only and idempotent, making it safe to call repeatedly for enrichment pipelines.

## Known failure modes

- Invalid address format (not matching 0x + 40 hex chars) returns validation error
- chain_id must be exactly 8453 (Base); other chain IDs rejected
- Address not found in any source returns empty identities array with sources still reporting OK
- Upstream web3.bio or Basenames service unavailable may return partial results or error
- Payment failure via x402 returns HTTP 402 and no data

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

Returns a JSON object containing the queried address, status of each identity source (web3bio and basenames, each 'OK' or error), a list of resolved identity records, any conflicts between sources, count of rejected claims, and an execution mode label (READ_ONLY).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$"
  },
  "chain_id": {
   "type": "integer",
   "const": 8453
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "address": "0x1111111111111111111111111111111111111111",
  "sources": {
   "web3bio": "OK",
   "basenames": "OK"
  },
  "conflicts": [],
  "execution": "READ_ONLY",
  "identities": [],
  "rejected_claims": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-identity-resolve-852e102e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)