{
  "data": {
    "a": {
      "slug": "pipedream",
      "name": "Pipedream API + MCP",
      "vendor": "Pipedream (Workday)",
      "vendorUrl": "https://pipedream.com",
      "kind": "http-api",
      "category": "workflow-automation",
      "summary": "Code-first workflows in Node.js, Python, Go and Bash, plus Connect, an API and SDK that runs 10,000+ prebuilt actions across 3,000+ apps on behalf of your own users with managed OAuth.",
      "url": "https://www.anchorterminal.com/tools/pipedream",
      "markdownUrl": "https://www.anchorterminal.com/tools/pipedream.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pipedream.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pipedream.json",
      "repo": "https://github.com/PipedreamHQ/pipedream",
      "license": "Pipedream Source Available License (components)",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.pipedream.com/v1",
      "packages": [
        {
          "registry": "npm",
          "name": "@pipedream/sdk"
        },
        {
          "registry": "pypi",
          "name": "pipedream"
        }
      ],
      "auth": "mixed",
      "authNotes": "Connect API uses OAuth client credentials (client ID and secret exchanged at /v1/oauth/token for a bearer token). End users connect their accounts through short-lived Connect tokens. The developer MCP server at https://remote.mcp.pipedream.net/v3 takes the bearer token plus `x-pd-project-id`, `x-pd-environment` and `x-pd-external-user-id` headers. The end-user server at https://mcp.pipedream.net/v2 signs in with OAuth.",
      "pricing": "freemium",
      "pricingNotes": "Billed in credits, one credit per 30 seconds of compute at 256 MB (more memory costs more). Tool calls through MCP, action runs, deployed trigger emissions and proxy requests cost credits, listing apps and tools doesn't. Free $0 with a daily credit limit and Connect in development only, no card. Startup $150 a month or $99 a month billed yearly, 10,000 credits a month, extra credits $0.012 each, production Connect with 100 end users included and $2 per extra end user. Business is custom, annual contract only (https://pipedream.com/pricing).",
      "priceSummary": "$150 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402 support in docs or pricing (checked 2026-09-30).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 11719,
        "npmWeekly": 587447,
        "pypiWeekly": 327799,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://pipedream.com/docs",
      "llmsTxt": "https://pipedream.com/docs/llms.txt",
      "openapi": "https://pipedream.com/docs/pipedream_openapi_swagger.json",
      "capabilities": [
        "automation.workflows",
        "automation.apps",
        "automation.embedded",
        "automation.code",
        "automation.webhooks",
        "automation.auth",
        "agent.tools"
      ],
      "tags": [
        "hosted",
        "freemium",
        "mcp",
        "llms-txt",
        "openapi",
        "typescript",
        "python",
        "webhooks",
        "enterprise"
      ],
      "lastRelease": "2026-09-02",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 65.5,
        "grade": "B",
        "agentReady": false,
        "rank": 255,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 73,
          "maintenance": 79,
          "payments": 40,
          "reliability": 65,
          "schema": 74,
          "security": 58,
          "transparency": 75
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.",
        "bestFor": "Best when an agent acts in many third-party apps on behalf of your own users and you don't want to run OAuth yourself.",
        "strengths": [
          "Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP",
          "Billed by compute time, one credit per 30 seconds at 256 MB, so a many-step run can cost one credit",
          "Every action declares `readOnlyHint`, `destructiveHint` and `openWorldHint`",
          "TypeScript, Python and Java SDKs, last released 2 September 2026",
          "SOC 2 Type 2, HIPAA BAA, and data location and subprocessors published"
        ],
        "weaknesses": [
          "Public changelog's last entry is 1 October 2025",
          "Production Connect starts at $150 a month ($99 billed yearly). Free is development only",
          "No published limit or 429 behaviour for action runs and tool calls",
          "No security.txt, no bug bounty and no prompt-injection guidance",
          "Cloud only, in AWS us-east-1"
        ],
        "agentNotes": [
          "Pass your own user ID as `x-pd-external-user-id` so each user's accounts stay separate",
          "Send `x-pd-app-slug` to load one app's tools rather than 10,000",
          "Use a Connect rate-limit token (`x-pd-rate-limit`) to cap runaway loops per user",
          "Check `isError` on tool results before treating a call as done",
          "Stay on `x-pd-environment: development` until billing is set, since production needs a paid plan"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 65.5
          }
        ],
        "editorialScores": {
          "ergonomics": 73,
          "maintenance": 79,
          "payments": 40,
          "reliability": 65,
          "schema": 74,
          "security": 58,
          "transparency": 65
        },
        "provenanceScore": 84
      },
      "connect": {
        "http": "curl -X POST https://api.pipedream.com/v1/oauth/token -H \"Content-Type: application/json\" \\\n  -d \"{\\\"grant_type\\\":\\\"client_credentials\\\",\\\"client_id\\\":\\\"$PIPEDREAM_CLIENT_ID\\\",\\\"client_secret\\\":\\\"$PIPEDREAM_CLIENT_SECRET\\\"}\"\ncurl \"https://api.pipedream.com/v1/connect/apps?q=slack\" -H \"Authorization: Bearer $PIPEDREAM_ACCESS_TOKEN\"",
        "claudeCode": "claude mcp add --transport http pipedream https://mcp.pipedream.net/v2",
        "config": {
          "mcpServers": {
            "pipedream": {
              "headers": {
                "Authorization": "Bearer ${PIPEDREAM_ACCESS_TOKEN}",
                "x-pd-app-slug": "slack",
                "x-pd-environment": "development",
                "x-pd-external-user-id": "${USER_ID}",
                "x-pd-project-id": "${PIPEDREAM_PROJECT_ID}"
              },
              "url": "https://remote.mcp.pipedream.net/v3"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/automation.workflows",
        "tool": "https://letme.dev/pipedream"
      },
      "alsoIn": [
        "agent-auth"
      ],
      "area": "business",
      "unitPrices": [
        {
          "item": "Startup plan",
          "unit": "month",
          "usd": 150,
          "note": "$99 a month billed yearly. 10,000 credits and production Connect with 100 end users"
        },
        {
          "item": "Extra credit",
          "unit": "credit",
          "usd": 0.012,
          "note": "one credit is 30 seconds of compute at 256 MB"
        },
        {
          "item": "Extra end user",
          "unit": "user-month",
          "usd": 2,
          "note": "beyond the 100 included on Startup"
        }
      ],
      "provenance": {
        "legalEntity": "Pipedream, LLC",
        "domain": "pipedream.com",
        "domainRegistered": "1998-06-01",
        "domainNote": "pipedream.com was registered in 1998, well before the company was founded.",
        "endpointOnVendorDomain": true,
        "terms": "https://pipedream.com/terms",
        "privacy": "https://pipedream.com/privacy",
        "statusPage": "https://status.pipedream.com",
        "changelog": "https://pipedream.com/docs/changelog",
        "securityTxt": "none",
        "checked": "2026-10-01",
        "notes": [
          "The terms, last updated 30 September 2026, name Pipedream, LLC, a Delaware limited liability company, and point Workday customers to Workday's early access scheme. Workday agreed to buy Pipedream in November 2025."
        ],
        "score": 84
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/pipedream.json",
      "live": {
        "slug": "pipedream",
        "probe": {
          "target": "https://api.pipedream.com/v1",
          "method": "get",
          "lastAt": "2026-10-08T22:39:55.584422284Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 378,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 343,
          "p95ms24h": 415,
          "samples24h": 269,
          "samples30d": 2172,
          "days": [
            {
              "date": "2026-09-30",
              "probes": 35,
              "ok": 35
            },
            {
              "date": "2026-10-01",
              "probes": 276,
              "ok": 276
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 254,
              "ok": 254
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.pipedream.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-08T22:39:37.054514897Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@pipedream/sdk",
            "version": "3.1.6",
            "seenAt": "2026-10-08T16:25:14.275510921Z"
          },
          {
            "registry": "pypi",
            "name": "pipedream",
            "version": "2.1.20",
            "released": "2026-09-02",
            "seenAt": "2026-10-08T16:25:15.083005628Z"
          }
        ],
        "githubStars": 11721,
        "npmWeekly": 508516,
        "pypiWeekly": 266870,
        "securityTxt": {
          "url": "https://pipedream.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:32.668195027Z"
        },
        "llmsTxt": {
          "url": "https://pipedream.com/docs/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:00:45.555132969Z"
        },
        "domain": {
          "domain": "pipedream.com",
          "registered": "1998-06-01",
          "source": "https://rdap.verisign.com/com/v1/domain/pipedream.com",
          "checkedAt": "2026-10-04T13:06:14.75079587Z"
        },
        "pages": [
          {
            "url": "https://pipedream.com/docs/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:22:54.097423317Z",
            "changedAt": "2026-10-02T15:22:54.204376413Z",
            "fingerprint": "85598021dd17"
          },
          {
            "url": "https://pipedream.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:22:56.610443095Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "d35da09334d8"
          },
          {
            "url": "https://pipedream.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:22:58.457950432Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "333facaf775d"
          },
          {
            "url": "https://pipedream.com/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:23:00.472196082Z",
            "changedAt": "2026-10-08T18:23:00.472196082Z",
            "fingerprint": "7ae8ebca8eb0"
          }
        ],
        "updatedAt": "2026-10-08T22:39:55.584422284Z"
      }
    },
    "answer": "Pipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories.",
    "b": {
      "slug": "power-automate",
      "name": "Microsoft Power Automate",
      "vendor": "Microsoft",
      "vendorUrl": "https://www.microsoft.com/power-platform/products/power-automate",
      "kind": "http-api",
      "category": "workflow-automation",
      "summary": "Microsoft's workflow builder for cloud flows across Microsoft 365, Dataverse and third-party connectors. Outside agents list, create, update and delete solution-aware flows through the Dataverse Web API, and start a flow through its HTTP request trigger.",
      "url": "https://www.anchorterminal.com/tools/power-automate",
      "markdownUrl": "https://www.anchorterminal.com/tools/power-automate.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/power-automate.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/power-automate.json",
      "license": "Proprietary service under the Microsoft Product Terms for Microsoft Power Platform",
      "transports": [
        "http"
      ],
      "packages": [
        {
          "registry": "nuget",
          "name": "Microsoft.PowerPlatform.Dataverse.Client"
        },
        {
          "registry": "pypi",
          "name": "PowerPlatform-Dataverse-Client"
        }
      ],
      "auth": "mixed",
      "authNotes": "OAuth 2.0 through Microsoft Entra ID for flow management. A person registers an app in the tenant and an administrator creates an application user with a Dataverse security role, or a user signs in with delegated access. The read-only Power Platform API takes a token for `https://api.powerplatform.com` with `.default`. A flow's HTTP request trigger has three modes. Any user in my tenant (the default for new flows) and Specific users in my tenant take an Entra bearer token with audience `https://service.flow.microsoft.com/`, and the second can name service principal object IDs. The legacy Anyone mode needs only the trigger URL, which carries a shared access signature as `sig=`. No API-key path for management.",
      "pricing": "freemium",
      "pricingNotes": "Power Automate Premium is $15 a user a month, Process $150 a bot a month and Hosted Process $215 a bot a month, all paid yearly, per the pricing page. API calls carry no separate charge and count against daily Power Platform request allowances (40,000 per Premium user, 250,000 per Process licence, a 25,000 tenant pool for unlicensed service principals). A flow owned by a service principal that uses premium connectors needs a Process licence or a designated licensed co-owner. To start without a contract there is a Free licence limited to standard connectors, a self-serve 90-day trial, and the Power Apps Developer Plan with a free Dataverse environment and 750 flow runs a month. Card requirements were not stated (checked 2026-10-08).",
      "priceSummary": "$15 / seat-mo",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the Power Automate code docs, the Power Platform API reference or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": 10702,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://learn.microsoft.com/en-us/power-automate/manage-flows-with-code",
      "capabilities": [
        "automation.workflows",
        "automation.apps",
        "automation.webhooks"
      ],
      "tags": [
        "hosted",
        "official",
        "oauth",
        "enterprise",
        "odata",
        "dotnet",
        "python",
        "closed-source",
        "sla",
        "audit-log",
        "freemium",
        "webhooks"
      ],
      "lastRelease": "2026-10-02",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62,
        "grade": "B",
        "agentReady": false,
        "rank": 350,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 2,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 69,
          "maintenance": 76,
          "payments": 25,
          "reliability": 63,
          "schema": 68,
          "security": 61,
          "transparency": 76
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.",
        "bestFor": "Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.",
        "strengths": [
          "Solution-aware cloud flows are rows in the Dataverse `workflows` table, with documented list, create, update, delete, share, export and import calls",
          "Service protection limits are published (6,000 requests per user in five minutes) and 429 responses carry `Retry-After`",
          "The SLA of 1 October 2026 pays a 25 per cent credit below 99.9 per cent uptime for Power Automate",
          "Each run of a solution flow is a `flowruns` row with status, error code and message, kept 28 days by default",
          "A service principal can own flows, and new HTTP request triggers default to callers signed in to the tenant"
        ],
        "weaknesses": [
          "Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported",
          "A flow's definition travels as `clientdata`, one string of encoded JSON with connection references the caller builds by hand",
          "No documented call runs, cancels or resubmits a flow. Starting one means an HTTP request trigger built into the flow",
          "The legacy Anyone trigger mode carries its signature in the URL query string as `sig=`",
          "Power Automate's own released versions page stops at version 2508.2 of August 2025, and service health needs an admin sign-in"
        ],
        "agentNotes": [
          "Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition",
          "Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use",
          "Put the flow in a solution first. Flows that sit only under My flows are outside the supported API",
          "On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance",
          "Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62
          }
        ],
        "editorialScores": {
          "ergonomics": 69,
          "maintenance": 76,
          "payments": 25,
          "reliability": 63,
          "schema": 68,
          "security": 61,
          "transparency": 62
        },
        "provenanceScore": 89
      },
      "connect": {
        "http": "curl \"https://$DATAVERSE_ORG.api.crm.dynamics.com/api/data/v9.2/workflows?\\$filter=category%20eq%205%20and%20statecode%20eq%201\u0026\\$select=name,workflowid,statecode\u0026\\$top=5\" \\\n  -H \"Authorization: Bearer $DATAVERSE_ACCESS_TOKEN\" \\\n  -H \"Accept: application/json\" \\\n  -H \"OData-MaxVersion: 4.0\" \\\n  -H \"OData-Version: 4.0\""
      },
      "letme": {
        "capability": "https://letme.dev/automation.workflows",
        "tool": "https://letme.dev/power-automate"
      },
      "sameCompany": [
        "azure-foundry-fine-tuning",
        "azure-ai-content-safety",
        "azure-speech-to-text",
        "azure-text-to-speech",
        "microsoft-agent-framework",
        "microsoft-execution-containers",
        "microsoft-entra-agent-id",
        "azure-key-vault",
        "azure-devops-mcp",
        "microsoft-learn-mcp",
        "playwright-mcp",
        "azure-mcp",
        "azure-maps",
        "azure-translator",
        "microsoft-graph-calendar",
        "microsoft-teams",
        "dynamics-365-sales",
        "microsoft-advertising-api",
        "microsoft-excel-graph",
        "outlook-mail-graph"
      ],
      "area": "business",
      "unitPrices": [
        {
          "item": "Power Automate Premium",
          "unit": "seat-month",
          "usd": 15,
          "note": "paid yearly, 40,000 Power Platform requests a day"
        },
        {
          "item": "Power Automate Process",
          "unit": "month",
          "usd": 150,
          "note": "per bot, paid yearly, 250,000 actions a day for one flow or a flow group"
        },
        {
          "item": "Power Automate Hosted Process",
          "unit": "month",
          "usd": 215,
          "note": "per bot, paid yearly, with a Microsoft-hosted virtual machine"
        }
      ],
      "provenance": {
        "legalEntity": "Microsoft Corporation",
        "domain": "microsoft.com",
        "domainRegistered": "1991-05-02",
        "domainNote": "The management API answers on a dynamics.com host such as https://\u003corg\u003e.api.crm.dynamics.com, flow trigger URLs on logic.azure.com and the inventory API on api.powerplatform.com, all Microsoft domains. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.microsoft.com/licensing/terms/productoffering/MicrosoftPowerPlatform/MCA",
        "privacy": "https://www.microsoft.com/en-us/privacy/privacystatement",
        "statusPage": "https://status.cloud.microsoft",
        "changelog": "https://learn.microsoft.com/en-us/dynamics365/released-versions/Microsoft-Dataverse",
        "securityTxt": "expired",
        "checked": "2026-10-08",
        "notes": [
          "The terms link is the Microsoft Product Terms page for Microsoft Power Platform under the Microsoft Customer Agreement, which names Power Automate Premium, Process and Hosted Process. It showed no effective date.",
          "The Microsoft privacy statement was last updated in September 2026 and says customer agreements control for enterprise and developer products. Customer data is governed by the Products and Services Data Protection Addendum, published as a .docx download, which we did not read.",
          "www.microsoft.com/.well-known/security.txt carries Expires 2026-09-23T16:00:00.000Z when read on 2026-10-08, with MSRC as the contact.",
          "status.cloud.microsoft rendered only a title for our reader. Tenant service health is in the Power Platform and Microsoft 365 admin centres behind an admin sign-in.",
          "The changelog link is the weekly Dataverse service update page, because flow management runs on Dataverse. Power Automate's own released versions page (https://learn.microsoft.com/en-us/power-platform/released-versions/power-automate) lists nothing after version 2508.2 of August 2025.",
          "RDAP for microsoft.com gives a registration date of 1991-05-02. dynamics.com, azure.com and powerplatform.com were not looked up."
        ],
        "score": 89
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/power-automate.json"
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Pipedream (Workday)",
        "b": "Microsoft",
        "name": "Vendor"
      },
      {
        "a": "https://api.pipedream.com/v1",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Pipedream Source Available License (components)",
        "b": "Proprietary service under the Microsoft Product Terms for Microsoft Power Platform",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-02",
        "b": "2026-10-02",
        "name": "Last release"
      },
      {
        "a": "no date given",
        "b": "no date given",
        "name": "Terms last updated"
      },
      {
        "a": "2026-02-02",
        "b": "2026-09-01",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "12k stars, 587k npm/wk, 328k PyPI/wk",
        "b": "11k PyPI/wk",
        "name": "Popularity"
      },
      {
        "a": "2.5/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Pipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories.",
        "question": "Which is better for AI agents, Pipedream API + MCP or Microsoft Power Automate?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Pipedream API + MCP and Microsoft Power Automate need an API key?"
      },
      {
        "answer": "Pipedream API + MCP has a hosted endpoint at https://api.pipedream.com/v1. No hosted endpoint is listed for Microsoft Power Automate.",
        "question": "Can an agent call Pipedream API + MCP and Microsoft Power Automate without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 74 against 68",
          "Payments \u0026 pricing, 40 against 25"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Best when an agent acts in many third-party apps on behalf of your own users and you don't want to run OAuth yourself.",
        "slug": "pipedream",
        "watchFor": "Public changelog's last entry is 1 October 2025"
      },
      {
        "aheadOn": null,
        "also": null,
        "goodFor": "Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.",
        "slug": "power-automate",
        "watchFor": "Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported"
      }
    ],
    "job": {
      "capability": "automation.workflows",
      "name": "Automation workflows"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/activepieces-vs-pipedream.json",
        "title": "Activepieces API + MCP vs Pipedream API + MCP",
        "url": "https://www.anchorterminal.com/compare/activepieces-vs-pipedream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/activepieces-vs-power-automate.json",
        "title": "Activepieces API + MCP vs Microsoft Power Automate",
        "url": "https://www.anchorterminal.com/compare/activepieces-vs-power-automate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/make-vs-pipedream.json",
        "title": "Make API + MCP vs Pipedream API + MCP",
        "url": "https://www.anchorterminal.com/compare/make-vs-pipedream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/make-vs-power-automate.json",
        "title": "Make API + MCP vs Microsoft Power Automate",
        "url": "https://www.anchorterminal.com/compare/make-vs-power-automate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/n8n-vs-pipedream.json",
        "title": "n8n API + MCP vs Pipedream API + MCP",
        "url": "https://www.anchorterminal.com/compare/n8n-vs-pipedream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/n8n-vs-power-automate.json",
        "title": "n8n API + MCP vs Microsoft Power Automate",
        "url": "https://www.anchorterminal.com/compare/n8n-vs-power-automate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paragon-vs-power-automate.json",
        "title": "Paragon ActionKit + MCP vs Microsoft Power Automate",
        "url": "https://www.anchorterminal.com/compare/paragon-vs-power-automate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipedream-vs-tray.json",
        "title": "Pipedream API + MCP vs Tray.ai API + MCP",
        "url": "https://www.anchorterminal.com/compare/pipedream-vs-tray"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipedream-vs-windmill.json",
        "title": "Pipedream API + MCP vs Windmill API + MCP",
        "url": "https://www.anchorterminal.com/compare/pipedream-vs-windmill"
      },
      {
        "json": "https://www.anchorterminal.com/compare/pipedream-vs-workato.json",
        "title": "Pipedream API + MCP vs Workato API + MCP",
        "url": "https://www.anchorterminal.com/compare/pipedream-vs-workato"
      },
      {
        "json": "https://www.anchorterminal.com/compare/power-automate-vs-tray.json",
        "title": "Microsoft Power Automate vs Tray.ai API + MCP",
        "url": "https://www.anchorterminal.com/compare/power-automate-vs-tray"
      },
      {
        "json": "https://www.anchorterminal.com/compare/power-automate-vs-windmill.json",
        "title": "Microsoft Power Automate vs Windmill API + MCP",
        "url": "https://www.anchorterminal.com/compare/power-automate-vs-windmill"
      },
      {
        "json": "https://www.anchorterminal.com/compare/power-automate-vs-workato.json",
        "title": "Microsoft Power Automate vs Workato API + MCP",
        "url": "https://www.anchorterminal.com/compare/power-automate-vs-workato"
      },
      {
        "json": "https://www.anchorterminal.com/compare/paragon-vs-pipedream.json",
        "title": "Paragon ActionKit + MCP vs Pipedream API + MCP",
        "url": "https://www.anchorterminal.com/compare/paragon-vs-pipedream"
      }
    ],
    "scores": [
      {
        "by": 2,
        "edge": "pipedream",
        "key": "reliability",
        "name": "Reliability",
        "pipedream": 65,
        "power-automate": 63,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 6,
        "edge": "pipedream",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "pipedream": 74,
        "power-automate": 68,
        "weight": 13
      },
      {
        "by": 4,
        "edge": "pipedream",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "pipedream": 73,
        "power-automate": 69,
        "weight": 13
      },
      {
        "by": 3,
        "edge": "power-automate",
        "key": "security",
        "name": "Security \u0026 auth",
        "pipedream": 58,
        "power-automate": 61,
        "weight": 14
      },
      {
        "by": 15,
        "edge": "pipedream",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "pipedream": 40,
        "power-automate": 25,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 3,
        "edge": "pipedream",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "pipedream": 79,
        "power-automate": 76,
        "weight": 7
      },
      {
        "by": 1,
        "edge": "power-automate",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "pipedream": 75,
        "power-automate": 76,
        "weight": 7
      }
    ],
    "summary": "Pipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories. Both do automation workflows.",
    "verdicts": {
      "pipedream": "Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.",
      "power-automate": "Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate",
    "json": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate.md",
    "slim": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate.min.md"
  },
  "markdown": "Pipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories. Both do automation workflows.\n\n- Pipedream API + MCP: grade B, 65.5/100, rank #255 of 722. Markdown https://www.anchorterminal.com/tools/pipedream.md · JSON https://www.anchorterminal.com/api/v1/tools/pipedream.json\n- Microsoft Power Automate: grade B, 62/100, rank #350 of 722. Markdown https://www.anchorterminal.com/tools/power-automate.md · JSON https://www.anchorterminal.com/api/v1/tools/power-automate.json\n\n## Which one, for what\n\n### Pipedream API + MCP (B)\n\nGood for: Best when an agent acts in many third-party apps on behalf of your own users and you don't want to run OAuth yourself.\n\nAhead on:\n- Schema \u0026 documentation, 74 against 68\n- Payments \u0026 pricing, 40 against 25\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Public changelog's last entry is 1 October 2025\n\n### Microsoft Power Automate (B)\n\nGood for: Organisations already on Microsoft 365 and Dataverse that want an agent to inventory, deploy or adjust flows inside existing roles and solutions.\n\nWatch for: Flows under My flows can't be managed in code, and Microsoft calls the `api.flow.microsoft.com` API unsupported\n\n\n## Score by category\n\n| Category | Weight | Pipedream API + MCP | Microsoft Power Automate | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 63 | Pipedream API + MCP +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 74 | 68 | Pipedream API + MCP +6 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 69 | Pipedream API + MCP +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 61 | Microsoft Power Automate +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 25 | Pipedream API + MCP +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 79 | 76 | Pipedream API + MCP +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 76 | Microsoft Power Automate +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.5 · B** | **62 · B** | |\n\n## Facts side by side\n\n| Fact | Pipedream API + MCP | Microsoft Power Automate |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Pipedream (Workday) | Microsoft |\n| Hosted endpoint | `https://api.pipedream.com/v1` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Pipedream Source Available License (components) | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-02 | 2026-10-02 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2026-02-02 | 2026-09-01 |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 12k stars, 587k npm/wk, 328k PyPI/wk | 11k PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Pipedream API + MCP.** Managed OAuth per end user across 3,000+ apps, through API, SDK or MCP. Public changelog's last entry is 1 October 2025.\n\n**Microsoft Power Automate.** Cloud flows in a solution are rows an agent can read and write through the Dataverse Web API under Entra ID OAuth and security roles, with published limits and a 99.9 per cent SLA. Flows under My flows can't be managed in code, a flow's body is one hand-built JSON string, and setup needs a tenant administrator.\n\n## Before you call either\n\n### Pipedream API + MCP\n\n1. Pass your own user ID as `x-pd-external-user-id` so each user's accounts stay separate\n2. Send `x-pd-app-slug` to load one app's tools rather than 10,000\n3. Use a Connect rate-limit token (`x-pd-rate-limit`) to cap runaway loops per user\n4. Check `isError` on tool results before treating a call as done\n5. Stay on `x-pd-environment: development` until billing is set, since production needs a paid plan\n\n### Microsoft Power Automate\n\n1. Filter `workflows` on `category eq 5` for cloud flows, and add `$select`, because `clientdata` holds the whole definition\n2. Flows created through the API start with `statecode` 0 (off). The docs say to turn the flow on before use\n3. Put the flow in a solution first. Flows that sit only under My flows are outside the supported API\n4. On 429 wait the `Retry-After` seconds. Reads of `flowruns` count against the daily Power Platform request allowance\n5. Treat an HTTP trigger URL with `sig=` as a secret, and prefer the tenant or named-user trigger modes with a bearer token for `https://service.flow.microsoft.com/`\n\n## Questions\n\n### Which is better for AI agents, Pipedream API + MCP or Microsoft Power Automate?\n\nPipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories.\n\n### Do Pipedream API + MCP and Microsoft Power Automate need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Pipedream API + MCP and Microsoft Power Automate without installing anything?\n\nPipedream API + MCP has a hosted endpoint at https://api.pipedream.com/v1. No hosted endpoint is listed for Microsoft Power Automate.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/pipedream-vs-power-automate.json, and with the fewest tokens: https://www.anchorterminal.com/compare/pipedream-vs-power-automate.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"pipedream\", \"b\": \"power-automate\"}`. From a terminal: `anchor compare pipedream power-automate`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/pipedream.json and https://www.anchorterminal.com/api/v1/tools/power-automate.json\n\n## Other comparisons with Pipedream API + MCP or Microsoft Power Automate\n\n- [Activepieces API + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/activepieces-vs-pipedream.md)\n- [Activepieces API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/activepieces-vs-power-automate.md)\n- [Make API + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/make-vs-pipedream.md)\n- [Make API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/make-vs-power-automate.md)\n- [n8n API + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/n8n-vs-pipedream.md)\n- [n8n API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/n8n-vs-power-automate.md)\n- [Paragon ActionKit + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/paragon-vs-power-automate.md)\n- [Pipedream API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/pipedream-vs-tray.md)\n- [Pipedream API + MCP vs Windmill API + MCP](https://www.anchorterminal.com/compare/pipedream-vs-windmill.md)\n- [Pipedream API + MCP vs Workato API + MCP](https://www.anchorterminal.com/compare/pipedream-vs-workato.md)\n- [Microsoft Power Automate vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-tray.md)\n- [Microsoft Power Automate vs Windmill API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-windmill.md)\n- [Microsoft Power Automate vs Workato API + MCP](https://www.anchorterminal.com/compare/power-automate-vs-workato.md)\n- [Paragon ActionKit + MCP vs Pipedream API + MCP](https://www.anchorterminal.com/compare/paragon-vs-pipedream.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Pipedream API + MCP vs Microsoft Power Automate",
        "url": ""
      }
    ],
    "description": "Pipedream API + MCP scores 65.5 (B) on agent readiness against Microsoft Power Automate's 62 (B), and leads in 5 of 7 scored categories. Both do automation workflows. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Pipedream API + MCP B 65.5",
      "Microsoft Power Automate B 62",
      "scores"
    ],
    "h1": "Pipedream API + MCP vs Microsoft Power Automate",
    "image": "https://www.anchorterminal.com/assets/og/compare-pipedream-vs-power-automate.png",
    "path": "/compare/pipedream-vs-power-automate",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Pipedream API + MCP vs Microsoft Power Automate for AI agents",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/pipedream-vs-power-automate"
  },
  "tokens": {
    "markdown": 2150,
    "slim": 630
  },
  "version": 1
}
