The catalog holds 1940 unique tools. 1380 are Premium. 560 are Kyauta. Those two Lambobi are the Pro Raba. They are not the execution Raba. Machine status on the same 1940 is 1491 describe_only, 439 supported, and 10 requires_worker. Docs at https://swarme.io/developers state that describe_only blocks quote and run. A Pro badge does not lift that block.

Pro is a commercial Alama

Read access_level on GET /api/capabilities/{slug}. Observed values are Kyauta and Premium. This post uses Pro as the public name for Premium. Do not invent a third access level.

Cross-tab from the catalog dump:

access_leveldescribe_onlysupportedrequires_workerKyauta (560)2473085Premium (1380)12441315

Most Pro tools are still describe_only (1244 of 1380). Most of the supported set is Kyauta (308 of 439). If your client filters access_level=Premium and then quotes, you are aiming at 131 supported Pro tools, not 1380 executable jobs.

Execution mode is a third axis:

access_levelclient_browserserver_syncasync_workerexternal_aiasync_worker_external_aiKyauta2472258800Premium1097111221491

Catalog totals: client_browser 1344, server_sync 336, external_ai 149, async_worker 110, async_worker_external_ai 1. Pro is concentrated in client_browser (1097) and external_ai (149). Those modes often describe as describe_only. Do not treat Pro as server_sync.

How zuwa count without stopping at 500

GET /api/capabilities?limit=500 returns at most 500 rows. That cap is not the catalog Girma and not the Pro count. Walk category slugs and union by kayan aiki slug. Observed API slugs include web-seo, security-network, and ai-tools. Homepage labels are not the query value.

Category counts that sum zuwa 1940:

  • Amfani 254
  • Kasuwanci 226
  • Mai haɓakawa 189
  • security-network 134
  • Takarda 129
  • web-seo 123
  • Hoto 116
  • ai-tools 112
  • PDF 109
  • ai-write 97
  • Rubutu 97
  • Bidiyo 97
  • Fayil 92
  • Sauti 89
  • QR 76

After the union you should have 1940 unique slugs. Sitemap unique kayan aiki slugs also land on 1940. Then Raba access_level. Stopping at the first 500 will not give you 1380 Pro tools.

Ƙirƙira the key at https://swarme.io/dashboard?tab=developers. https://swarme.io/dashboard/developers returns 404. Prefix sk_sw_QdE8 only; do not print a full key. Scopes capabilities:read, capabilities:quote, and capabilities:run do not change access_level.

Pro does not mean quote will succeed

Describe smoke on mixed Pro and Kyauta slugs all returned HTTP 200. Machine status matched the catalog. Examples:

  • anchor-text-analyzer — Premium, supported, server_sync
  • app-store-qr-code — Premium, supported, server_sync
  • bates-numbering-pdf — Premium, supported, async_worker
  • 3-2-1-backup-planning-tool — Premium, describe_only, client_browser
  • aac-converter — Kyauta, describe_only, client_browser
  • accessibility-statement-generator — Kyauta, supported, server_sync

A Pro describe_only slug still describes. It still refuses quote/run. A Kyauta supported slug still quotes. API QA later attempted quote+run on 435 tools: 272 passed, 163 failed, 1505 skipped (1491 skipped_browser_only). Those counts are not a Pro audit. They are a machine-status audit.

A completed uuid-generator run (Kyauta, supported) returned UUID 4cd3c7b6-0495-447a-8efd-9a1374f7599c at $0.00 included after a 900-second quote lock. Wallet on that account was $0.00 with billing_mode metered_observe. Dashboard Lifetime is not Pro-catalog math and not API credit.

Observed 422 bodies after a successful quote (Use labeled address lines in key: value Fom or provide JSON., Enter valid Base64URL input.) are Filin rules. They are not "this kayan aiki is not Pro."

MCP does not publish 1380 Pro kayan aiki

POST https://swarme.io/mcp initialize (protocolVersion 2025-03-26) identified Swarme Capability MCP Alpha 2026.07.15-wallet-alpha. tools/list returned 22 tools. Bincike through swarme_capabilities_Bincike still returns catalog slugs, including Pro ones. MCP does not flatten 1380 Premium capabilities into 1380 MCP tools.

Unauthenticated quote is HTTP 419 (Your secure request token expired.). Unauthenticated balance is HTTP 401. The login toast Your secure Fom token expired. Please go back and try again. is a Fom token. None of those codes is a Pro count.

Fayil path is still not Pro

pdf-zuwa-word is Kyauta, client_browser, describe_only, server_receives_Fayil_bytes false. pdf-editor is Premium, client_browser, describe_only, server_receives_Fayil_bytes false. merge-pdf and compress-pdf are Kyauta, async_worker, supported, server_receives_Fayil_bytes true. Pro did not decide where bytes go. Review how zuwa choose a secure kan layi Fayil kayan aiki before an Loda.

Checklist

  1. Union the catalog zuwa 1940 slugs. Do not stop at limit=500.
  2. Count access_level: 560 Kyauta, 1380 Premium.
  3. Count machine_run_status separately: 1491 describe_only, 439 supported, 10 requires_worker.
  4. Do not quote a Pro describe_only slug.
  5. Surface both labels zuwa the caller before spend.

For matching a request zuwa one executable slug after you know it is Pro or Kyauta, see AI kayan aiki routing.