Namefi · Authentication Profile

Namefi Authentication

Authentication

Authentication methods for Namefi API

Namefi declares 3 security scheme(s) across its OpenAPI definitions.

Domain RegistrarTokenized DomainsAI AgentsOn‑chain Domains
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

API Key apiKey
EIP-712 other
SIWE http-bearer

Source

Authentication Profile

Raw ↑
generated: '2026-11-19'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.namefi.io/docs/02-authentication
sources:
- https://docs.namefi.io/docs/02-authentication
- https://docs.namefi.io/docs/02b-siwe-authentication
- https://docs.namefi.io/docs/02a-eip712-signing
- https://docs.namefi.io/docs/02c-prepare-auth-requests
description: Authentication methods for Namefi API
schemes:
- type: apiKey
  name: API Key
  evidence: The simplest authentication method. Works for all operations including DNS record creation, updates, deletes, domain registration,
    and parking.
  location: header
  header: x-api-key
  how_to_obtain: Generate an API key from the API keys management page; the key inherits permissions from the wallet that generated it.
- type: other
  name: EIP-712
  evidence: EIP-712 signs a typed-data envelope per request. The current source of truth for the domain and types is the live helper API.
  location: header
  header: x-namefi-signer, x-namefi-signature, x-namefi-eip712-type
  how_to_obtain: Obtain the signing domain and types from the live helper endpoints (GET /v-next/eip712/domain, GET /v-next/eip712/types, GET
    /v-next/eip712/types-for-method) and sign the envelope with an external wallet, then include the signer address, signature, and primary type
    in the respective headers.
- type: http-bearer
  name: SIWE
  evidence: SIWE (EIP-4361) gives you a session token after one ERC-191 personal_sign signature. Use it for protected operations that do not require
    EIP-712.
  location: header
  header: x-namefi-siwe-token
  how_to_obtain: 'Follow the SIWE flow: GET /v-next/siwe/allowed-chains, GET /v-next/siwe/nonce, GET /v-next/siwe/message, sign the messageString
    with personal_sign, POST /v-next/siwe/verify, and reuse the returned token.'
docs: https://docs.namefi.io/docs/02-authentication

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/namefi-io-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.