Install Jentic One Beta

Connect the Trello to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Trello, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftrello.com%2Ftrello" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftrello.com%2Ftrello" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Trello API.

Create a card in a list with a name, description, due date, and label assignments in a single call

Move a card between lists or reorder it within a list to advance it through a kanban workflow

Add, complete, and reorder checklist items on a card to track subtasks

Assign or remove board members and labels on a card

Read a board's or card's activity feed to see comments, moves, and updates over time

GET STARTED

Start building with Trello API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Trello API for, with concrete tasks.

★ AI Agent Card Triage and Routing

AI agents use the Trello API through Jentic to triage incoming work - reading new cards, analyzing their content, then moving them to the right list, applying labels, and assigning members. An agent searches Jentic for 'create a trello card', receives the schema for POST /cards, and can list existing cards to avoid duplicates before creating. The whole triage flow from intake to assignment runs in seconds.

List cards in the 'Inbox' list, read each card's name and description, then move it to the appropriate list and apply a label based on its content

Kanban Workflow Automation

Automate moving cards through a board's lists as work progresses, keeping the kanban board in sync with external systems. The API exposes lists, card positions, and card fields so agents can advance cards, set due dates, and update checklists without manual dragging. Useful for pipelines that move a card to 'Done' when a deployment or approval completes.

Find cards in the 'In Progress' list whose checklist is fully complete, then move each to the 'Done' list and add a comment noting completion

Board Reporting and Activity Analysis

Read a board's activity feed and card data to generate reports on throughput, stale cards, and recent changes. The API returns actions (comments, moves, updates) per board and card, so agents can aggregate activity, flag cards untouched for days, and summarize what moved during a period.

Read the recent actions on a board, identify cards with no activity in the last 7 days, and post a summary comment listing the stale cards

AI Agent Integration via Jentic

AI agents discover and call Trello endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle the API key and token manually.

Search Jentic for 'create a trello card', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

324 endpoints — manage trello boards, lists, cards, checklists, and members programmatically across 324 rest endpoints.

METHOD

PATH

DESCRIPTION

POST

/cards

Create a card

GET

/cards/{idCard}

Get a card by id

PUT

/cards/{idCard}/idList

Move a card to another list

GET

/lists/{idList}/cards

List the cards in a list

GET

/boards/{idBoard}/lists/{filter}

Get the lists on a board

POST

/cards/{idCard}/actions/comments

Add a comment to a card

POST

/cards/{idCard}/checklists

Add a checklist to a card

GET

/boards/{idBoard}/actions

Read the activity feed for a board

POST

/cards

Create a card

GET

/cards/{idCard}

Get a card by id

PUT

/cards/{idCard}/idList

Move a card to another list

GET

/lists/{idList}/cards

List the cards in a list

GET

/boards/{idBoard}/lists/{filter}

Get the lists on a board

POST

/cards/{idCard}/actions/comments

Add a comment to a card

POST

/cards/{idCard}/checklists

Add a checklist to a card

GET

/boards/{idBoard}/actions

Read the activity feed for a board

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Trello API by hand means passing both its key and token query parameters on every call to trello.com/1 and handling error responses yourself. Through Jentic you install once, import Trello from the API Directory, store the key and token once, and your agent calls it.

Permission scoping

Trello puts the card id in the URL path (/cards/{idCard}), so a rule can pin your agent to one card: it can read that card and add comments and nothing else. You choose the operations it may call, so moving, editing, or archiving a card is not included unless you add it.

Credential isolation

Your Trello key and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a trello card' or 'move a card to another list', and Jentic returns the matching Trello operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Trello API through Jentic.

What authentication does the Trello API use?

Trello uses an API key plus a token, both passed as query parameters (`key` and `token`) on every request. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

How do I create a card through the Trello API via Jentic?

Search Jentic for 'create a trello card', load the operation schema for POST /cards, and execute with the target list id, a name, and any optional fields like a description or due date. Jentic injects the API key and token automatically. The response returns the new card's id and URL.

What are the rate limits for the Trello API?

Trello enforces rate limits per API key (roughly 300 requests per 10 seconds) and per token (roughly 100 requests per 10 seconds). The API returns 429 Too Many Requests when limits are exceeded. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

Can I move cards between lists via the Trello API?

Yes. Use PUT /cards/{idCard}/idList with the destination list's id in the `value` field (or PUT /cards/{idCard} with `idList`, and optionally `pos`, to move and reposition in one call). This is how agents advance cards through a kanban workflow, for example from 'In Progress' to 'Done'.

How many endpoints does the Trello API have?

The Trello API exposes 324 endpoints covering boards, lists, cards, checklists, members, and activity actions.

Can I limit what my agent is allowed to do with the Trello API?

Yes. Because you run Jentic One yourself and your own rules decide which operations and credentials the agent may use, you pick exactly which Trello calls it can make. Trello puts the card id in the URL path (/cards/{idCard}), so a rule can pin the agent to one card, letting it read that card and add comments and nothing else. Since you choose the operations, moving, editing, or archiving a card is not available to the agent unless you add it.

Trello

Name: Trello API
Brand: Trello
Availability: InStock

Developer ToolsProject ManagementapiKey324 EndpointsREST

For Agents

Automate Trello kanban boards: create cards, move them between lists, manage checklists, due dates, labels, and members, and read board and card activity. Covers 324 endpoints spanning boards, lists, cards, checklists, members, and actions.

Use for: I need to create a card in the 'To Do' list with a due date, I want to move a card from 'In Progress' to 'Done', Search for all cards on a board assigned to a specific member, List all cards in a given list

Not supported: Does not handle payments, communications, or CRM - use for kanban boards, cards, and project tracking only.

Manage Trello boards, lists, cards, checklists, and members programmatically across 324 REST endpoints. Create and move cards through lists, add checklists and due dates, assign members and labels, and read the activity feed for a board or card. Authenticated with an API key and token passed as query parameters, so agents can automate kanban workflows without a browser.

Jentic One on Github View OpenAPI Document

Connect the Trello to your agent

Capabilities

Start building with Trello API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Trello