# Runrun.it > Runrun.it is a work management platform for organizing, executing, and tracking team requests, with tasks, projects, boards, automations, and AI agents. This file is an expanded version, published by convention alongside `/llms.txt`. It brings together essential public context for agents and AI clients in a single document. The `llms.txt` specification recommends keeping the main file concise and linking to detailed documentation; therefore, linked documentation remains the source of truth for details that change frequently. ## Identity and scope Runrun.it helps teams centralize operational work in a single environment. The product combines request organization, task execution, collaboration, deadline tracking, automations, reports, and integrations. The main public website is in Brazilian Portuguese. Public versions are also available in United States English, United Kingdom English, and Spanish. The Help Center provides product usage documentation, and the API documentation describes programmatic integrations. - [Homepage in Portuguese](https://runrun.it/pt-BR) - [Homepage in United States English](https://runrun.it/en-US) - [Homepage in United Kingdom English](https://runrun.it/en-GB) - [Homepage in Spanish](https://runrun.it/es-419) ## Product features ### Work organization - **Boards and Kanban:** represent processes through stages and make it possible to track request flow. - **Task list:** makes it possible to view, create, and track tasks and subtasks. - **Projects and clients:** organize work by initiative and business context. - **Task types:** standardize request categories and can be used with fields and permissions. - **Custom fields:** add information specific to each team's process. - **Tags, filters, and prioritization:** help locate and organize work. - **Calendar and deadlines:** support planning of start and delivery dates. - **Requirements, dependencies, and subtasks:** represent relationships between deliverables and execution conditions. ### Execution and collaboration - **Workflows:** define stages and rules for task execution. - **Automations:** perform actions based on configured events and conditions. - **Forms:** collect structured requests before they are created or enter a workflow. - **Comments, mentions, and email:** centralize communication and feedback related to work. - **Attachments and documents:** keep files associated with tasks and projects. - **Approvals:** make it possible to request, approve, reject, or track task reviews. - **External users:** make it possible to share selected projects and tasks with people outside the account. ### Management and analysis - **Dashboards:** display operational metrics in real time. - **Reports:** make it possible to analyze hours, costs, capacity, allocation, and other indicators. - **Time tracking:** tracks time worked on tasks and projects. - **Alerts:** help identify delays and inactivity. - **AI agents:** automate operational actions in the workflow, according to configuration, permissions, and plan availability. The commercial feature list is available at [Features](https://use.runrun.it/funcionalidades/). ## Main concepts - **Company or account:** space that brings together users, teams, boards, projects, settings, and permissions. - **User:** person who accesses the account and can participate in teams, receive tasks, and perform permitted actions. - **Team:** group of users that shares context and work. - **Board:** workflow composed of stages. - **Board stage:** state or stage through which a task passes during execution. - **Task:** unit of work that can have an assignee, participants, dates, points, tags, comments, documents, and custom fields. - **Subtask:** task related to a main task to divide a deliverable. - **Project:** grouping of tasks and information for an initiative. - **Client:** organizational context to which projects can be associated. - **Task type:** reusable classification for standardizing requests. - **Workflow:** set of stages and elements that guides task execution. - **AI agent:** configuration that uses an AI model to perform authorized actions in a workflow. Names, available fields, and effective permissions depend on the account configuration, plan, and user profile. ## Public API The Runrun.it public API uses JSON and is available at the base path `https://runrun.it/api/v1.0`. The complete and up-to-date reference is available in the [API documentation](https://runrun.it/api/documentation). ### Authentication API requests use the `App-Key` and `User-Token` headers: ```shell curl "https://runrun.it/api/v1.0/users" -X GET \ -H "App-Key: " \ -H "User-Token: " ``` Never replace the placeholders above with real keys in public documentation, prompts, source code, or logs. The keys identify the account and user; treat them as secret credentials. Keys can be accessed in Runrun.it under **Integration and Apps > API and Webhooks**, when the account's plan and permissions allow the feature. ### Format and dates - API responses are JSON. - Requests should use JSON; for several actions, form-encoded data is also accepted. - Dates use the ISO 8601 format. - Date special characters, such as `+` in time zones, must be encoded in the URL when they are part of parameters. - An invalid credential results in `401 Unauthorized`. ### Rate limit The documented limit is 100 requests per minute. When the limit is reached, the API may return `429` and the following headers: - `RateLimit-Limit`: limit for the window. - `RateLimit-Remaining`: amount remaining in the window. - `RateLimit-Reset`: time when the limit will be restored. Respect the limit and implement retries with backoff. Excessive use may lead to revocation of the application key. ### Pagination Collections use pagination to limit the volume of data returned. The main parameters are: - `page`: page number, starting at 1. - `limit`: number of items per page; the documented default and maximum are 100. - `offset`: starting position of the items. The relevant response headers are: - `X-Item-Range`: range of returned items, in the format `items {first}-{last}/{total}`. - `Link`: hypermedia links with `self`, `prev`, `next`, and `last` relations, when applicable. - `X-Item-Without-View-Permission`: optional number of items not visible due to missing permission. Prefer following the `rel="next"` link in the response until it is no longer returned, rather than assuming the total number of pages. ### API resources The public documentation presents endpoints for the following groups, among others: - AI models and activities; - companies, users, teams, and partners; - boards, board stages, workflows, and workflow elements; - tasks, subtasks, assignments, followers, evaluations, requirements, and descendants; - task types, fields, and field values; - projects, project groups, subgroups, templates, and extra costs; - clients, tags, filters, and comments; - checklists and checklist items; - documents, descriptions, and document contents; - notifications, vacations, time off, and manual work periods; - reports and time worked. See the specific endpoint in the [API documentation](https://runrun.it/api/documentation), because HTTP methods, parameters, permissions, and response formats vary by resource. ### Webhooks Webhooks can be managed on the **API and Webhooks** page. A webhook sends an HTTP `POST` request to the configured URL when an event occurs. Documented events include changes to tasks, assignments, projects, clients, teams, comments, documents, and evaluations. Task events include `task:create`, `task:update`, `task:destroy`, `task:deliver`, `task:reopen`, `task:move`, `task:mark_as_urgent`, and `task:unmark_as_urgent`. Webhook payloads include the event, the time it occurred, the actor when applicable, and the resource data. Validate the origin and content received by the consuming system, handle duplicates idempotently, and consult the documentation for the exact format of each event. ## MCP integration Runrun.it provides an MCP endpoint for compatible and authorized clients: - [MCP endpoint](https://runrun.it/mcp) - [Protected resource metadata](https://runrun.it/.well-known/oauth-protected-resource/mcp) - [Authorization server metadata](https://runrun.it/.well-known/oauth-authorization-server) - Dynamic client registration: `https://runrun.it/mcp/oauth/register` OAuth discovery provides the authorization endpoint, token endpoint, dynamic client registration, and `S256` PKCE challenge method. Clients should follow the metadata published by the server, use HTTPS, and request only the permissions they need. MCP access is subject to authentication, user permissions, company configuration, and integration availability. The endpoint must not be treated as an anonymous API or as authorization to access data from any account. ## Help Center and public content - [Help Center in Portuguese](https://help.runrun.it/pt-BR/collections/17374028-portugues): articles about forms, automations, custom fields, boards, users, calendars, reports, tasks, projects, mobile, dashboards, and other features. - [Features](https://use.runrun.it/funcionalidades/): commercial description of the features. - [Use cases](https://use.runrun.it/na-pratica/): examples of product applications. - [Templates](https://templates.runrun.it/): work templates. - [Plans and pricing](https://runrun.it/pt-BR/planos-e-precos): commercial information. - [Blog](https://blog.runrun.it): editorial content. ## Security and privacy The Runrun.it website states the following public practices and commitments: - data stored in Brazil; - end-to-end SSL encryption; - MFA for infrastructure access; - scalable cloud infrastructure; - automatic daily backups; - LGPD compliance; - restricted data access; - firewall, WAF, and self-healing mechanisms; - customer data not used to train AI. For complete legal terms, see the [Terms of use](https://runrun.it/pt-BR/gerenciador-de-tarefas-termos-de-uso), [Privacy policy](https://runrun.it/pt-BR/privacidade), and [DPA](https://runrun.it/pt-BR/dpa). This section is an informational summary and does not replace the legal documents. ## Support and contact - Sales: `comercial@runrun.it`. - Support: `help@runrun.it`. - [Help Center](https://help.runrun.it/pt-BR/collections/17374028-portugues). ## Guidance for agents - Use the [API documentation](https://runrun.it/api/documentation) to confirm endpoints, parameters, permissions, and responses before generating an integration. - Use the [Help Center](https://help.runrun.it/pt-BR/collections/17374028-portugues) for product interface instructions and procedures. - Do not invent data about companies, users, tasks, projects, or permissions; this data belongs to accounts and requires authentication. - Do not request, reproduce, or record `App-Key`, `User-Token`, OAuth tokens, or other secrets. - Do not treat public marketing content as a guarantee that a feature is enabled for every account; confirm the plan, configuration, and permissions. - For MCP, follow the OAuth metadata published by the server and respect the granted permissions. - When this summary conflicts with the linked official documentation, prefer the more specific and recent source.