MCP documentation menu

ICANN 2026 Round Applicant Guidebook (agb)

Overview

Two tools cover the ICANN 2026 Round Applicant Guidebook:

  • datapulse_agb returns a whole chapter of the Guidebook, split into modules, appendices, glossary and a SubPro topic index, plus a 2012 Round string-status reference.
  • datapulse_agb_search finds the passages that answer a question, by meaning, and returns them with a citation (chapter, section number, PDF page).

Source: Applicant Guidebook V2-2026.04.24 (24 April 2026), the authoritative version of the 2026 Round Guidebook, superseding V1-2025.12.16 (16 December 2025) and the Board-adopted V0-2025.10.30 (ICANN Board Resolution 2025.10.30.12). The chapters are generated from ICANN’s PDF; every page boundary is marked in the served text as [p. 191] and footnotes appear as [^N] references with the note text at the end of its page.

The round’s application window ran 30 April to 12 August 2026. ICANN may have published later program updates; the Guidebook text is the rules, not a status feed.

datapulse_agb

ParameterTypeRequiredDescription
chapterstringNoChapter to retrieve. Default: index (returns chapter listing with descriptions)
partintegerNoPart of the chapter, from 1 (default 1)

A chapter longer than about 40 KB is served in parts. A part ends at a section heading where one falls in its last 40% (past about 24 KB), otherwise at a paragraph or page break; a table carried into the next part has its header row repeated there, introduced by a bracketed note. The multi-part chapters are appendix 1 and module 7 (7 parts each), modules 3, 4 and 5 (4 each), appendix 3 and module 1 (3 each) and the glossary (2). Each part begins with a bracketed line naming the part, its PDF pages and the call that returns the next one, e.g. [datapulse_agb chapter="module7_string_evaluation" part 1 of 7, PDF pages 181-190; the next part is datapulse_agb(chapter="module7_string_evaluation", part=2)]. To reach a passage datapulse_agb_search returned, pick the part whose page range holds its page. Shorter chapters come back whole, with no header.

Chapters

ChapterDescription
indexChapter listing with descriptions and routing guidance (default)
overviewVersion history, preamble, executive summary (key differences from the 2012 Round), document overview
module1_applicant_journeyEnd-to-end process: eligibility (§1.1.1), USD 227,000 fee (§1.1.2), ASP (§1.1.7), every stage with expected durations (§1.2), lifecycle timelines (§1.5)
module2_general_informationResources, languages, Universal Acceptance, freedom of expression, security and stability, legal compliance, accountability mechanisms, subsequent rounds, calendar days, registry-registrar obligations
module3_application_submissionSubmission period and TAMS (§3.1), closed generics (§3.1.7), pre-submission validations and RZ-LGR (§3.1.8), IDNs (§3.1.9), fees, payments and refunds (§3.3, Table 3-2), Reveal Day, replacement period, prioritization draw, Application Change Requests (§3.8), statuses
module4_community_objectionsApplication comments, GAC Early Warnings (§4.2), GAC Consensus Advice (§4.3), singular/plural notifications (§4.4), objections and appeals (§4.5)
module5_contentionReplacement strings (§5.1), contention resolution (§5.2), .Brand string changes (§5.3), Community Priority Evaluation and scoring tables (§5.4), geographic names contention (§5.5), ICANN auction and bid credits (§5.6)
module6_applicant_evaluationBackground screening (§6.1), financial and operational evaluation (§6.2)
module7_string_evaluationString and application types (§7.1), blocked and reserved names (§7.2), .Brand eligibility (§7.3), Code of Conduct exemption (§7.4), geographic names (§7.5), variants (§7.6), name collision (§7.7), PICs and RVCs (§7.8), RSP review (§7.9), string similarity (§7.10)
appendix1_questionsComplete list of application questions by TAMS question set, with evaluation criteria
appendix2_geographicGeographic names checklist, sample government letter, Separable Country and Territory Names List
appendix3_objectionsICANN objection and appeal procedures article by article; objection and appeal timelines
appendix4_registry_agreementPointer to the 2026 Base Registry Agreement (12 March 2026) on icann.org
appendix5_financialStandard financial profile templates
appendix6_predictabilityPredictability Framework for changed circumstances
appendix7_8_coiConflict of interest rules and the service-provider code of conduct
appendix9_privacyPrivacy policy for applicant data
appendix10_termsTLD Application Terms and Conditions
appendix11_12_support_rspPointers to the Applicant Support Program and RSP Evaluation Program handbooks
glossaryDefinitions and acronyms (Table G1)
subpro_topic_indexWhich Guidebook section implements each SubPro Final Report topic
round2012_strings2012 Round gTLD string outcomes: strings still in process (which block 2026 Round applications per §7.2.1 and §7.10.3.2), delegated, terminated, not-approved and withdrawn strings. Not Guidebook text; data as of April 2026
ParameterTypeRequiredDescription
querystringYesThe question, in natural language (1-1000 characters)
limitintegerNoPassages to return, 1-20. Default 10; 0 or absent means the default, above 20 is capped
min_scorenumberNoMinimum cosine similarity, 0-1. Default 0.55; 0 disables the filter
chapterstringNoRestrict to one chapter name from the table above

