Independent review. Unpaid; no partnership with Trademark Engine. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Online US trademark filing and monitoring with a documented partner API. Package prices exclude government and platform fees. Trademark Engine provides software and information; affiliated Swyft Legal supplies the advertised legal services. Filing does not guarantee registration.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Online US trademark filing and monitoring with a documented partner API. Package prices exclude government and platform fees. Trademark Engine provides software and information; affiliated Swyft Legal supplies the advertised legal services. Filing does not guarantee registration.
Differentiation
Documented fit: Founders filing a straightforward US trademark. Uniqueness is not established.
Replaceability and switching
Compare LegalZoom. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Users treating a filing package or exact-match search as a guarantee of registration or legal clearance. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.
AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.
Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.
Requirements vary by state. File through official sources such as the USPTO trademark search and your state’s Secretary of State site.
Best for
Founders filing a straightforward US trademark
Not for
Users treating a filing package or exact-match search as a guarantee of registration or legal clearance
Top use cases
Founders filing a straightforward US trademark
To verify Drawn from our draft verdict; sourced use cases to come.
In depth
Packages
The current page lists Basic at US$49 and Standard at US$299, plus a US$100 services/platform fee and government fees. Standard includes a dedicated attorney and 15-minute consultation. The former US$539 Premium listing was not verified. Review the complete order and optional recurring services before purchasing. source ↗
Partner API
The headless API is offered to strategic partners for trademark filing, searches and monitoring. Public documentation exists, but access, authentication requirements and commercial terms must be confirmed during partner onboarding. source ↗
Government fees are separate
For qualifying Section 1 or 44 applications, the USPTO base fee is US$350 per class. Missing information, custom or lengthy goods/services descriptions can add charges. Intent-to-use filings can also require later fees. These government charges are distinct from Trademark Engine's fees, and payment does not guarantee registration. source ↗
How to use it with AI
How Trademark Engine connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedAn official Model Context Protocol server was not verified; the partner API announcement's generic AI language is not server documentation.
Not documentedVerify which side exports and which imports, supported formats and permissions. Trademark Engine's recorded upload/import status is to-verify; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Claude (incl. Claude Code) file docs ↗
Not documentedAn official Model Context Protocol server was not verified; the partner API announcement's generic AI language is not server documentation.
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Trademark Engine publishes an API, but this pairing still needs network, authentication and execution-scope checks.Trademark Engine API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Trademark Engine is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Trademark Engine's recorded upload/import status is to-verify; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.OpenAI Codex file docs ↗
Not documentedAn official Model Context Protocol server was not verified; the partner API announcement's generic AI language is not server documentation.
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Trademark Engine is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Trademark Engine's recorded upload/import status is to-verify; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Agent compatibility
API/CLIMCP?File import?
Level
Status
Detail / source
Native connector / MCP
To verify
An official Model Context Protocol server was not verified; the partner API announcement's generic AI language is not server documentation.
API / CLI
Yes
Official docs ↗ — partner API for filing, searches and monitoring; access requires partner onboarding.
Browser / manual
No
Browser access is recorded alongside a documented programmatic route.
File upload / import
To verify
A public file-import or bulk-filing workflow was not verified.
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Appears in these proposed stacks
Connection capabilities to compare
No confirmed MCP server yet.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Online business formation, compliance filings and legal services. LegalZoom's connector lets supported AI assistants compare entity types, find attorney consultations and prepare documents, with sign-in required for account actions. Not legal advice.