Trello

Trello's REST API supports field filtering and pagination, but lacks explicit batching endpoints and response compaction features, requiring agents to make multiple requests for complex operations.

REST API with multiple community SDKs (Node.js, Python) and developer documentation provide solid programmatic access, but the absence of an official MCP server and GraphQL limits modern agent integration patterns.

API key authentication with OAuth2 support and scoped permissions enable autonomous agent authentication without human-in-the-loop, supporting both personal and app-level tokens.

Standard rate limits apply but response time metrics are unavailable; no evidence of ETags or conditional request support, and concurrent request handling is not documented, limiting agent throughput optimization.

Developer documentation and REST conventions are present but no OpenAPI spec found; the .well-known/agents.json file exists but robots.txt blocks agents, creating conflicting signals about API discoverability.

Trello maintains consistent API versioning and response schemas typical of mature REST APIs, but no explicit idempotency key support or status page evidence is present in the collected signals.

Scoped API tokens provide access control, but there is no evidence of sandbox/test mode, dry-run capabilities, or explicit undo/rollback operations for destructive actions that agents might perform.

Trello supports webhooks for real-time updates when board state changes, enabling agents to react to events rather than polling, though streaming/SSE is not documented.