Every template in the catalog carries a **level** badge, which sums up how much we've reviewed it before offering it to you and how you connect to it. The list is shown in alphabetical order by name, not grouped by level; those that can't yet be connected appear in their place with the "Coming soon" badge: | Level | Badge | How you connect | What it means | | --- | --- | --- | --- | | **A** | "Official · Key" | You paste an API key from the provider itself. | Official provider server, verified by the Platform, no extra steps. | | **B** | "Official · OAuth" | You authorize access from the provider's own sign-in page (section 6). | Official provider server; the connection is made with your session, without copying any key by hand. | | **C** | "Community · Not verified by us" | Can't be connected directly from here yet (the card marks it with the "Coming soon" badge). | Server maintained by the community, not by the official provider — more risk, review it yourself before trusting it. | > **Note — Real catalog figures, verified on September 4, 2026** > > Today there are **more than 20 level-A templates** and **more than 110 level-B** ones directly > connectable from your account, plus the first **2 level-C** ones — the catalog grows with every > review, so the screen always shows you the real, up-to-date figure for your account, never a fixed > number from this manual. Every card also says whether the server is **verified** ("Verified on {date}") or, in the rare case we don't yet have any check on file, "Not verified" — before connecting any template, review its info sheet (section 4). > **Warning — Level C: community server, at your own judgment** > > "Community server: not maintained by the official provider. Review its code and reputation before > trusting it with your data." — the card's real text. While level C doesn't yet have a guided connection > button ("You can't connect it directly from here yet"), if you genuinely want to use that particular > server, the route is to bring your own server (section 1, Manual 26 section 8) with its URL and your > own credential — under your own responsibility, same as any Custom server.