{ "data": { "a": { "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" }, "answer": "Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth.", "b": { "slug": "tray", "name": "Tray.ai API + MCP", "vendor": "Tray.ai", "vendorUrl": "https://tray.ai", "kind": "http-api", "category": "workflow-automation", "summary": "Low-code integration platform with an embedded product for SaaS vendors.", "url": "https://www.anchorterminal.com/tools/tray", "markdownUrl": "https://www.anchorterminal.com/tools/tray.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tray.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tray.json", "license": "proprietary", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.tray.io/core/v1", "packages": [], "auth": "mixed", "authNotes": "REST and GraphQL endpoints take a bearer token, either the org master token (you act) or an end user's user token (you act as them). Tray Headless MCP uses a one-time OAuth2 sign-in bound to one workspace, and the docs say not to send a static Authorization header. Agent Gateway MCP servers take OAuth2 or an API token, and API token users can't use per-user credentials.", "pricing": "paid", "pricingNotes": "Pro, Team and Enterprise plans, all quoted by sales and billed on tasks that cover integration, automation, MCP and agent use. Every plan lists full API access and Tray Headless, and Agent Gateway is an add-on. A free trial exists with no stated length. No prices are published (https://tray.ai/pricing/).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in Tray docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://tray.ai/documentation/developer/getting-started/introduction", "llmsTxt": "https://tray.ai/documentation/llms.txt", "openapi": "https://tray.ai/documentation/files/openapi/trayapi.yaml", "capabilities": [ "automation.workflows", "automation.apps", "automation.embedded", "automation.code", "automation.webhooks", "automation.auth", "agent.tools" ], "tags": [ "hosted", "mcp", "llms-txt", "openapi", "enterprise", "closed-source", "webhooks" ], "lastRelease": "2026-09-09", "graded": true, "anchor": { "graded": true, "score": 55.5, "grade": "C", "agentReady": false, "rank": 508, "ranked": true, "rankOf": 722, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 33, "maintenance": 60, "payments": 0, "reliability": 72, "schema": 80, "security": 66, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Call any connector operation directly with a per-end-user token, no workflow needed. No published prices and no self-serve plan.", "bestFor": "SaaS vendors embedding integrations for their customers, with an agent that acts per end user.", "strengths": [ "Call any connector operation directly with a per-end-user token, no workflow needed", "Published API limits, 30 requests a second with bursts to 50", "Every action logged and streamable, with settable retention and log masking", "Four minor incidents in 90 days, none on the core APIs", "US, EU and APAC regions, SOC 2 Type 2 and a pentest dated 23 September 2026" ], "weaknesses": [ "No published prices and no self-serve plan", "Upstream 429s are wrapped in a 200, which hides throttling from naive retry logic", "Headless MCP can delete projects, workflows and auths with no server-side confirmation", "No official SDK and no tool annotations", "API lives on api.tray.io while the brand, docs and legal pages are on tray.ai" ], "agentNotes": [ "Use a user token when acting for a customer and the master token only for admin work", "Parse the body of call-connector responses for upstream status codes before treating a 200 as success", "Point Headless MCP at the workspace's region, api.eu1.tray.io or api.ap1.tray.io outside the US", "Pick the workspace at OAuth sign-in. Headless MCP binds it to the session and takes no workspace ID", "Ask before any Headless MCP delete. The server won't" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.5 } ], "editorialScores": { "ergonomics": 33, "maintenance": 60, "payments": 0, "reliability": 72, "schema": 80, "security": 66, "transparency": 67 }, "provenanceScore": 68 }, "connect": { "http": "curl https://api.tray.io/core/v1/connectors -H \"Authorization: Bearer $TRAY_MASTER_TOKEN\"", "claudeCode": "claude mcp add --transport http tray https://api.tray.io/mcp", "config": { "mcpServers": { "tray": { "url": "https://api.tray.io/mcp" } } } }, "letme": { "capability": "https://letme.dev/automation.workflows", "tool": "https://letme.dev/tray" }, "area": "business", "provenance": { "legalEntity": "Tray.ai, Inc.", "domain": "tray.ai", "domainRegistered": "2017-12-15", "domainNote": "The API and MCP hosts are on tray.io, the company's former domain. The brand, docs and legal pages are on tray.ai.", "endpointOnVendorDomain": false, "terms": "https://tray.ai/legal/msa/", "privacy": "https://tray.ai/legal/privacy-policy/", "statusPage": "https://status.tray.ai/", "changelog": "https://tray.ai/documentation/releases", "securityTxt": "none", "checked": "2026-09-30", "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tray.json", "live": { "slug": "tray", "probe": { "target": "https://api.tray.io/core/v1", "method": "get", "lastAt": "2026-10-08T21:12:23.905466749Z", "lastOk": true, "lastStatus": 404, "lastMs": 446, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 449, "p95ms24h": 530, "samples24h": 271, "samples30d": 2157, "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": 239, "ok": 239 } ] }, "vendorStatus": { "page": "https://status.tray.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:28.424843706Z" }, "securityTxt": { "url": "https://tray.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:59.834964634Z" }, "llmsTxt": { "url": "https://tray.ai/documentation/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:56.974439042Z" }, "domain": { "domain": "tray.ai", "registered": "2017-12-15", "source": "https://rdap.identitydigital.services/rdap/domain/tray.ai", "checkedAt": "2026-10-04T13:09:14.155471976Z" }, "pages": [ { "url": "https://tray.ai/documentation/releases", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:25:17.997047088Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7b99a20c97aa" }, { "url": "https://tray.ai/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:25:24.091767607Z", "changedAt": "2026-10-07T18:10:12.327281171Z", "fingerprint": "adf78e7b6aca" }, { "url": "https://tray.ai/legal/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:25:22.088982995Z", "changedAt": "2026-10-07T18:10:10.594781985Z", "fingerprint": "8e4a2a8f5e95" }, { "url": "https://tray.ai/legal/msa/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:25:20.248452923Z", "changedAt": "2026-10-07T18:10:08.537401988Z", "fingerprint": "be6b48f8b5d1" } ], "updatedAt": "2026-10-08T21:12:23.905466749Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Microsoft", "b": "Tray.ai", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.tray.io/core/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Microsoft Product Terms for Microsoft Power Platform", "b": "proprietary", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-02", "b": "2026-09-09", "name": "Last release" }, { "a": "no date given", "b": "2025-01-28", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "2026-01-01", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "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": "11k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth.", "question": "Which is better for AI agents, Microsoft Power Automate or Tray.ai API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Microsoft Power Automate and Tray.ai API + MCP need an API key?" }, { "answer": "No hosted endpoint is listed for Microsoft Power Automate. Tray.ai API + MCP has a hosted endpoint at https://api.tray.io/core/v1.", "question": "Can an agent call Microsoft Power Automate and Tray.ai API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 69 against 33", "Payments \u0026 pricing, 25 against 0", "Maintenance \u0026 community, 76 against 60", "Transparency \u0026 trust, 76 against 68" ], "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" }, { "aheadOn": [ "Reliability, 72 against 63", "Schema \u0026 documentation, 80 against 68", "Security \u0026 auth, 66 against 61" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "SaaS vendors embedding integrations for their customers, with an agent that acts per end user.", "slug": "tray", "watchFor": "No published prices and no self-serve plan" } ], "job": { "capability": "automation.workflows", "name": "Automation workflows" }, "others": [ { "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/activepieces-vs-tray.json", "title": "Activepieces API + MCP vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/activepieces-vs-tray" }, { "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/make-vs-tray.json", "title": "Make API + MCP vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/make-vs-tray" }, { "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/n8n-vs-tray.json", "title": "n8n API + MCP vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/n8n-vs-tray" }, { "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-power-automate.json", "title": "Pipedream API + MCP vs Microsoft Power Automate", "url": "https://www.anchorterminal.com/compare/pipedream-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/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/tray-vs-windmill.json", "title": "Tray.ai API + MCP vs Windmill API + MCP", "url": "https://www.anchorterminal.com/compare/tray-vs-windmill" }, { "json": "https://www.anchorterminal.com/compare/tray-vs-workato.json", "title": "Tray.ai API + MCP vs Workato API + MCP", "url": "https://www.anchorterminal.com/compare/tray-vs-workato" }, { "json": "https://www.anchorterminal.com/compare/paragon-vs-tray.json", "title": "Paragon ActionKit + MCP vs Tray.ai API + MCP", "url": "https://www.anchorterminal.com/compare/paragon-vs-tray" } ], "scores": [ { "by": 9, "edge": "tray", "key": "reliability", "name": "Reliability", "power-automate": 63, "tray": 72, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 12, "edge": "tray", "key": "schema", "name": "Schema \u0026 documentation", "power-automate": 68, "tray": 80, "weight": 13 }, { "by": 36, "edge": "power-automate", "key": "ergonomics", "name": "Agent ergonomics", "power-automate": 69, "tray": 33, "weight": 13 }, { "by": 5, "edge": "tray", "key": "security", "name": "Security \u0026 auth", "power-automate": 61, "tray": 66, "weight": 14 }, { "by": 25, "edge": "power-automate", "key": "payments", "name": "Payments \u0026 pricing", "power-automate": 25, "tray": 0, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "power-automate", "key": "maintenance", "name": "Maintenance \u0026 community", "power-automate": 76, "tray": 60, "weight": 7 }, { "by": 8, "edge": "power-automate", "key": "transparency", "name": "Transparency \u0026 trust", "power-automate": 76, "tray": 68, "weight": 7 } ], "summary": "Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth. Both do automation workflows.", "verdicts": { "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.", "tray": "Call any connector operation directly with a per-end-user token, no workflow needed. No published prices and no self-serve plan." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/power-automate-vs-tray", "json": "https://www.anchorterminal.com/compare/power-automate-vs-tray.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/power-automate-vs-tray.md", "slim": "https://www.anchorterminal.com/compare/power-automate-vs-tray.min.md" }, "markdown": "Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth. Both do automation workflows.\n\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- Tray.ai API + MCP: grade C, 55.5/100, rank #508 of 722. Markdown https://www.anchorterminal.com/tools/tray.md · JSON https://www.anchorterminal.com/api/v1/tools/tray.json\n\n## Which one, for what\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\nAhead on:\n- Agent ergonomics, 69 against 33\n- Payments \u0026 pricing, 25 against 0\n- Maintenance \u0026 community, 76 against 60\n- Transparency \u0026 trust, 76 against 68\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### Tray.ai API + MCP (C)\n\nGood for: SaaS vendors embedding integrations for their customers, with an agent that acts per end user.\n\nAhead on:\n- Reliability, 72 against 63\n- Schema \u0026 documentation, 80 against 68\n- Security \u0026 auth, 66 against 61\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No published prices and no self-serve plan\n\n\n## Score by category\n\n| Category | Weight | Microsoft Power Automate | Tray.ai API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 72 | Tray.ai API + MCP +9 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 80 | Tray.ai API + MCP +12 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 33 | Microsoft Power Automate +36 |\n| Security \u0026 auth | 14% (17.5 this run) | 61 | 66 | Tray.ai API + MCP +5 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 0 | Microsoft Power Automate +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 76 | 60 | Microsoft Power Automate +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 76 | 68 | Microsoft Power Automate +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62 · B** | **55.5 · C** | |\n\n## Facts side by side\n\n| Fact | Microsoft Power Automate | Tray.ai API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Microsoft | Tray.ai |\n| Hosted endpoint | no (local only) | `https://api.tray.io/core/v1` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Microsoft Product Terms for Microsoft Power Platform | proprietary |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-02 | 2026-09-09 |\n| Terms last updated | no date given | 2025-01-28 |\n| Privacy policy last updated | 2026-09-01 | 2026-01-01 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 11k PyPI/wk | none |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\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**Tray.ai API + MCP.** Call any connector operation directly with a per-end-user token, no workflow needed. No published prices and no self-serve plan.\n\n## Before you call either\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### Tray.ai API + MCP\n\n1. Use a user token when acting for a customer and the master token only for admin work\n2. Parse the body of call-connector responses for upstream status codes before treating a 200 as success\n3. Point Headless MCP at the workspace's region, api.eu1.tray.io or api.ap1.tray.io outside the US\n4. Pick the workspace at OAuth sign-in. Headless MCP binds it to the session and takes no workspace ID\n5. Ask before any Headless MCP delete. The server won't\n\n## Questions\n\n### Which is better for AI agents, Microsoft Power Automate or Tray.ai API + MCP?\n\nMicrosoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth.\n\n### Do Microsoft Power Automate and Tray.ai API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Microsoft Power Automate and Tray.ai API + MCP without installing anything?\n\nNo hosted endpoint is listed for Microsoft Power Automate. Tray.ai API + MCP has a hosted endpoint at https://api.tray.io/core/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/power-automate-vs-tray.json, and with the fewest tokens: https://www.anchorterminal.com/compare/power-automate-vs-tray.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"power-automate\", \"b\": \"tray\"}`. From a terminal: `anchor compare power-automate tray`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/power-automate.json and https://www.anchorterminal.com/api/v1/tools/tray.json\n\n## Other comparisons with Microsoft Power Automate or Tray.ai API + MCP\n\n- [Activepieces API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/activepieces-vs-power-automate.md)\n- [Activepieces API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/activepieces-vs-tray.md)\n- [Make API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/make-vs-power-automate.md)\n- [Make API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/make-vs-tray.md)\n- [n8n API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/n8n-vs-power-automate.md)\n- [n8n API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/n8n-vs-tray.md)\n- [Paragon ActionKit + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/paragon-vs-power-automate.md)\n- [Pipedream API + MCP vs Microsoft Power Automate](https://www.anchorterminal.com/compare/pipedream-vs-power-automate.md)\n- [Pipedream API + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/pipedream-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- [Tray.ai API + MCP vs Windmill API + MCP](https://www.anchorterminal.com/compare/tray-vs-windmill.md)\n- [Tray.ai API + MCP vs Workato API + MCP](https://www.anchorterminal.com/compare/tray-vs-workato.md)\n- [Paragon ActionKit + MCP vs Tray.ai API + MCP](https://www.anchorterminal.com/compare/paragon-vs-tray.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": "Microsoft Power Automate vs Tray.ai API + MCP", "url": "" } ], "description": "Microsoft Power Automate scores 62 (B) on agent readiness against Tray.ai API + MCP's 55.5 (C), and leads in 4 of 7 scored categories. Tray.ai API + MCP leads on reliability, schema \u0026 documentation and security \u0026 auth. Both do automation workflows. Category scores, facts…", "facts": [ "Microsoft Power Automate B 62", "Tray.ai API + MCP C 55.5", "scores" ], "h1": "Microsoft Power Automate vs Tray.ai API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-power-automate-vs-tray.png", "path": "/compare/power-automate-vs-tray", "published": "2026-10-01", "section": "tools", "title": "Microsoft Power Automate vs Tray.ai API + MCP for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/power-automate-vs-tray" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }