Akiflow vs TickTick for AI agents
As of 15 Oct 2026, TickTick gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
L1 · Needs a person describes Akiflow today: nothing gets an agent past the front door on its own. Registration answers with a hidden reCAPTCHA puzzle and the signup button hangs on Signing up..., so our agent stopped there first. The emailed login code worked, but with no account the official MCP server only answers 401 Unauthorized - No JWT provided, and no work was reached. There is no API key route, no free plan, and the trial needs a card at checkout, which the stuck registration never let our agent see.
Driven 15 Oct 2026 · The drive and its evidence- Find: Some docs for agents: An MCP server.
- Access: Sign-up in a browser.
- Use: 57% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 57% of the work done. Next: do 80% of the core work (now 57%)
L3 · Does the work: our agent gets in on its own, signing up through the web form, making a personal API key in Settings, and calling the project endpoint without hitting a CAPTCHA or needing a human. No checkpoint stopped it. Through the documented REST API and the official MCP server, it created a task and read it back, reaching lists, tags, reminders, repeats, comments, Kanban, focus records and habit check-ins. Premium is a card-only Stripe Checkout page, not tried on this drive, and deleting the account needs the web app, a password and confirmation steps.
Gets furtherDriven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
AkiflowStopped at sign up: needs a human
TickTickIn on its own; 57% of the work done
| Checkpoint | Akiflow | TickTick |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | In a browser |
| Verify | In a browser | Headless |
| Key | Not reached | In a browser |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | In a browser |
| Cancel | Not reached | Not needed |
| Delete | Not reached | In a browser |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Akiflow | TickTick | |
|---|---|---|
| Headless (checkpoints) | 1 | 4 |
| In a browser (checkpoints) | 1 | 4 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 6 | 0 |
| Work done | Not measured | 57% of the core |
| API | No | Yes |
| OpenAPI | No | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | No |
| SDK | No | No |
| llms.txt | Yes | No |
Bot checks, and where a person was needed.
| Akiflow | TickTick | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 (invisible) stopped it at sign up, without a visible challenge | None met |
| Wall type | A check of our network and browser | No bot-check wall |
| First wall | reCAPTCHA image puzzle on registration | None |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| Akiflow | TickTick | |
|---|---|---|
| Level | L1 · Needs a person | L3 · Does the work |
| Agent-ready setup | 65 of 100, fair | 45 of 100, poor |
| Standards | MCP client registration (behind) | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) |
| Security | No review in this drive | Reported privately to the owner |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Akiflow | TickTick | |
|---|---|---|
| Pay | Payment not reached | Reaches the checkout |
| Free plan or trial | Trial with a card | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | In a browser |
How each one takes payment
- Akiflow: Payment not reached.
- TickTick: Reaches the checkout: stopped at the card form.
Akiflow vs TickTick: the short answers.
Which can an AI agent use, Akiflow or TickTick?
TickTick gets an AI agent further: L3 · Does the work against L1 · Needs a person. With Akiflow our agent was stopped at sign up (needs a human); with TickTick it got in on its own and did 57% of the work. Driven 15 Oct 2026 (Akiflow) and 6 Oct 2026 (TickTick).
Can an AI agent sign up for Akiflow and TickTick on its own?
Akiflow: no, needs a human. TickTick: yes, in a browser.
Do Akiflow and TickTick have an MCP server?
Akiflow: yes (official). TickTick: yes (official).
Can an AI agent delete its Akiflow or TickTick account?
Akiflow: not reached. TickTick: yes, in a browser.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.