Skip to main content
Tools are invoked as JSON-RPC methods against POST /api/mcp. See MCP transport for the request and response envelopes.

​
Available now

​
ping

Liveness and auth check. Proves your API key is accepted and the dispatcher is reachable. Takes no parameters.
​
params
object
Ignored.
Result 
{ "pong": true }
Example 
curl -X POST https://api-atlaswork.vercel.app/api/mcp \
  -H "Authorization: Bearer $ATLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "ping", "params": {} }'

​
The signing tool set

The full tool suite turns the signing lifecycle into a small, deliberate set of agent tools. Each is review-first by default and idempotent — see Idempotency.
These tools are being built out. The list below is the committed surface so you can design integrations against it; call ping today to confirm connectivity and auth. Each tool’s parameters will be documented here as it lands.
ToolWhat it does
send contract for reviewCreate an envelope from a document and parties in one call; returns a review URL for a human to approve.
send from templateSend a known-good template by mapping recipients to roles and supplying prefill values. May auto-send, since the layout is trusted.
check signing statusReport where an envelope stands (“Alice hasn’t signed yet; her link was opened yesterday”).
get envelopeFetch a single envelope’s full detail.
list envelopesBrowse envelopes for the account.
list templates / get templateDiscover and inspect available templates and their roles.
remind signerRe-send the current participant’s signing email (rate-limited).
void envelopeCancel an envelope before completion.
extract contract dataPull the completed contract’s structured terms (parties, dates, amounts, renewal, governing law).

​
Document inputs

The send contract for review tool accepts a document several ways, depending on what the agent’s host supports:
  • a public URL,
  • an attached file passed through,
  • inline drafted text, or
  • an upload session — Atlas returns a short-lived upload link, the user drops the file there, says “done,” and the agent completes the session.
Review-first is the contract of the agent surface: the agent prepares, a human clicks Send. Template-based repeat sends are the exception, because the layout is known-good and the intent is explicit.