Control SignedBy from a prompt.

Console access itself is free on every plan, Free included — no monthly console fee, no card required to start sealing Verified Badge documents by chat.

Sending documents and using templates from the console is priced separately from the rest of SignedBy's flat-fee plans, because it's usage that scales with an agent or automation rather than a person, and needs the Pro plan or higher:

• 100 document-sends free every month via console, on any plan — Pro, Team, or Business.
• $0.20 per documentsent beyond that, billed monthly alongside your subscription — console is metered on every plan, including Business. This is separate from Business's existing unlimited, included access to the plain API (see /developers), which is unaffected.

Reads (listing/checking documents) and webhook deliveries are never metered — only creating and sending a document counts. Verified Badge sealing has its own separate free-tier limit, not this metering — see /verified-badge. Exact pricing is still being finalized; this page will be updated before any charge is ever billed.

SignedBy runs a real MCP server at /api/mcp — six tools show up ready to call: send a document, check status, list documents and templates, void, and download the signed PDF. No wrapper code, no manifest to ingest first.

Mistral Le Chat

• Connectors → + Add Connector → the "Custom MCP Connector" tab
• Name it (e.g. signedby) and paste the server URL: https://signedby.ai/api/mcp
• Le Chat detects it needs an HTTP Bearer Token and prompts for one — paste your SignedBy API key

Claude Code / Claude Desktop

Add this to your MCP config:

{
  "mcpServers": {
    "signedby": {
      "url": "https://signedby.ai/api/mcp",
      "headers": { "Authorization": "Bearer sb_live_..." }
    }
  }
}

Generate the key in Settings → Integration & API — the same key the REST API uses, requires the Pro plan or higher.

Not using an MCP client? A machine-readable tool manifest for OpenAI-style function calling or a custom agent framework also lives at /console/tools.json.

curl https://signedby.ai/console/tools.json

Under the hood, the MCP server and the manifest both call the same REST endpoints documented in full at /developers — neither is a different API. Any integration built against the REST API directly works exactly the same way.