TaskFolk Ships a Checkout for Agents

TaskFolk is a project management platform — issues, sprints, releases, portfolios, forms, automations. The kind of product that has existed for twenty years and usually arrives in the catalog as a REST API and a docs page.

This one arrives with four interfaces, and the fourth is the one worth stopping on.

The fourth one

The second specification TaskFolk publishes is called the Agent Commerce API. It has four operations. All four are POST. None of them do any project management at all:

POST /api/mpp/v1/credits/small     Buy the small AI credit pack (2,000 credits)
POST /api/mpp/v1/credits/medium    Buy the medium AI credit pack (5,500 credits)
POST /api/mpp/v1/credits/large     Buy the large AI credit pack (12,000 credits)
POST /api/mpp/v1/credits/custom    Buy a custom amount of AI credits (1 cent per credit)

That is a till. It is a machine-callable, priced, documented way for a consumer to top up its own balance — published as a contract, separately from the product API, at a stated unit price.

Most providers courting agents ship an MCP server and stop. The agent can then read, write, and do work right up until the credits run out, at which point a human has to open a browser, find the billing page, and click. The autonomy ends at the paywall.

TaskFolk put the paywall behind an endpoint. Whether or not that specific design wins, it is the first time the catalog has profiled a provider that treats paying as part of the API surface rather than as the thing the API surface stops at.

The agent card tells you which door to use

The card declares both interfaces explicitly rather than leaving an agent to guess:

mcp   -> https://taskfolk.ai/api/mcp/v1
rest  -> https://taskfolk.ai/api/v1

And six skills: manage-issues, manage-projects, manage-sprints, manage-releases, search, manage-members.

That is a small thing that matters. A provider serving both MCP and REST usually documents them in separate places and lets the reader work out which is canonical. Naming both in the discovery manifest, with the protocol attached, means an agent picks the right one without a human curating the choice first.

The MCP server refuses correctly

An anonymous tools/list against taskfolk.ai/api/mcp/v1 returns:

{"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Missing or invalid API key."}}

A well-formed JSON-RPC error, not an HTML login page. That is the difference between a server that is live and gated, and a URL that merely exists. The tool list is not readable without a key — so nothing is asserted here about which tools it exposes — but the endpoint is unambiguously speaking MCP.

What the REST surface actually covers

Thirty-one tags across 111 paths. The largest groups:

Agents as a first-class tag inside the product API — alongside Issues and Projects — is the same signal from a different angle. Agents are not a channel bolted onto the side here; they are a resource the platform manages.

Also worth noting: a 45KB llms.txt, a /developer section, and a full reference at /api/v1/reference. Every request in this profile was made twice, once with a default client user-agent and once identifying as a browser, and the bytes were identical. TaskFolk serves everyone the same thing — which, as we wrote last week, is not something to take for granted.

Why it is in the catalog

TaskFolk came in through the Add an API form and was published by the submission gate at confidence 92. The profile is built entirely from what is served on the live domain: two OpenAPI definitions, an agent card, an llms.txt, and a probed MCP endpoint. Nothing here is derived or modelled.

The full profile, with every artifact and the evidence behind it, is at apis.io/providers/taskfolk/.