Clavocial
Developers

Put your product
inside the keyboard.

Reach users everywhere they type. Build a plugin that hooks into Clavocial with the user's consent — social flows, AI assistants, dictionaries, education, games, security, shopping. Sandboxed, verified, and running on your infra or the user's device — never ours.

Submit a plugin → Read the spec
Built on four guarantees

Standards your users can trust.

Safe

Your plugin runs in a sandboxed iframe — strict CSP, its own origin, no access to what the user types unless they grant it, per invocation.

Crash-free

The native typing path never waits on a plugin. Isolation, load + call timeouts, and resource caps mean one plugin can't take down the keyboard.

Secure

Verified publisher domains, HTTPS-only, least-privilege permissions with explicit in-keyboard consent, and an AI malware scan before listing.

Purposeful

Declare a category and typed entry points. Users pick you from a grid of icons — intentional, never ambient background code.

The manifest

One JSON file describes your plugin.

Identifiable, tunable entry points. Declare only the permissions you need.

{
  "pluginId": "com.acme.assistant",
  "name": "Acme Assistant",
  "category": "ai-assistant",
  "description": "Answer questions from any text field.",
  "icon": "https://acme.com/icon.svg",
  "publisher": { "name": "Acme", "domain": "acme.com" },
  "entryPoints": [
    { "type": "assistant", "label": "Ask Acme",
      "url": "https://acme.com/kb-plugin" }
  ],
  "permissions": ["read-selection", "insert-text"],
  "compute": "thirdparty"
}

Entry points

grid-action

An icon in the plugin grid that opens your sandboxed panel.

compose-addon

Hook into the social composer — your platform's own posting flow.

text-transform

Receive selected text, return a replacement (translate, define, rewrite).

assistant

A query box — AI assistants, shopping, security lookups, and more.

Permissions — default none, granted in-keyboard

read-selectioninsert-textread-clipboardnetworkcameramicstorageidentity

Nothing is ambient. A permission applies only while the user has your plugin open, after explicit consent. Compute runs on the user's device (sandbox) or your backend — declare which with compute.

Prove it's really you

Verify your official domain.

This is how a user knows your plugin is the real Facebook, the real LinkedIn — not an impersonator.

  1. Start: request a token for your domain (acme.com).
  2. Publish: host it at https://acme.com/.well-known/clavocial-verification.txt (or a DNS TXT record).
  3. Check: we fetch it over HTTPS and bind the domain to you. Only you can publish plugins under it.
Reviewed before it ships

Every plugin is AI-scanned for malware.

On submission we fetch your entry-point source and scan it for keylogging, exfiltration, obfuscation, cryptomining, and permission abuse. A plugin is listed only on a clean verdict — unscanned never means live. It's fail-closed by design.

Start your submission →