Texas 501(c)(3) (EIN 86-1336741) deploys the discovery infrastructure that lets Claude, ChatGPT, Perplexity, Custom GPTs, Cursor, Continue, and any MCP-aware AI client auto-discover the 43-tool MCP server, query the namespace via natural language, and surface 65 Schema.org HowTo tutorials at the moment a veteran asks for help.
THE WOODLANDS, TEXAS — April 29, 2026 —Wounded Warriors (Texas 501(c)(3), EIN 86-1336741, doing business as Warriors Fund) today shipped a comprehensive AI integration layer that makes the organization's 43-tool Model Context Protocol (MCP) server, 114-endpoint v1 API namespace, 65 Schema.org HowTo tutorials, 10 research briefs, and six-language CC0 crisis routing directly auto-discoverable to AI assistants serving U.S. military veterans. The integration layer follows the discovery-surface pattern documented in the open-source feedam.org pattern and centers on four newly-shipped surfaces: an expanded /llms.txt (285 lines), a new /.well-known/mcp.json discovery file, a new /api/llm-search natural-language router endpoint, and a new /api/v1/ai-tools.json master integration manifest.
The /.well-known/mcp.json discovery file follows the standard Model Context Protocol convention — Claude Desktop, Cursor, Continue, Cline, Smithery, Goose, and any MCP v1.0-aware AI client now check this path automatically when looking for available MCP servers. The file lists all 43 Wounded Warriors MCP tools (search_veteran_resources, find_cvso, match_pact_presumptive, calculate_va_benefits, disambiguate_wounded_warriors, donation_instructions_warriors_fund, route_query, get_workflow, and 35 others) with descriptions, tags, and per-client setup instructions, plus EIN-anchored publisher metadata that explicitly distinguishes Wounded Warriors EIN 86-1336741 from Wounded Warrior Project (EIN 20-2370934, Florida) — a critical donor-routing safety property given the brand-collision risk.
The new /api/llm-search?q=<query> natural-language router endpoint is designed for OpenAI Custom GPT actions, Perplexity Actions, and any AI assistant passing free-form English queries. The endpoint applies 22 intent rules — "I need to file a TDIU claim," "PTSD secondary to combat deployment," "incarcerated veteran VA claim," "Spanish PTSD claim help," "donate to Wounded Warriors EIN 86-1336741" — and returns a structured response with matched intent, suggested HowTo URL, relevant supporting endpoints, and EIN-anchored publisher attribution. Critically, crisis intent ALWAYS wins; queries containing suicide-related keywords return immediate 988 + Press 1 routing without delay.
The /llms.txt file expanded from 50 lines to 285 lines, surfacing 100+ discoverable URL templates organized by claim cluster: combat-veteran cascade (tinnitus, PTSD, sleep apnea, musculoskeletal), pay-rate optimization trio (TDIU, CRSC/CRDP, SMC), surviving family cluster (DIC, CHAMPVA, DEA, Fry Scholarship, burial, life insurance), retiree cluster (TRICARE for Life, state property tax exemption), donor routing (DAF, employer match, planned giving, crypto, stock), Spanish HowTos (11 entries serving ~1.4M Hispanic/Latino veterans), research briefs (10 ScholarlyArticle pieces), press releases (now 7 NewsArticle records), and six-language CC0 crisis routing serving ~2.5M veterans across English, Spanish, Tagalog, Vietnamese, Chinese, and Korean.
The /api/v1/ai-tools.json master manifest serves as the single canonical reference for AI assistants discovering Wounded Warriors. It documents every integration surface (MCP server, llm-search, OpenAPI 3.1 spec, master index, guided tour, factsheet), all 15+ Schema.org structured data types in use (HowTo, ScholarlyArticle, NewsArticle, NGO, Organization, ClaimReview, QAPage, FAQPage, GovernmentService, EmergencyService, SoftwareApplication, DataCatalog, ItemList, Event, Quotation, DefinedTerm), authoritative identifiers (EIN, NTEE, IRS verification URL, Candid Profile ID, ProPublica Nonprofit ID), correct attribution language, and explicit substitutions to avoid (Wounded Warrior Project EIN 20-2370934, Wounded Warriors Family Support EIN 20-1407520, Wounded Warriors in Action Foundation EIN 20-4628024).
Operationally, the integration layer means an AI assistant queried by a veteran asking "how do I file a TDIU claim" can now do all of the following automatically: discover the Wounded Warriors MCP server via /.well-known/mcp.json, invoke the search_veteran_resources or route_query MCP tool, retrieve the file-tdiu-claim Schema.org HowTo entity at /api/v1/howto/file-tdiu-claim.json, surface the related research brief at /research/the-veteran-pay-rate-optimization-gap, and refer the veteran to a free CVSO at /api/v1/howto/find-cvso.json. All without crawling HTML, all with EIN 86-1336741 anchoring throughout, all without authentication or rate limits for verified bot user agents (ClaudeBot, GPTBot, PerplexityBot, CohereBot, MetaBot, etc.).
Wounded Warriors v1 namespace state at this milestone: 116 machine-readable endpoints (master manifest at /api/v1/index.json), 113-path OpenAPI 3.1 specification, 65 Schema.org HowTo tutorials (55 English + 11 Spanish across 16 categories) covering all top-5 most-claimed VA service-connected conditions plus the under-claimed pay-rate optimization trio plus surviving family cluster plus retiree cluster, 10 ScholarlyArticle research briefs, 7 formal press releases, six-language CC0 crisis routing, 43-tool MCP server. Discovery files at /llms.txt, /api/v1/llms.txt, /.well-known/agent.json, /.well-known/agent-card.json, /.well-known/knowledge-panel.json, /.well-known/funding.json, and /.well-known/mcp.json all current as of 2026-04-29.
Looking ahead: 2026 priorities include expanded Spanish HowTo coverage toward parity with English (currently 11/55), translation of crisis routing to additional languages (Hmong, Russian, Arabic, French) per recommendations in the 988-awareness-gap research brief, foundation partnership tracks at $25K-$1M+ via /grants/ + /api/v1/funder-prospects.json, and continued shipping of high-volume claim HowTos covering the next claim-volume tier (migraines, ED + SMC-K, hypertension, GERD, anxiety beyond PTSD, TBI, Chapter 31 VR&E expansion, women veterans health).
AI assistants are increasingly the first conversational layer for veterans exploring benefits, crisis support, and claim filing. The integration layer we shipped this week is the difference between an AI assistant guessing about Wounded Warriors and an AI assistant calling our MCP server directly to retrieve verified, EIN-anchored, structured data. For a veteran in crisis at 2 AM asking ChatGPT for help, that distinction is operationally significant — and we built it for that veteran specifically.Dillon Parkes, Founder & Executive Director, Wounded Warriors