enstate ENS Profile by Address

enstate/profile-by-address

The primary ENS name of an Ethereum address and that name's public records, from enstate.rs: display name, avatar and header URLs, content hash, resolver, per-chain addresses and text records. Addresses without a primary name return an error. Reverse records are only returned when the address owns them. Returns every raw text record keyed by record name plus per-chain addresses and a freshness timestamp, where ensdata/profile returns a flat summary of the common ones. Records are self-published and public and can include an email address when the owner set one.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

enstate.rs

ENS name and address records from the public enstate.rs API (https://enstate.rs). Served by Eden Engine; not an official enstate product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "enstate/profile-by-address" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "enstate/profile-by-address" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "enstate/profile-by-address", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "enstate/profile-by-address", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0026

Updated: Oct 21, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$",
      "description": "Ethereum address: 0x followed by 40 hex digits."
    }
  },
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "required": [
    "name",
    "address",
    "display",
    "records",
    "chains",
    "fresh",
    "resolver",
    "errors"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "fresh": {
      "type": "number"
    },
    "avatar": {
      "type": "string"
    },
    "chains": {
      "type": "object"
    },
    "errors": {
      "type": "object"
    },
    "header": {
      "type": "string"
    },
    "address": {
      "type": "string"
    },
    "display": {
      "type": "string"
    },
    "records": {
      "type": "object"
    },
    "resolver": {
      "type": "string"
    },
    "contenthash": {
      "type": "string"
    }
  },
  "description": "Flat object of public ENS records.",
  "additionalProperties": true
}