REST API

Every key is a bearer token (t2f_...). API access requires an active or trial subscription — the anonymous/free demo quota doesn't apply here.

Create a job

curl -X POST https://text2folder.com/api/v1/jobs \
  -H "Authorization: Bearer t2f_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"image_base64": "<base64 screenshot>"}'

Check status / download

curl https://text2folder.com/api/v1/jobs/JOB_ID \
  -H "Authorization: Bearer t2f_your_key_here"

Finalize reviewed lines

curl -X POST https://text2folder.com/api/v1/jobs/JOB_ID/finalize \
  -H "Authorization: Bearer t2f_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"lines": ["Project Alpha", "Project Beta"]}'

Finalization uses saved paid naming rules automatically, then applies mandatory safety sanitization. Append ?download=1 once the job's status is ready to stream the ZIP directly.

MCP server

The MCP worker forwards your API key to the same REST endpoints, so agents in Cursor and other MCP clients get the identical job pipeline as tool calls. Point your client at the worker's /mcp endpoint:

{
  "mcpServers": {
    "text2folders": {
      "url": "https://mcp.text2folder.com/mcp",
      "headers": {
        "Authorization": "Bearer t2f_your_key_here"
      }
    }
  }
}

• create_job

  Upload a base64 screenshot and start OCR.

• get_job

  Check status, OCR'd lines, and download readiness for a job.

• finalize_job

  Build the ZIP from reviewed lines, applying paid naming rules before sanitization.

• list_jobs

  List recent jobs for the authenticated account.

Note: MCP authenticates with the same API keys as the REST API. Hosted MCP OAuth is not supported; create a key in /app to call the tools.