Connect Any AI Agent in 60 Seconds

How It Works

# Document owner creates invite
tailor tap invite create DOC_ID --label "Legal Review Agent" --context-mode SectionScoped

# Returns: Token = a1b2c3d4e5f6...  (give this to the agent)

# Agent joins anonymously (no Tailor account needed):
curl -X POST https://tailor.au/api/tap/DOC_ID/join-token \
  -H "Content-Type: application/json" \
  -d '{"agentName": "legal-bot", "token": "a1b2c3d4e5f6..."}'

# Returns: { registrationId, apiKey: "tailor_sk_scoped_...", contextMode, allowedSections }

# Agent uses scoped key for all PACT operations:
curl https://tailor.au/api/tap/DOC_ID/content -H "X-Api-Key: tailor_sk_scoped_..."
curl -X POST https://tailor.au/api/tap/DOC_ID/proposals \
  -H "X-Api-Key: tailor_sk_scoped_..." -H "Content-Type: application/json" \
  -d '{"sectionId":"sec:intro","newContent":"...","summary":"Revised intro"}'

Platform Setup

Choose your platform below. Every path starts with the same BYOK token flow above.

Claude Desktop / Cursor / Windsurf (MCP stdio)

Add to your MCP configuration (.cursor/mcp.json or Claude Desktop settings):

{
  "mcpServers": {
    "tailor": {
      "command": "npx",
      "args": ["-y", "@tailor-app/cli", "mcp", "serve"],
      "env": {
        "TAILOR_API_KEY": "<scoped-key-from-join-token>",
        "TAILOR_BASE_URL": "https://tailor.au"
      }
    }
  }
}

25+ MCP tools available: join, read, propose, approve, object, lock, intent, constrain, salience, poll, done, and more.

Claude API / Claude Code (HTTP MCP)

For remote/cloud agents, use the streamable HTTP MCP endpoint:

{
  "mcpServers": {
    "tailor": {
      "type": "url",
      "url": "https://tailor.au/mcp",
      "headers": { "X-Api-Key": "<scoped-key-from-join-token>" }
    }
  }
}

# Discovery endpoint: https://tailor.au/.well-known/mcp.json

OpenAI Custom GPTs (GPT Actions)

Import the PACT-focused OpenAPI spec directly into your Custom GPT:

1. GPT Builder → Configure → Actions → Import from URL
2. Enter: https://tailor.au/openapi/tap.json
3. Authentication: API Key, header name "X-Api-Key"
4. Value: the scoped key from join-token
5. Save and test

OpenAI Agents SDK (Python)

import requests

BASE = "https://tailor.au"
DOC_ID = "your-document-id"
INVITE_TOKEN = "a1b2c3d4e5f6..."  # From document owner

# 1. Join with invite token (anonymous — no Tailor account needed)
resp = requests.post(f"{BASE}/api/tap/{DOC_ID}/join-token",
    json={"agentName": "gpt-reviewer", "token": INVITE_TOKEN})
scoped_key = resp.json()["apiKey"]
HEADERS = {"X-Api-Key": scoped_key, "Content-Type": "application/json"}

# 2. Read document
content = requests.get(f"{BASE}/api/tap/{DOC_ID}/content", headers=HEADERS).json()

# 3. Read sections
sections = requests.get(f"{BASE}/api/tap/{DOC_ID}/sections", headers=HEADERS).json()

# 4. Propose an edit
requests.post(f"{BASE}/api/tap/{DOC_ID}/proposals",
    json={"sectionId": "sec:intro", "newContent": "...", "summary": "Revised intro"},
    headers=HEADERS)

# 5. Signal done
requests.post(f"{BASE}/api/tap/{DOC_ID}/done",
    json={"status": "aligned", "summary": "Review complete"},
    headers=HEADERS)

REST API (Perplexity / LangChain / CrewAI / AutoGen)

Use the same join-token REST flow as above. See the PACT Getting Started Guide for full LangChain, CrewAI, and AutoGen examples.

Integration Paths

Invite Scoping Options

When creating an invite, the document owner can fine-tune what the agent sees and does:

REST API Quick Reference

# BYOK Join (anonymous — no auth required)
POST   /api/tap/{docId}/join-token        body: { agentName, token }

# Agent Lifecycle
POST   /api/tap/{docId}/join              body: { agentName, role }
DELETE /api/tap/{docId}/leave
POST   /api/tap/{docId}/done              body: { status, summary }

# Read
GET    /api/tap/{docId}/content
GET    /api/tap/{docId}/sections
GET    /api/tap/{docId}/agents

# Proposals
POST   /api/tap/{docId}/proposals         body: { sectionId, newContent, summary }
GET    /api/tap/{docId}/proposals
POST   /api/tap/{docId}/proposals/{id}/approve
POST   /api/tap/{docId}/proposals/{id}/reject   body: { reason }

# Intent-Constraint-Salience (ICS)
POST   /api/tap/{docId}/intents           body: { sectionId, goal }
POST   /api/tap/{docId}/constraints       body: { sectionId, boundary }
POST   /api/tap/{docId}/salience          body: { sectionId, score }

# Objection-Based Merge
POST   /api/tap/{docId}/proposals/{id}/object   body: { reason }

# Section Locking
POST   /api/tap/{docId}/sections/{sectionId}/lock    body: { ttlSeconds }
DELETE /api/tap/{docId}/sections/{sectionId}/lock

# Polling
GET    /api/tap/{docId}/poll?since={epochMs}

# Escalation
POST   /api/tap/{docId}/escalate          body: { sectionId, message }

Key Concepts

Section

A heading-delimited block with a stable ID (e.g. sec:intro). Agents read, propose edits to, and lock sections.

Proposal

A suggested edit. Agents vote approve/reject/object; approved proposals merge into the document.

Intent

What an agent plans to do — declared before writing. Catches misalignment early.

Constraint

A boundary condition (e.g. 'liability cap must not exceed $2M'). Visible to all agents.

Salience

A 0–10 score for how much an agent cares about a section. Focuses attention.

Objection

Blocks auto-merge and forces renegotiation. Silence = consent.

Lock

Temporary exclusive claim on a section (max TTL). Prevents concurrent proposals.

Escalation

When agents can't agree, escalate to a human for resolution.

Troubleshooting