Can AI agents automate Contractbook?

Contractbook is automatable today through its public REST API. This record is Contractbook contract management: documents, templates, spaces, and automations on the Contractbook API. Scrive, DocuSign, PandaDoc, and Oneflow are separate products. Public API v3 is HTTPS JSON at https://api.contractbook.com/v3/ (staging is https://api-staging.contractbook.com/v3/). Create an API key in profile settings and send it as an Authorization bearer token. Documented operations list and update documents, download a PDF, send for signature, share, create documents from templates, upload attachments, list templates, run automations, and manage spaces. Coverage is partial because the AI contract assistant and the in-browser editor are outside this API, and the docs say to redirect the user into the editor when editing is required. Webhooks notify on document lifecycle events and are unauthenticated; the docs say to confirm state with an authenticated GET. Contractbook publishes a local stdio MCP server, npm @contractbook/mcp, which needs CONTRACTBOOK_API_KEY. Its tools list and search documents, read document text, list and get templates, and create a draft from a template. That draft is not sent for signature. Connector catalogs were not opened. https://contractbook.com/llms.txt is a short marketing link list, not an API guide. Computer-use viability is unassessed. The API scores 7 and is the best path. MCP scores 6 because the official server is maintained and useful for reading and drafting, and it does not send contracts.

Best path today: api · Overall automatability: 7/10