Every chapter is split into passages of at most 1,000 characters (broken between paragraphs, list items or sentences, footnote definitions left out) under its heading. A table is split between whole rows, and a passage that opens inside a table repeats the table’s caption and header row; a row too long for one passage continues in the next, which names the row ((continued)). Passages are embedded in advance with BGE-M3 (1024 dimensions) on the same embedding server that powers datapulse_disputedb_search. The query is embedded the same way; passages are ranked by cosine similarity and returned as JSON:

{
  "version": "V2-2026.04.24",
  "query": "...",
  "min_score": 0.55,
  "returned": 3,
  "results": [
    {
      "score": 0.7412,
      "chapter": "module7_string_evaluation",
      "section": "7.2.1",
      "heading": "Module 7 String and Application Evaluation Procedures › 7.2 Blocked and Reserved Names Overview › 7.2.1 Blocked Names",
      "page": 191,
      "citation": "AGB V2-2026.04.24 §7.2.1 Blocked Names (p. 191)",
      "text": "..."
    }
  ]
}

A passage from the bundled 2012 string reference has no PDF page: page is absent and the citation names the reference, marked as not Guidebook text. citation names the passage exactly. When a passage needs its surrounding context (a table it references, the rest of a list), read the chapter with datapulse_agb.

Score interpretation (BGE-M3 cosine similarity): 0.72+ strong match, 0.65-0.72 relevant, 0.55-0.65 weak, below 0.55 likely irrelevant. The default min_score (0.55) keeps the useful passages and the scores sort them afterwards: the passage that answers a short factual question often scores 0.60-0.70 beside adjacent passages (an exception, a waiver, a related fee) that score within 0.03 of it, so a 0.65 floor can drop the answer (observed 2026-10-19 with “what is the application fee”: §1.1.2 with the USD 227,000 fee scored 0.64, §3.3.1 0.62, interleaved with Table 3-2 conditional-fee rows at 0.62 and 0.61). A question phrased very differently from the Guidebook’s own wording may need min_score 0.45.

When the search index or its embedding service is unavailable, the tool reports itself unavailable with the reason.

Routing guidance

Question TypeChapter
“Which section says…”, any question you cannot placedatapulse_agb_search first
Eligibility, fee overview, stages and durationsmodule1_applicant_journey
Submission mechanics, payment details, refunds, IDNs, change requestsmodule3_application_submission
Application types, .Brand, community TLDsmodule7_string_evaluation (§7.1, §7.3), module2_general_information
Objection grounds, GAC warnings, disputesmodule4_community_objections (overview) or appendix3_objections (detailed)
String contention, auctions, community prioritymodule5_contention
Background/financial screeningmodule6_applicant_evaluation
String evaluation, name collision, geographic names, blocked/reserved names, similaritymodule7_string_evaluation
Whether a string was applied for in 2012, strings still in processround2012_strings
Geographic names specificallyappendix2_geographic
Application questions and evaluation criteriaappendix1_questions
Term definitionsglossary
Which section implements a SubPro recommendationsubpro_topic_index

Scope limitations

These tools cover the 2026 Round application process and policy only. They do not cover:

  • History or outcomes of the 2012 round beyond the string-status reference in round2012_strings (refer to ICANN’s public archives)
  • Whether a specific TLD is currently delegated in the DNS root (answered by datapulse_live_dns)
  • Who applied in the 2026 Round, for which strings, and the resulting contention sets (answered by datapulse_gtld_applications and datapulse_help(topic="gtld_2026_applications"); that data is not authoritative, as ICANN is still processing the applications)
  • Program status, vendor announcements or calendar changes published after 24 April 2026
  • Blockchain or alternative namespaces (Unstoppable Domains, ENS, Handshake)

Example: a rules question with a citation

datapulse_agb_search(query="can I apply for a string that was applied for in 2012 and is still in process")
# → observed 2026-10-19: the bundled 2012 reference's "Strings still in process" (0.69) and §7.10.3.2 (p. 241, 0.61):
#   not allowed. The rule itself is §7.2.1 Blocked Names (p. 191). Then confirm the string's 2012 status:
datapulse_agb(chapter="round2012_strings")

Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026. Your AI assistant reads this page by calling datapulse_help(topic="agb").