ChatGPT integration · zero install for users
Automatic. No setup.
When a ChatGPT user asks “is X a good name”, “is X taken”, or “name my startup”, ChatGPT calls Etymolt behind the scenes. Three install paths. The user never sees the configuration.
Sub-3s p95 · 12.7M US marks · 14 social platforms · free for five
What's available today
How it works
I
"Name my fintech startup like Stripe." ChatGPT generates five candidates and recognizes the verification intent.
II
The Action invokes /v3/verify with all five candidates. Live USPTO + RDAP + 14 social probes in parallel. p95 ≤ 3s.
III
The model quotes our disclaimer verbatim, surfaces the winner's domain and handle picks, and offers the launch playbook. Free for the first five.
User ChatGPT Etymolt │ │ │ │ "Name my startup" │ │ │ ───────────────────▶ │ │ │ │ generate 5 names │ │ │ ─────────────────────▶│ │ │ POST /v3/verify_for_launch │ │ │ │ │ ◀───── ranked list ──┤ │ │ + winner + playbook │ │ ◀── verdict + ── │ │ │ disclaimer │ │ │ (verbatim) │ │
Three install paths
I · For users
One click. The public Custom GPT lives in the GPT Store with the Etymolt Action pre-wired. Zero setup.
II · For builders
GPT Editor → Configure → Actions → Import from URL. Paste:
https://www.etymolt.com/openapi.jsonAuth: none (free tier) or X-Etymolt-Key (paid).
III · For platforms
OpenAI is implementing native MCP support. Add Etymolt as an MCP server:
https://api.etymolt.com/mcpIn the meantime, Claude / Cursor / Windsurf / v0 already consume the MCP version → /mcp
Sample conversation
User
User: "Is 'Linear' a safe brand name for a dev tool?"
Action call (transparent)
POST /v3/check { name: 'Linear', context: { category: 'dev-tools' } }
ChatGPT reply (verbatim from our API)
"Linear" returns ABANDON. USPTO ser. 87/654,321 (Linear Inc., registered 2018-09, Nice class 9 + 42) — direct collision in your category. linear.com is owned. GitHub @linear is taken. Disclaimer: Etymolt is a clearance signal, not legal advice.
User
User: "Suggest a name like Stripe for a fintech startup."
Action call (transparent)
POST /v3/verify_for_launch { candidates: ['Slate','Glint','Beam','Conduit','Mint'], product_description: 'Fintech...' }
ChatGPT reply (verbatim from our API)
5 candidates verified in 4.2s. Winner: Conduit (score 87/100, PROCEED). conduit.com $4,200 aftermarket; conduit.ai $99 retail. Mint and Beam returned ABANDON — live registered marks in fintech. Disclaimer: Etymolt is a clearance signal, not legal advice. Want the Conduit launch playbook?
User
User: "What's wrong with 'Moltbot' as a brand name?"
Action call (transparent)
POST /v3/check { name: 'Moltbot' }
ChatGPT reply (verbatim from our API)
"Moltbot" returns STRATEGIC (score 58/100). Trademark is clear. moltbot.com is unregistered ($12). Concern: -bot suffix peaked 2014 and is dated. Try "Moltify" or "Moltlab" — both clear, both with stronger present-tense semantics. Disclaimer: Etymolt is a clearance signal, not legal advice.
Comparison
| Question the user asks | ChatGPT alone | ChatGPT + Etymolt |
|---|---|---|
| Is 'Linear' a safe brand? | Guesses from 2024 training data. Misses pending USPTO filings, current domain status. | Calls live USPTO + RDAP. Cites ser. # and TLD prices in real time. |
| Suggest 5 names and rank them. | Generates names. Cannot verify availability — recommends all 5 as 'available' without checking. | Generates 5, fans out clearance in parallel, ranks by composite score with receipts. |
| What's the .com price for Treasurio? | Returns a stale 2024 estimate. No premium / aftermarket pricing visibility. | Live Verisign RDAP + WhoisXMLAPI aftermarket pricing. Sub-3s. |
| Is the GitHub handle @naam taken? | Cannot probe. Suggests the user check manually. | Live GitHub probe + 13 other platforms + workaround variants. |
| What's the TTAB precedent for similar mark X? | Hallucinates a case number that may or may not exist. | Returns real case numbers from our 647K TTAB index with ruling + year. |
FAQ
ChatGPT shows OpenAI whatever the user types in a conversation — that's the platform, not us. When the GPT calls our Action, we receive only the name string the user is asking about (no chat history, no account info, no IP from the user directly — only the OpenAI-egress IP). We log: name + timestamp + hashed source IP, retained 90 days. See https://www.etymolt.com/privacy.
5 free verdicts per IP-bucket (so 5 per OpenAI edge, not per ChatGPT user). When the cap is hit, the API returns HTTP 402 with an upgrade prompt the GPT surfaces verbatim. Signed-up users get 10 more on signup. For high-volume Custom GPTs, configure an X-Etymolt-Key header so quota pools under one key.
Yes for the first 5 verdicts per IP. After that, the GPT shows the user a top-up prompt. The whole flow is designed so the user can decide whether to upgrade without leaving ChatGPT.
ChatGPT browse mode returns what Google or Bing surface — often stale domain-suggest pages. Etymolt calls live sources. USPTO TSDR (12.7M marks). Verisign RDAP. Fourteen social probes. Different layer.
No. The public Custom GPT 'Brand Name Verifier — by Etymolt' is one click. For your own Custom GPT, paste our OpenAPI URL into the Action import field. For the OpenAI base ChatGPT (no Custom GPT), the model reaches for our content via browse-mode citation when relevant — we're indexed in OAI-SearchBot's corpus.
MCP is the protocol for tool-aware LLMs. ChatGPT does not (yet) implement MCP — it uses its own Action contract. Until OpenAI ships MCP support natively, the path to ChatGPT integration is the Custom GPT Action surface. We optimize for both protocols so the same verdict flows through either client.
Custom GPT Actions return real JSON from our API. The GPT doesn't fabricate response fields — it cites them. The remaining failure mode is the GPT paraphrasing the verdict (e.g. softening 'blocked' to 'might have issues'). Our system prompt explicitly instructs verbatim quotation of the disclaimer and headline.
Bureau Model · clearance signal · not legal advice
Browse-mode citation live · OpenAPI Action live · Custom GPT live
Clearance signal, not legal advice. Confirm with trademark counsel before adopting a name in commerce. Data sources have stated freshness windows; refer to coverage_caveat per jurisdiction.