Integration Evidence: Does this vendor officially document a named integration?

1. # Free, read-only: public Actor metadata (pricing, builds). Does not start a run.
   curl "https://api.apify.com/v2/acts/VNySEt559gcOuwjE9"

2. # Paid run in YOUR Apify account. Only after spending is authorized.
   # Set APIFY_TOKEN securely in your client/shell; never paste it into URLs or shared files.
   curl -X POST "https://api.apify.com/v2/acts/VNySEt559gcOuwjE9/runs?build=0.2.4&memory=512&timeout=60&maxTotalChargeUsd=0.02&waitForFinish=30" \
     -H "Authorization: Bearer $APIFY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"company_website":"https://linear.app/","integration_name":"GitHub"}'

   Limits are query parameters: build 0.2.4, memory 512 MB, timeout 60 s, maxTotalChargeUsd=0.02.

3. # Save data.id (run ID) from the first response. On timeout/ambiguity, poll THIS run.
   # Never start a second charged run to recover output.
   curl "https://api.apify.com/v2/actor-runs/$RUN_ID" \
     -H "Authorization: Bearer $APIFY_TOKEN"

4. # data.defaultDatasetId from the run object (one report item).
   curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?format=json&clean=true" \
     -H "Authorization: Bearer $APIFY_TOKEN"

   # Alternative: data.defaultKeyValueStoreId → OUTPUT record.
   curl "https://api.apify.com/v2/key-value-stores/$KV_STORE_ID/records/OUTPUT" \
     -H "Authorization: Bearer $APIFY_TOKEN"

Recovery: Save the run ID from the first response; on timeout or ambiguous response, poll that same run; never start a second charged run to recover output.

Hosted MCP server https://mcp.apify.com. Anonymous (no token) inspection is allowed only when ?tools= is limited to search-actors, fetch-actor-details, search-apify-docs and fetch-apify-docs.

No live MCP execution of these call-actor templates has been performed by anyone, owner or independent; they were validated offline against the tool schemas and current metadata, and the recorded examples came from Apify SDK/API runs.

1. {
     "name": "fetch-actor-details",
     "arguments": {
       "actor": "impressionable_lupine/verified-integration-evidence",
       "output": {
         "pricing": true,
         "inputSchema": true,
         "outputSchema": true,
         "metadata": true,
         "readme": true
       }
     }
   }

   Client config for anonymous inspection

   Client config for anonymous inspection

   {
     "mcpServers": {
       "apify-inspect": {
         "url": "https://mcp.apify.com?tools=search-actors,fetch-actor-details"
       }
     }
   }

2. {
     "name": "call-actor",
     "arguments": {
       "actor": "impressionable_lupine/verified-integration-evidence",
       "input": {
         "company_website": "https://linear.app/",
         "integration_name": "GitHub"
       },
       "waitSecs": 30,
       "callOptions": {
         "build": "0.2.4",
         "memory": 512,
         "timeout": 60,
         "maxTotalChargeUsd": 0.02
       }
     }
   }

   Client config for execution (your own authentication)

   Client config for execution (your own authentication)

   {
     "mcpServers": {
       "apify": {
         "url": "https://mcp.apify.com?tools=actors,runs,storage"
       }
     }
   }

   {
     "mcpServers": {
       "apify": {
         "url": "https://mcp.apify.com?tools=actors,runs,storage",
         "headers": {
           "Authorization": "Bearer <APIFY_TOKEN>"
         }
       }
     }
   }

3. {
     "name": "get-actor-run",
     "arguments": {
       "runId": "<runId returned by call-actor>"
     }
   }

4. {
     "name": "get-dataset-items",
     "arguments": {
       "datasetId": "<datasetId returned by call-actor>",
       "clean": true
     }
   }

   {
     "name": "get-key-value-store-record",
     "arguments": {
       "keyValueStoreId": "<keyValueStoreId returned by call-actor>",
       "recordKey": "OUTPUT"
     }
   }

Recovery: Save the run ID from the first response; on timeout or ambiguous response, poll that same run; never start a second charged run to recover output. call-actor returns the run status and storage IDs (the IDs are under storages in call-actor’s structured result), not the items.