--- title: "Press kit" canonical: "https://canmyagentuse.com/press" contentKind: "page" locale: "en" description: "Boilerplate, fact sheet, naming rules, brand assets, and catalog figures for writing about the independent compatibility catalog." llmSummary: "Press kit for Can My Agent Use: approved boilerplate, fact sheet, naming rules, brand assets, palette, milestones, and contact routes." updatedAt: "2026-08-29T00:00:00.000Z" verifiedAt: "2026-08-29" tags: ["press", "brand", "media"] --- # Press kit Everything needed to write about Can My Agent Use accurately: boilerplate, the fact sheet, naming rules, brand assets, and current catalog figures. Quote it, screenshot it, link it — no permission request needed for editorial coverage. Pointing an agent here instead? Use the [canonical prompts](/prompt.md). ## Catalog figures - Catalog capabilities: 125 - Exact product columns: 31 - Evidence Atlas exact surfaces: 93 - Evidence Atlas compatibility cells: 4557 - Public source records: 183 Figures are generated from the catalog at build time. Catalog coverage is research progress, never usage share. ## Boilerplate ### Short (43 words) Can My Agent Use (canmyagentuse.com) is an independent compatibility catalog for AI agents. It answers whether exact web, desktop, and CLI agent products support a capability, and it links every published answer to dated public evidence. Cells without a reviewed source stay unknown. ### Standard (104 words) Can My Agent Use (canmyagentuse.com) is an independent compatibility catalog for AI agents. It answers whether exact web, desktop, and CLI agent products support a capability, and it links every published answer to dated public evidence. Cells without a reviewed source stay unknown. The catalog records support as yes, partial, no, unknown, or not applicable, and keeps plan, platform, and configuration limits attached to each answer. People read the HTML catalog; agents read the same records as Markdown twins, a versioned JSON API, and llms.txt indexes. Can My Agent Use is not affiliated with any AI vendor, and a listing is not an endorsement. ### Extended (168 words) Can My Agent Use (canmyagentuse.com) is an independent compatibility catalog for AI agents. It answers whether exact web, desktop, and CLI agent products support a capability, and it links every published answer to dated public evidence. Cells without a reviewed source stay unknown. The catalog records support as yes, partial, no, unknown, or not applicable, and keeps plan, platform, and configuration limits attached to each answer. People read the HTML catalog; agents read the same records as Markdown twins, a versioned JSON API, and llms.txt indexes. Can My Agent Use is not affiliated with any AI vendor, and a listing is not an endorsement. Every non-unknown cell carries a written note, an exact product target, an environment profile, and a dated reference to public evidence such as vendor documentation or release notes. A separate Evidence Atlas snapshot records dated research across exact product surfaces, including explicit non-support and open evidence gaps. The catalog first published on August 28, 2026 and keeps its methodology, coverage measures, and contradictions public. ## Fact sheet | Fact | Value | | --- | --- | | Product name | Can My Agent Use | | Domain | canmyagentuse.com | | What it is | An independent compatibility catalog for chat, desktop, and CLI AI agent products. | | First published | 2026-08-28 | | Unit of record | One capability on one exact product surface (web, desktop, or CLI), never a provider family. | | Support statuses | yes · partial · no · unknown · not applicable | | Evidence classes | documented, vendor-attested, listed, tested, reported, inferred, not-found | | Formats | HTML for people; Markdown twins, JSON API, OpenAPI, llms.txt, and an agent skill for machines. | | Affiliation | None. Independent publication; product names and marks belong to their owners. | | Price | Free to read. No account, no tracking wall. | ## Name and usage Use: - “Can My Agent Use” — the product name, title case, no question mark. - “canmyagentuse.com” — the domain and compact signature. - “Can my agent use this?” — the lookup sentence, question mark included. - “Independent compatibility catalog” — the category description. Avoid: - A question mark on the product name. - Invented abbreviations such as “CMAU”. - Describing the catalog as certified, approved, partnered, or vendor-affiliated. - Citing catalog coverage as usage share, market share, or a product quality score. - Superlatives the corpus cannot prove, such as “the best agent” or “fully compatible”. ## Brand assets The mark is the **evidence aperture**: four ledger corners framing one copper compatibility cell. | Asset | Format | Size | Note | | --- | --- | --- | --- | | [Evidence aperture mark](https://canmyagentuse.com/brand-mark.svg) | SVG | 64 × 64 | Four paper ledger corners framing one copper compatibility cell on chrome. The primary mark. | | [Compact mark](https://canmyagentuse.com/favicon.svg) | SVG | 64 × 64 | The same geometry tuned for small sizes. | | [Directory logo](https://canmyagentuse.com/brand-mark-512.png) | PNG | 512 × 512 | The mark rendered for directory listings, app tiles, and profile avatars. | | [Social card](https://canmyagentuse.com/og-card.png) | PNG | 1200 × 630 | The default Open Graph and Twitter card. | | [Social card source](https://canmyagentuse.com/og-card.svg) | SVG | 1200 × 630 | Editable source for the social card. | Allowed: - Use the mark and name to identify or link to canmyagentuse.com in articles, talks, videos, and directories. - Place the mark on chrome (#12100e) or paper (#fff8eb) with clear space around it. - Scale the mark proportionally. Not allowed: - Recoloring, distorting, outlining, or adding effects to the mark. - Combining the mark or name with another product identity, or implying affiliation or endorsement. - Using the mark as another product’s app icon or favicon. - Placing provider logos inside the Can My Agent Use identity. ## Color and type Copper marks the catalog’s own question. Green, amber, brick, and neutral gray are reserved for support statuses — do not use them as decoration. | Color | Hex | Role | | --- | --- | --- | | Chrome | `#12100e` | Night-ledger site chrome | | Chrome ink | `#f3eadc` | Text on chrome | | Copper | `#c45c26` | The catalog’s query accent | | Deep copper | `#8f431c` | Query belt | | Paper | `#fff8eb` | Record surfaces | | Canvas | `#efe6d4` | Page ground | | Ink | `#1a1714` | Body text | | Yes | `#215e48` | Supported | | Partial | `#9a6418` | Supported with limits | | No | `#8a3324` | Explicitly unsupported | | Unknown | `#6d675e` | No reviewed evidence | Typefaces: IBM Plex Sans (400 / 500 / 600) — Headings and body copy; IBM Plex Mono (400 / 500) — Labels, paths, and evidence annotations. Both typefaces are self-hosted and published under the SIL Open Font License. ## Milestones - 2026-08-28 — [Catalog foundation is up](/news/catalog-foundation.md): Lookup, product columns, and Markdown and JSON copies are live. - 2026-08-28 — [Evidence Atlas v1 is ready](/news/evidence-atlas-v1.md): The first reviewed capabilities, evidence records, and machine-readable catalog files are published. - 2026-08-28 — [Web, desktop, and CLI columns](/news/harness-columns.md): Major chat, desktop, and CLI products are listed as exact catalog columns. - 2026-08-28 — [Unknown is the published default](/news/unsourced-cells.md): Coverage percentages count sourced cells, not claimed support. ## Contact There is no press inbox yet. Open a public issue on the open-data repository for coverage questions, or use the correction route for a catalog record. - [Open data on GitHub](https://github.com/reachjalil/canmyagentuse-data) - [Open data on Hugging Face](https://huggingface.co/datasets/reachjalil/canmyagentuse) - [Catalog correction route](/report.md) Independent compatibility research. Product names and marks belong to their respective owners. Provider marks used inside the catalog are documented on the [brand references](/provider-marks.md) page.