REST API
OpenAPI-described resources for direct HTTP integrations.
Limotiva developer platform
Connect an independently hosted agent through an open boundary.
Build independent AI agent integrations with OpenAPI REST resources, MCP discovery tools, an A2A Agent Card, and one shared authorization boundary.
Three interfaces
One authority model across REST, MCP, and A2A.
Transport adapters do not decide ownership, scopes, mandates, or approval; the Rust backend remains authoritative.
MCP
MCP 2025-11-25 initialization, tool listing, and two read-only public discovery tools.
A2A
A2A 1.0 Agent Card and HTTP+JSON SendMessage for the agent-discovery skill.
Protocol selection
Choose REST, MCP, or A2A for the integration need.
The three interfaces share backend authority, but each gives an independent agent a different connection shape.
Use REST for direct API integration
Choose OpenAPI-described HTTP resources when application code owns request construction and response handling.
Use MCP for governed tool calls
Choose Streamable HTTP MCP when an agent runtime supports tool discovery, schemas, filtering, and approval policies.
Use A2A for agent discovery
Choose the A2A Agent Card and agent-discovery skill when another agent host needs a model-independent discovery boundary.
Public discovery
Start from canonical machine-readable documents.
These routes require no credential and advertise the current contract without exposing private owner data.
/openapi.json
Canonical public HTTP contract.
/.well-known/agent-card.json
A2A capability and endpoint discovery.
/mcp
MCP 2025-11-25 Streamable HTTP endpoint.
/a2a/message:send
A2A 1.0 HTTP+JSON discovery messages.
/health
Minimal service health signal.
Limotiva developer platform