Agent Interoperability

Protocol Integration Hub

AbiPilot natively supports open standards for multi-agent interoperability, external tools discovery, and secure cryptographic transactions.

Model Context Protocol (MCP)

Model Context Protocol (MCP) allows external AI clients and development tools to query and execute workflow actions, view ticket resources, and check system status over a secure, streamable JSON-RPC 2.0 interface.

Endpoint (POST): POST /mcp

Exposed MCP Tools

Tool Name	Description	Parameters
`create_workflow_ticket`	Tool Create Ticket Description	`workflowId`, `title`, `dataContextJson`
`get_ticket_status`	Tool Get Status Description	`ticketId`
`list_workflows`	Tool List Workflows Description	—
`execute_ticket`	Tool Execute Ticket Description	`ticketId`
`resume_ticket`	Tool Resume Ticket Description	`ticketId`, `decision`

Exposed MCP Resources

Resource Uri	Description
`abipilot://workflows/templates`	Res Templates Description
`abipilot://tickets/{tenantId}/active`	Res Active Tickets Description
`abipilot://agents/status`	Res Agents Status Description

Request Example (JSON-RPC 2.0)

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "create_workflow_ticket",
    "arguments": {
      "workflowId": 105,
      "title": "API Lead Enrichment",
      "dataContextJson": "{\"lead_email\":\"partner@abipilot.com\"}"
    }
  },
  "id": 1
}

Agent-to-Agent Protocol (A2A)

Based on Google's A2A specification, this layer exposes our bots' capabilities and coordinates multi-turn cross-platform delegations via public Agent Cards and secure endpoints.

Agent Card Discovery: GET /.well-known/agent.json

Inbound Endpoint (POST): POST /a2a

Task Delegation Lifecycle

1. Discovery — External agent reads Agent Card capabilities JSON
2. Handshake & Delegation — External agent calls POST /a2a with task directive POST
3. Execution — Workflow instantiates ticket, executes action stages Working
4. HITL Check (Optional) — Pauses for human input if verification fails Pending
5. Resolution — Postback webhook delivers result back to delegating agent Completed

Agent Card Discovery Example

{
  "agent_id": "abipilot_core",
  "name": "AbiPilot Bot Workforce",
  "description": "Specialized AI agents for enterprise operations",
  "skills": [
    {
      "id": "translate-document",
      "description": "Translate documents between EN, ES, and PT",
      "input_schema": {
        "type": "object",
        "properties": {
          "file_url": { "type": "string" },
          "target_lang": { "type": "string" }
        }
      }
    }
  ]
}

Agent Payments Protocol (AP2)

An open framework for autonomous financial transactions. AI agents request, delegate, and settle payments through cryptographically signed mandates (Ed25519) within pre-approved spending guards.

Cryptographic Mandate Chain

Intent Mandates authorize spending limits; Cart Mandates lock specific line items; Settlement Receipts prove cryptographic execution.

Ed25519 Mandate Delegation

Mandate Encryption Description

Spend Velocity Guardrails

Protects funds with strict spending velocity caps (hourly, daily, monthly limits) and automatic freeze policies.

Human-in-the-Loop Thresholds

Automatically triggers Human-in-the-Loop review if the transaction exceeds the threshold (e.g. $1,000).

Soc2 Compliance: Cryptographic signatures produce immutable audit trails mapping to SOC2 Trust Services Criteria (Common Criteria 6.6 / Process Integrity 1.1).

Feature Availability by Plan

Protocol	Free Trial	Starter	Professional	Enterprise	Partner
MCP (JSON-RPC)
A2A (Google Spec)
AP2 (Ed25519 Payments)

Upgrade your subscription to Professional or Enterprise to unlock agent communication protocols.

Getting Started

Step1 Check Eligibility

Verify plan eligibility (Professional or Enterprise required).

Step2 Enable Protocols

Enable MCP, A2A, or AP2 protocols in your Tenant Dashboard under Settings.

Step3 Keys Discover

Retrieve your API Access keys and download the well-known Agent Card configuration.

Step4 Establish Connection

Connect external IDEs, AI clients, or external partner agents to the exposed endpoints.

Step5 Operational Monitoring

Monitor tool calls, A2A collaboration tasks, and cryptographic settlements in real-time.

Ready to Connect?

Api Integration Description