---
title: "Rpc Resolve Entity"
method: POST
path: "/v1/graph/rpc/resolve"
tags: ["graph-entity"]
---

# Rpc Resolve Entity

`POST /v1/graph/rpc/resolve`

## Request

- Base URL: `https://api.bitpoort.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.bitpoort.com/v1/graph/rpc/resolve`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Resolve ``address`` to its entity/cluster via WS-C3 signal fusion.

Returns the canonical resolution block (label / type / cluster_id / confidence
/ evidence[] / as_of / resolution_method / disclaimer). An address that resolves
to nothing returns ``label=None, type="unknown", confidence=0.0`` — never an
invented identity. ``resolve_entity`` never raises, so this is a thin pass-through.

## Request body

- ResolveEntityRequest
  - `address` string, required: address to resolve
  - `chain` string

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bitpoort/apis/bitpoort-api.md) · [All operations](https://skmtc.dev/bitpoort/apis/bitpoort-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitpoort/apis/bitpoort-api/revisions/1a51d8566777?raw)