> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve ENS Name

Resolve an ENS name (e.g. vitalik.eth) to its Ethereum address. Use this to turn a human-readable name into the 0x address other actions need. Ideal for: accepting names instead of addresses, identity lookups, address book resolution.

![Resolve ENS Name logo](https://ai-icon.b3.fun/logo/ethereum)
Catalog action EVM Onchain

Resolve an ENS name (e.g. vitalik.eth) to its Ethereum address. Use this to turn a human-readable name into the 0x address other actions need. Ideal for: accepting names instead of addresses, identity lookups, address book resolution.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `resolve-ens` |
| Category | EVM Onchain |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `blockchain`, `evm`, `ens`, `name`, `identity`, `address`, `resolve`, `query`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | `string` | Yes | ENS name to resolve, e.g. "vitalik.eth". Normalized \(ENSIP-15\) before lookup. |
| `coinType` | `number` | No | Optional ENSIP-9 coin type for a chain-specific address record. Omit for the default Ethereum address. |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | `string` | Yes | The normalized name that was looked up |
| `address` | `string \| null` | Yes | The resolved 0x address, or null when the name has no address record |
| `resolved` | `boolean` | Yes | True when the name resolved to an address |

## Examples

**Workflow node**

```json
{
  "type": "resolve-ens",
  "payload": {
    "name": "vitalik.eth"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/resolve-ens/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "name": "vitalik.eth"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.