What authentication does the Checkvist API use?

Checkvist uses an API token passed in the X-Client-Token header. You obtain a token by POSTing your username and Remote API key to /auth/login.json, and you refresh it by POSTing the previous value as old_token to /auth/refresh_token.json; a token is valid for one day and can be refreshed within 90 days. Checkvist's own documentation also accepts HTTP Basic authentication (username with password, or username with the Remote API key from your profile page) and the same token as a token query parameter. Through Jentic, both credentials and the resulting token live in your Jentic One instance and are injected at execution time.

Is there a Checkvist MCP server?

You don't need an MCP server to give your agent Checkvist. Jentic connects it directly from the API Directory: import Checkvist, store your token once, and your agent can create checklists, nest tasks, and post comments, with no extra tool definitions loaded into its context.

Can I create nested tasks with the Checkvist API?

Yes. POST /checklists/{id}/tasks.json accepts task[parent_id], the id of an existing task, so you can place a new task under any task to build a hierarchy. The call returns the created task including its id, which you can pass as task[parent_id] on the next call to nest further.

How do I bulk import tasks into Checkvist via the API?

Use POST /checklists/{id}/import.json and put the items in import_content as indented plain text, one item per line with indentation for nesting, the same format Checkvist's own import function takes. The call creates the whole branch at once and returns the created list items, so their ids come back in one response.

What are the rate limits for the Checkvist API?

Checkvist does not document a rate limit, and neither its own OpenAPI file nor the spec behind this page declares one, so treat throttling as undefined rather than absent. The timing constraint that is documented is the token: it lasts one day and can be refreshed within 90 days, so refresh it proactively in long-running scripts.

How do I create a Checkvist task through Jentic?

Install Jentic One on its own machine, then run `jentic register` on the machine your agent runs on and import the Checkvist API from the API Directory, storing your credentials once. Your agent then searches by intent, loads the schema for /checklists/{id}/tasks.json, and executes it with the checklist id and task content while Jentic handles login, token refresh, and X-Client-Token injection.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Checkvist operations and credentials the agent may use. Checkvist puts the checklist id in the URL path, such as /checklists/{id}/tasks.json, so you can pin the agent to a single checklist where it may add tasks and post comments and nothing else. You also choose the exact operations it can call, so bulk import via /checklists/{id}/import.json stays off limits unless you explicitly allow it.