How to Choose a Secure Online File Tool Before You Upload
Seven practical questions for evaluating file processing, retention, providers, access controls, and output handling before submitting sensitive material.
Read articleSwarme resources
Guidance for
practical workflows.
Product updates and operational guidance for documents, media, data, development, accessibility, security, and AI-assisted work.
AI Tool Routing: From a Plain-Language Request to a Reliable Workflow
A practical model for turning an outcome such as “extract these pages and translate them” into a reviewable sequence of tool operations.
Read articleHow to Prepare a PDF for Accurate OCR, Extraction, and Automation
Improve OCR and document extraction by checking page quality, orientation, text layers, structure, and validation requirements before processing.
Read articleLifetime on Swarme Does Not Fund the API Wallet
Dashboard Lifetime is not a funded API wallet. The observed account was signed in as Admin, plan Lifetime, member since Jul 2026, with 4 payments on the dashboard. GET /api/account/balance still returned $0.00 credits. billing_mode was metered_observe. wallet_policy was observe. spend_limit_minor was 0.
Read articleHow to Read Swarme API 422 Errors
HTTP 422 on a Swarme run is usually a field rule, not an auth failure and not a broken quote. Four observed bodies, each after a successful quote on a supported tool, are enough to read the pattern.
Read articleHow to Create a Swarme API Key
A Swarme API key is created in the dashboard, not by guessing a REST path. The URL that works is https://swarme.io/dashboard?tab=developers. https://swarme.io/dashboard/developers returns 404. Bookmark the tab query. Do not document the 404 path as the developers portal.
Read articleHow to Fix Swarme's Expired Login Form Token
The toast on Swarme's login form is a CSRF failure, not a catalog outage. The exact copy is Your secure form token expired. Please go back and try again. That sentence is the product's instruction. Follow it. Do not treat it as a 422 field rule, a describe_only block, or a missing tool.
Read articleHow to List All Swarme Tools When the API Stops at 500
GET /api/capabilities?limit=500 does not mean the catalog has 500 tools. It means one response will not return more than 500. The catalog currently holds 1940 unique tools. An unfiltered call with limit=500 returns 500.
Read articleWhy Most Swarme Tools Will Not Run From an API Key
Most of the Swarme catalog is visible to an API key and still refuses to execute. That is not an auth bug. It is execution.machine_run_status.
Read articleHow to List Swarme MCP Tools
An MCP client that skips initialize and tools/list will guess the wrong surface. Swarme's catalog has 1940 tools. The MCP server does not expose 1940 MCP tools. It exposes a small, named set that searches, describes, quotes, and runs capabilities through the same contract as REST.
Read articleWhy Swarme Quotes a Tool Before It Will Run
The quote step is not a receipt written after work finishes. It is a lock on price, input, and permission that must exist before Swarme will accept run. That rule held on a completed uuid-generator call priced $0.00 included. The lock lasted 900 seconds. Run still required quote_id.
Read articleHow to Generate a UUID With Swarme's API
A UUID is a small output, but Swarme's API treats it as a full capability run. You describe the slug, lock a quote, then run. Skipping a step is not a shortcut. It is a rejected request.
Read article