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`	Creates a workflow ticket for your organization.	`workflowId`, `title`, `dataContextJson`
`get_ticket_status`	Returns the status of a workflow ticket.	`ticketId`
`list_workflows`	Lists the workflow definitions available to your organization.	—
`execute_ticket`	Runs or retries a workflow ticket immediately.	`ticketId`
`resume_ticket`	Resumes a ticket that is waiting for a manual decision.	`ticketId`, `decision`

Exposed MCP Resources

Resource URI	Description
`abipilot://workflows/templates`	Workflow templates available to your organization.
`abipilot://tickets/{tenantId}/active`	Active workflow tickets of your organization.
`abipilot://agents/status`	Current status of your AI agents.

Request Example (JSON-RPC 2.0)

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "create_workflow_ticket",
    "arguments": {
      "workflowId": 105,
      "title": "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 set the spending limit, cart mandates lock the exact line items and settlement receipts record the executed payment. Every link of the chain is signed and verified before settlement.

Ed25519 Mandate Delegation

Every mandate is signed with Ed25519 over its canonical payload, so any change to the amount, merchant or signer breaks the signature.

Spend Velocity Guardrails

Protects funds with an hourly transaction cap and a daily spending cap per organization, plus a budget check before every settlement.

Human-in-the-Loop Thresholds

Carts above the approval threshold (1,000 USD by default) wait for human approval before they can be settled.

Audit trail: Signed mandates and settlement receipts are recorded in the audit log, an evidence trail you can map to SOC 2 controls.

Feature Availability by Plan

Protocol	Free Trial	Esencial	Crecimiento	Negocio
MCP (JSON-RPC)
A2A (Google spec)
AP2 (Ed25519 payments)

Upgrade your subscription to Crecimiento (MCP) or Negocio (MCP, A2A and AP2) to unlock agent communication protocols.

Getting Started

Check eligibility

Verify plan eligibility (Crecimiento or Negocio required).

Protocols included in your plan

There is nothing to switch on: protocol access comes with your plan. Crecimiento includes MCP; Negocio includes MCP, A2A and AP2. Calls to /mcp and /a2a are authenticated with your AbiPilot user session.

Discover the Agent Card

Download the Agent Card configuration (/.well-known/agent.json) to discover the available skills.

Establish the connection

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

Monitor operations

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

Ready to Connect?

Connect your AI clients, IDEs and partner agents to AbiPilot through MCP, A2A and AP2.