Integrate AI Agents with Siglata
Siglata exposes standard Model Context Protocol (MCP) Streamable HTTP endpoints, OAuth 2.0 PKCE authentication, and typed spreadsheet operations designed for automated agents and developer tools.
Standard Endpoints
POST /mcp
Streamable HTTP endpoint conforming to Model Context Protocol (MCP) specification. Handles tool dispatch for context, search, and execute.
GET /openapi.json
Full OpenAPI 3.1.0 machine-readable schema covering all endpoints, parameters, request bodies, and typed JSON responses.
GET /.well-known/oauth-authorization-server
RFC 8414 Authorization Server Metadata declaring PKCE (S256), token exchange endpoints, JWKS verification URI, and granted scopes.
GET /schema/spreadsheet/1
Versioned canonical schema specification for Siglata spreadsheet workbook representations and relational tables.
Quickstart: Call MCP via cURL
curl -X POST https://www.siglata.com/v1/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $SIGLATA_TOKEN" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "context",
"arguments": {}
}
}'Rate Limits
All API endpoints enforce fair-use rate limiting of 120 requests per minute per client IP or authorized token. Every response emits standard RFC headers:
RateLimit-Limit: 120RateLimit-Remaining: 119RateLimit-Reset: 60RateLimit-Policy: 120;w=60
Versioning Policy
All breaking changes are path-versioned (e.g. /schema/spreadsheet/1). Deprecated endpoints provide a minimum 6-month deprecation grace period announced via HTTP Sunset headers before removal.
Structured Error Model
All client and authentication errors return machine-parseable JSON error payloads with actionable resolution hints:
{
"error": {
"code": "invalid_request",
"message": "Missing required parameter 'params' in JSON-RPC body.",
"resolution": "Check the OpenAPI specification at https://www.siglata.com/openapi.json."
}
}