canonical: https://jentic.com/apis/routine.co/routine

# Routine API

Routine productivity and task management API. The API exposes 17 endpoints secured with bearer authentication.

## For AI agents

Programmatically create task, list tasks. Covers 17 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create task
- List tasks
- Get task
- Update task
- Delete task

## Use cases

### E-Commerce Operations

Use the Routine API to perform e commerce operations programmatically. The API provides 17 endpoints covering core functionality including create task, list tasks, get task.

Example prompt: Call POST /tasks to create task

### Automated Calendar Management

Automate calendar operations by combining multiple Routine API endpoints. Agents can list tasks and then get task in a single workflow.

Example prompt: Call GET /tasks to list tasks, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Routine API 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 bearer tokens manually.

Example prompt: Search Jentic for 'create task', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tasks` | Create task |
| GET | `/tasks` | List tasks |
| GET | `/tasks/{taskId}` | Get task |
| PUT | `/tasks/{taskId}` | Update task |
| DELETE | `/tasks/{taskId}` | Delete task |
| POST | `/projects` | Create project |
| GET | `/projects` | List projects |
| GET | `/projects/{projectId}` | Get project |

## Key resources

- **Calendar** — Operations for calendar
- **Notes** — Operations for notes
- **Projects** — Operations for projects
- **Tasks** — Operations for tasks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 60 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 46 / 100
- **View full report:** https://jentic.com/apis/routine.co/routine/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Routine by hand means setting up its bearer token against api.routine.co/v1 and writing your own pagination across tasks and projects. Through Jentic you install once, import Routine from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Routine puts the task and project ids in the URL path (`/tasks/{taskId}`, `/projects/{projectId}`), so a rule can pin your agent to one project: it can read and update items there and nothing else. You choose the operations it may call, so task deletion is not included unless you add it.
- **Credential handling:** Your Routine bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a task' or 'list projects', and Jentic returns the matching Routine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Routine API use?

The Routine API uses a Bearer token in the Authorization header. 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.

### Can I create task with the Routine API?

Yes. Use the POST /tasks endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Routine API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create task through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create task'. Jentic returns the matching Routine API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Routine API have?

The Routine API exposes 17 endpoints covering calendar, notes, projects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Routine operations and credentials your agent can use. Routine puts task and project ids in the URL path (`/tasks/{taskId}`, `/projects/{projectId}`), so you can pin the agent to a single project and let it read and update items there and nothing else. You also pick the operations it may call, so DELETE `/tasks/{taskId}` stays out of reach unless you add it.