Integration

Autentique integration

Autentique is a Brazilian electronic signature platform. Track documents and every signer's status, add, remove or re-notify signers, edit a document's settings or deadline, sign as the key's owner, delete or transfer documents, and organize them in folders you can share. Left out: creating documents (it needs a GraphQL file upload the platform cannot send), signing links (createLinkToSignature and the link of signers added by name), folder link sharing with a password, approving or rejecting biometric identity checks (their answer carries ID photos), and webhooks (set up in the dashboard). Document reads are billed per document, signature requests per channel. Authentication is an API key from the Autentique dashboard (profile, API), sent as a Bearer token; rate limit 10 requests per minute on Free, 60 on Professional, 200 on Corporate.

Connect Autentique How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Autentique.Built from the 21 Autentique tools below, on the connection you add once.

What you can do with Autentique

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Document, 7 operations

delete_documentDelete documentPOSTAgents: ask firstDeletes a document. If anyone already signed it, it only moves to your trash and stays signable: set deadline_at with update_document to block it. Returns true on success.
get_documentGet documentPOSTAgents: ask firstReturns one document with its file links and every signer's status (viewed, signed, rejected, biometric checks, email delivery). Personal data. Billed $0.0002 per call; prefer webhooks to frequent polling.
list_documentsList documentsPOSTAgents: ask firstLists documents page by page with each signer's status (viewed, signed, rejected) and file links. Personal data. Autentique bills $0.0002 per document returned, so keep limit small.
move_document_to_folderMove document to folderPOSTAgents: ask firstMoves a document into a folder. A document already in a folder needs current_folder_id too. Returns true on success.
sign_documentSign documentPOSTAgents: ask firstSigns a document with the legally binding electronic signature of the API key's owner, who must be one of its signers. Cannot be undone. Never use it to sign for anyone else. Returns true on success.
transfer_documentTransfer documentPOSTAgents: ask firstMoves a document to another organization and group of the account (it leaves its current place). Returns true on success.
update_documentUpdate documentPOSTAgents: ask firstChanges an existing document's settings: name, email message, reminders, refusal and ordering rules, footer, deadline, email template and notifications. Only the fields in document change.

Folder, 5 operations

create_folderCreate folderPOSTAgents: ask firstCreates a folder in the API key owner's account, at the root or inside a parent folder (at most five subfolders per folder). Returns the folder.
delete_folderDelete folderPOSTAgents: ask firstDeletes a folder. Documents in it are not deleted: they become unfiled and show in the default directory. Returns true on success.
get_folderGet folderPOSTAgents: ask firstReturns one folder: name, path, context, parent and subfolders, whether it is password protected and who it is shared with (user names and emails are personal data).
list_foldersList foldersPOSTAgents: ask firstLists folders page by page: id, name, path, context, subfolder count and subfolders, whether you may edit it. Optional search by name and sort order.
rename_folderRename folderPOSTAgents: ask firstRenames a folder. Returns the folder with its new name and path.

Organization, 2 operations

get_current_organizationGet current organizationPOSTAgents: ask firstReturns the organization the API key currently works in: id (the organization_id other tools take), UUID, name and CNPJ.
list_organizationsList organizationsPOSTAgents: ask firstLists every organization of the account that owns the API key, with id, UUID, name and CNPJ.

Signer, 2 operations

add_signerAdd signerPOSTAgents: ask firstAdds a signer to an existing document; Autentique sends the signature request to the email or phone given (WhatsApp or SMS). Billed: $0.002 by email, $0.02 WhatsApp, $0.03 SMS; extra verifications cost credits.
remove_signerRemove signerPOSTAgents: ask firstRemoves a signer from a document. Returns true on success.

Email template, 1 operation

list_email_templatesList email templatesPOSTAgents: ask firstLists the email templates of the account page by page: id (the email_template_id update_document takes), name, type and the email text, sender and colors.

Folder document, 1 operation

list_folder_documentsList folder documentsPOSTAgents: ask firstLists the documents in one folder, page by page: id, name, qualified-signature flag, sandbox flag, creation and deletion time. Autentique bills $0.0002 per document returned.

Folder share, 1 operation

share_folderShare folderPOSTAgents: ask firstShares a folder and its documents with users (by email address) or groups as VIEWER or EDITOR; email_message, when given, is the text of the email sent with the share. Returns the folder's shares.

Signature, 1 operation

resend_signaturesResend signaturesPOSTAgents: ask firstSends the signature requests of the given signers again (Autentique does not charge for resends). Signers resent too recently are skipped; if all were, it fails with too_many_resent_emails.

User, 1 operation

get_current_userGet current userPOSTAgents: ask firstReturns the account that owns the API key: id, name, email, phone (personal data), plan details (premium features, document and credit balance) and its current organization.

Use Autentique from Claude Code, Cursor or Codex

Connect Autentique in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Autentique operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Autentique

Create your workspace
Sign up free. Nothing to install.
Connect Autentique once
Add your Autentique connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.