Inspect Multiple Names

curl --request POST \ --url https://api.nameguard.io/bulk-inspect-names \ --header 'Content-Type: application/json' \ --data '{ "names": [ "vitalìk.eth", "nick.eth" ], "network_name": "mainnet" }'

{ "results": [ { "risk_count": 123, "highest_risk": { "message": "<string>", "check_name": "<string>" }, "name": "<string>", "namehash": "<string>", "inspected": true, "title": "<string>", "subtitle": "<string>", "beautiful_name": "<string>" } ] }

Inspects up to 250 names at a time with NameGuard.

Provides NameGuardReport with inspected field equal to false if the name is uninspected; else returns a ConsolidatedNameGuardReport for each name provided in request.names, including:

The details of all checks performed on a name that consolidates all checks performed on labels and graphemes in this name.

Each ConsolidatedNameGuardReport returned represents an equivalent set of checks as a NameGuardReport. However:

A NameGuardReport contains a lot of additional data that isn’t always needed / desired when a ConsolidatedNameGuardReport will do.

When NameGuard only needs to return a ConsolidatedNameGuardReport, some special performance optimizations are possible (and completely safe) that help to accelerate responses in many cases.

This endpoint will attempt automated labelhash resolution through the ENS Subgraph, using the network specified in request.network_name.

curl --request POST \ --url https://api.nameguard.io/bulk-inspect-names \ --header 'Content-Type: application/json' \ --data '{ "names": [ "vitalìk.eth", "nick.eth" ], "network_name": "mainnet" }'

Body

application/json

names

string[]

required

Maximum array length: 250

Example:

["vitalìk.eth", "nick.eth"]

network_name

enum<string>

required

Available options:

mainnet,

sepolia

Response

Successful Response

Bulk name analysis results.

results

ConsolidatedNameGuardReport · object[]

required

Show child attributes

Documentation Index

Body

Response