QName AI WHOIS API

QName AI (qname.ai) is a domain-research workspace whose WHOIS/RDAP capability is exposed programmatically through a small, approval-gated REST API and an agent-native CLI (@qname/cli). It offers authenticated single-domain and batch WHOIS/domain lookups plus a domain-traffic scope, consumable via the CLI, an installable Agent Skill, or direct REST calls.

QName AI WHOIS API publishes 1 API on the APIs.io network. Tagged areas include WHOIS, rdap, domain-research, Domain Search, and batch-lookup.

QName AI WHOIS API’s developer surface includes support, CLI, authentication, changelog, and 20 more developer resources.

27.5/100 thin Agent 12/100 agent aware Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
1 APIs 1 MCP Servers
WHOISrdapdomain-researchDomain Searchbatch-lookupCLIAgent ToolingAgentSkillllms-txtDeveloper ToolsDomain Intelligence

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/qname: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

QName AI WHOIS REST API

Approval-gated REST API for WHOIS/RDAP lookups: GET /api/whois/{domain} (single), POST /api/whois/batch (batch), and GET /api/domain-traffic (traffic). Requires an admin-approve...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Pricing Plans 1

Published pricing tiers and plan structures.

Qname Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Qname Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Qname Authentication

0 schemes

SECURITY

Qname Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
name: QName AI WHOIS API
description: QName AI (qname.ai) is a domain-research workspace whose WHOIS/RDAP capability is exposed programmatically through
  a small, approval-gated REST API and an agent-native CLI (@qname/cli). It offers authenticated single-domain and batch WHOIS/domain
  lookups plus a domain-traffic scope, consumable via the CLI, an installable Agent Skill, or direct REST calls.
url: https://raw.githubusercontent.com/api-evangelist/qname/refs/heads/main/apis.yml
created: '2026-09-13'
modified: '2026-09-14'
specificationVersion: '0.21'
tags:
- WHOIS
- rdap
- domain-research
- Domain Search
- batch-lookup
- CLI
- Agent Tooling
- AgentSkill
- llms-txt
- Developer Tools
- Domain Intelligence
tags_raw:
- whois
- rdap
- domain-research
- domain-search
- batch-lookup
- cli
- agent-tooling
- agent-skill
- llms-txt
- developer-tools
- domain-intelligence
apis:
- name: QName AI WHOIS REST API
  description: 'Approval-gated REST API for WHOIS/RDAP lookups: GET /api/whois/{domain} (single), POST /api/whois/batch (batch),
    and GET /api/domain-traffic (traffic). Requires an admin-approved API key (qname_ prefix) and enforces per-request and
    daily quotas.'
  humanURL: https://qname.ai/cli
  baseURL: https://qname.ai
  tags:
  - WHOIS
  - rdap
  - domain-research
  - Domain Search
  - batch-lookup
  - CLI
  - Agent Tooling
  - AgentSkill
  - llms-txt
  - Developer Tools
  - Domain Intelligence
  tags_raw:
  - whois
  - rdap
  - domain-research
  - domain-search
  - batch-lookup
  - cli
  - agent-tooling
  - agent-skill
  - llms-txt
  - developer-tools
  - domain-intelligence
  properties:
  - type: Documentation
    url: https://qname.ai/cli
  - type: Documentation
    url: https://github.com/QNameAI/qname-cli
  - type: LLMsTxt
    url: https://qname.ai/llms.txt
  - type: AgentSkill
    url: https://github.com/QNameAI/qname-cli
maintainers:
- FN: QName AI
  email: hello@qname.ai
  url: https://qname.ai
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 88
  at: '2026-09-13T14:20:00.634Z'
common:
- type: Website
  url: https://qname.ai
- type: DomainSecurity
  url: security/qname-domain-security.yml
- type: DeveloperPortal
  url: https://qname.ai/cli
- type: GitHubOrganization
  url: https://github.com/QNameAI
- type: Roadmap
  url: https://qname.ai/roadmap
- type: TermsOfService
  url: https://qname.ai/terms
- type: PrivacyPolicy
  url: https://qname.ai/privacy
- type: Support
  url: https://qname.ai/contact
- type: Login
  url: https://qname.ai/auth/login
- type: LLMsTxt
  url: llms/qname-llms.txt
- type: AgentSkill
  url: skills/qname-cli.md
- type: Packages
  url: packages/qname-packages.yml
- type: CLI
  url: cli/qname-cli.yml
- type: Authentication
  url: authentication/qname-authentication.yml
- type: Conventions
  url: conventions/qname-conventions.yml
- type: ErrorCatalog
  url: errors/qname-problem-types.yml
- type: DataModel
  url: data-model/qname-data-model.yml
- type: MCPServer
  url: mcp/qname-mcp.yml
- type: ChangeLog
  url: changelog/qname-changelog.yml
- type: ChangeLog
  url: https://qname.ai/changelog
- type: Plans
  url: plans/qname-plans-pricing.yml
- type: RateLimits
  url: rate-limits/qname-rate-limits.yml
- type: Lifecycle
  url: lifecycle/qname-lifecycle.yml
- type: Conformance
  url: conformance/qname-conformance.yml
x-enrichment:
  date: '2026-09-14'
  status: enriched
  artifacts_added: 17
  pass: local-v3

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/qname"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/qname/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/qname/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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. See our Privacy Policy and Terms.

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