{ "data": { "a": { "slug": "expensify", "name": "Expensify", "vendor": "Expensify, Inc.", "vendorUrl": "https://www.expensify.com", "kind": "http-api", "category": "spend-management", "summary": "Expensify is an expense management service with receipt scanning, expense reports, approvals, reimbursement and company cards. Its Integration Server API exports report and card data and creates expenses, reports and workspace settings. A hosted MCP server gives read-only search.", "url": "https://www.anchorterminal.com/tools/expensify", "markdownUrl": "https://www.anchorterminal.com/tools/expensify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/expensify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/expensify.json", "license": "Proprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT", "transports": [ "http" ], "remoteUrl": "https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations", "packages": [], "auth": "mixed", "authNotes": "Access is self-serve for anyone with an Expensify account. Signing in at https://www.expensify.com/tools/integrations/ generates a partnerUserID and partnerUserSecret pair, shown once and replaceable on the same page. The pair travels inside the `requestJobDescription` form field and acts with the account's own rights, so domain and workspace admin jobs need an admin's credentials. Creating reports or expenses in other users' accounts needs Expensify to enable it for the domain by email to Concierge. OAuth2 for the API (authorisation code grant, scope `integrations:api`, two-hour access tokens, rotating refresh tokens) is in private beta by request form. The MCP server uses OAuth 2.1 with PKCE and the `mcp:tools` scope.", "pricing": "freemium", "pricingNotes": "No separate API fee is published. Collect is $5 per unique member a month, pay-per-use. Control is $18 per member a month on an annual subscription or $36 per active member pay-per-use, and as low as $9 with Expensify Card spend. A workspace starts a 30-day free trial, with a payment card asked for when it ends, and a free Submit workspace exists for individuals. An agent can start on the trial without a contract. No sandbox was found, and whether the API works without a paid plan wasn't established (checked 2026-10-08).", "priceSummary": "$5 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Integration Server reference, the help articles or the pricing article (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://integrations.expensify.com/Integration-Server/doc/", "capabilities": [ "spend.transactions", "spend.expenses" ], "tags": [ "hosted", "freemium", "api-key", "oauth", "mcp", "soc2", "pci-dss" ], "graded": true, "anchor": { "graded": true, "score": 41.1, "grade": "E", "agentReady": false, "rank": 801, "ranked": true, "rankOf": 842, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 23, "payments": 30, "reliability": 62, "schema": 28, "security": 34, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published and a status page that tracks the API separately. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, and one credential pair carries the whole account's rights.", "bestFor": "A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.", "strengths": [ "Export templates written in Freemarker let the caller choose every output field, in CSV, XLS, XLSX, TXT, PDF, JSON or XML, filtered by date, state, workspace and report ID", "Rate limits are published as 5 requests per 10 seconds and 20 per 60 seconds, with status 429 when exceeded", "The status page lists Integration APIs as its own component, and no incident in the 90 days to 8 October 2026 names it", "The hosted MCP server at https://www.expensify.com/mcp is read-only and uses OAuth 2.1 with PKCE, the `mcp:tools` scope and a revocation endpoint", "Every job in the reference has a curl example, a parameter table with valid values and a sample error response" ], "weaknesses": [ "No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API", "The partnerUserID and partnerUserSecret pair acts with all of the account's rights. No scopes or read-only credential were found for the API", "No idempotency key or pagination is documented, and no official SDK was found", "Errors arrive as `responseCode` in the body. An invalid credential returned HTTP 200 with `responseCode` 404 when we tried it on 8 October 2026", "The Terms of Service allow Expensify to modify or discontinue the service at any time without prior notice, and no SLA was found" ], "agentNotes": [ "POST `requestJobDescription` as a form field to the single endpoint. Keep it out of the URL query string, because it carries the secret", "Read `responseCode` in the body on every reply. HTTP status can be 200 on failure, and validation errors use 410", "Stay under 5 requests per 10 seconds and 20 per 60 seconds. No Retry-After header is documented, so space retries yourself", "Export in two calls. A `file` job returns a filename, then a `download` job fetches it. Amounts are in cents", "Don't retry a create job blindly. No idempotency key exists, so export and check before resending. Set `dry-run` to true when testing the Advanced Employee Updater" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.1 } ], "editorialScores": { "ergonomics": 45, "maintenance": 23, "payments": 30, "reliability": 62, "schema": 28, "security": 34, "transparency": 41 }, "provenanceScore": 75 }, "connect": { "http": "curl -X POST 'https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations' \\\n -d 'requestJobDescription={\"type\":\"get\",\"credentials\":{\"partnerUserID\":\"_REPLACE_\",\"partnerUserSecret\":\"_REPLACE_\"},\"inputSettings\":{\"type\":\"policyList\"}}'" }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/expensify" }, "area": "domain-data", "unitPrices": [ { "item": "Collect plan, pay-per-use", "unit": "seat-month", "usd": 5, "note": "Per unique member. No separate API fee is published" }, { "item": "Control plan, annual subscription", "unit": "seat-month", "usd": 18, "note": "As low as $9 with Expensify Card spend. Active members above the subscription size are $36" }, { "item": "Control plan, pay-per-use", "unit": "seat-month", "usd": 36, "note": "Per active member" } ], "provenance": { "legalEntity": "Expensify, Inc.", "domain": "expensify.com", "domainRegistered": "2007-10-26", "endpointOnVendorDomain": true, "terms": "https://www.expensify.com/terms", "privacy": "https://www.expensify.com/privacy", "statusPage": "https://status.expensify.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Service (last updated 10 September 2026) name Expensify, Inc., 401 SW 5th Ave, Portland, OR 97204, and govern the Expensify Service including related software and tools. No separate API agreement was found.", "The privacy policy (last updated 1 April 2026) is issued for the Expensify group and names Expensify, Inc. as controller.", "The API answers at integrations.expensify.com and the MCP server at www.expensify.com/mcp.", "https://www.expensify.com/.well-known/security.txt returned 404 on 8 October 2026.", "No changelog was found for the Integration Server API.", "RDAP for expensify.com gives a registration date of 2007-10-26." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/expensify.json", "live": { "slug": "expensify", "probe": { "target": "https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations", "method": "get", "lastAt": "2026-10-09T09:26:49.467838397Z", "lastOk": true, "lastStatus": 200, "lastMs": 601, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 434, "p95ms24h": 508, "samples24h": 171, "samples30d": 171, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 101, "ok": 101 } ] }, "vendorStatus": { "page": "https://status.expensify.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T09:25:09.253075546Z" }, "pages": [ { "url": "https://www.expensify.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:27:38.986175098Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a6875581ee6f" }, { "url": "https://www.expensify.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:27:41.220273608Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2df10b1a9dea" } ], "updatedAt": "2026-10-09T09:26:49.467838397Z" } }, "answer": "Payhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing.", "b": { "slug": "payhawk", "name": "Payhawk API + MCP", "vendor": "Payhawk Limited", "vendorUrl": "https://payhawk.com", "kind": "http-api", "category": "spend-management", "summary": "Spend management platform from Payhawk Limited in London, covering company cards, expenses, bills, purchase orders and travel. Outside agents reach it through a REST Developer API with read-only or full-access keys, and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/payhawk", "markdownUrl": "https://www.anchorterminal.com/tools/payhawk.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/payhawk.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/payhawk.json", "license": "Proprietary service under Payhawk's general terms and conditions", "transports": [ "http" ], "remoteUrl": "https://api.payhawk.com", "packages": [], "auth": "mixed", "authNotes": "Access needs a Payhawk customer account. An Administrator, an IT Administrator or a user with a custom role creates an API key in the portal under Settings, Integrations, choosing read-only or full access, and can regenerate it. The key goes in the `X-Payhawk-ApiKey` header or as a Bearer token. Two system-generated keys per account cannot be deleted by users. Group-level keys reach the group endpoints. If the key is not active, the API page says to write to partners@payhawk.com. The MCP server accepts OAuth 2 authorisation code with PKCE, where each user signs in with a Payhawk login and the assistant acts with that user's role.", "pricing": "paid", "pricingNotes": "Sold by quote per module (Travel, Cards and Expenses, Accounts Payable, Procurement) on annual or multi-year contracts, with unit-based charges for extra cards, reimbursements, purchase orders and invoices. The one published price is the Growth programme at 149 pounds a month for single-entity firms in the UK or EEA with fewer than 20 employees, with an optional 7-day trial for eligible customers. The API page says the API is free for all Payhawk accounts, and the pricing page lists Developer API access and the MCP server in the modules. A development sandbox is requested through a form on the API page (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI definition, the help centre or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 82, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developers.payhawk.com", "llmsTxt": "https://payhawk.com/llms.txt", "openapi": "https://api.payhawk.com/api/v3/docs.json", "capabilities": [ "spend.transactions", "spend.expenses", "spend.cards", "spend.bills", "spend.procurement" ], "tags": [ "hosted", "enterprise", "api-key", "oauth", "mcp", "openapi", "llms-txt", "webhooks", "sales-led", "status-page", "soc2", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 57.1, "grade": "C", "agentReady": false, "rank": 561, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 52, "maintenance": 53, "payments": 13, "reliability": 58, "schema": 71, "security": 71, "transparency": 78 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The Developer API has a public OpenAPI 3.1 definition with 179 operations, read-only or full-access keys and a published limit of 15 requests a second. It needs a Payhawk customer account, no official SDK or API changelog was found, and the 82-tool MCP server is added by hand because it is not yet in the assistant directories.", "bestFor": "A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals.", "strengths": [ "Public OpenAPI 3.1 definition with 105 paths and 179 operations, covering expenses, cards, fund accounts, suppliers, purchase orders and 24 webhook event types", "API keys are created as read-only or full access, sent in a header, and managed by administrators or a custom role", "The limit of 15 requests a second is stated on every operation, and responses carry RateLimit headers with Retry-After on a 429", "The MCP server acts with the signed-in user's own role, previews every write for confirmation, and never starts a payment or transfer", "SOC 1 and SOC 2 Type 2, ISO 27001, PCI DSS Level 1 and a penetration test attestation are downloadable from the trust page" ], "weaknesses": [ "No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form", "No official SDK on npm or PyPI, no API changelog and no deprecation policy were found. Release notes cover the product only", "The API page's FAQ contradicts the definition on the host name, the page size and whether expenses can be created or reviewed", "The status page is drawn by script, so its incident history could not be read. The terms disclaim service levels", "The MCP server has 82 tools, is not in the official MCP registry, and no guidance on prompt injection was found" ], "agentNotes": [ "Send the key in `X-Payhawk-ApiKey` or as a Bearer token to `https://api.payhawk.com/api/v3`. A read-only key returns 403 on writes", "Page lists with `$skip` and `$take`. The help centre gives 1,000 a page and the definition a maximum of 10,000, so count what comes back", "Pass `$filter` as URL-encoded JSON, for example `{\"status\":{\"$equal\":\"draft\"}}`. Date filters compare the date part only", "Keep to 15 requests a second and wait for `Retry-After` on a 429. Do not send `Idempotency-Key` when creating a per diem expense, which returns 400", "Use a group-level key and the `/groups/{groupId}` paths for master data in a multi-entity group. Expenses and payments stay on account paths" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.1 } ], "editorialScores": { "ergonomics": 52, "maintenance": 53, "payments": 13, "reliability": 58, "schema": 71, "security": 71, "transparency": 55 }, "provenanceScore": 100 }, "connect": { "http": "curl https://api.payhawk.com/api/v3/accounts/YOUR_ACCOUNT_ID/fund-accounts \\\n -H \"X-Payhawk-ApiKey: YOUR_API_KEY\"" }, "letme": { "capability": "https://letme.dev/spend.transactions", "tool": "https://letme.dev/payhawk" }, "area": "domain-data", "provenance": { "legalEntity": "Payhawk Limited", "domain": "payhawk.com", "domainRegistered": "2003-07-06", "endpointOnVendorDomain": true, "terms": "https://payhawk.com/terms", "privacy": "https://payhawk.com/privacy", "statusPage": "https://status.payhawk.com", "changelog": "https://payhawk.com/release-notes", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The terms name Payhawk Limited (company number 11747263, Chancery House, 53-64 Chancery Lane, London WC2A 1QS) as the contracting entity worldwide and Payhawk Inc., a Delaware corporation, in the US. Payhawk EOOD in Sofia owns the platform.", "Cards are issued by Payhawk Financial Services UAB in the EEA, Payhawk Financial Services Limited in the UK and Cross River Bank in the US, per the site footer.", "The API answers at api.payhawk.com and the MCP server at mcp.payhawk.com. An unauthenticated POST to /mcp returned 401 with a WWW-Authenticate header naming the protected resource metadata.", "payhawk.com/.well-known/security.txt has a contact, a policy link and an expiry of 1 January 2030.", "The terms were last updated on 9 December 2025, the privacy policy on 29 June 2026 and the Data Processing Addendum on 26 June 2026.", "The release notes cover the product. No changelog for the API was found.", "RDAP for payhawk.com gives a registration date of 2003-07-06. The terms' company number dates the company later, so the domain predates the vendor." ], "score": 100 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/payhawk.json", "live": { "slug": "payhawk", "probe": { "target": "https://api.payhawk.com", "method": "get", "lastAt": "2026-10-09T09:27:00.11605886Z", "lastOk": true, "lastStatus": 404, "lastMs": 123, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 53, "p95ms24h": 123, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-09", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.payhawk.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:24.812233514Z" }, "updatedAt": "2026-10-09T09:27:00.11605886Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Expensify, Inc.", "b": "Payhawk Limited", "name": "Vendor" }, { "a": "https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations", "b": "https://api.payhawk.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "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 Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT", "b": "Proprietary service under Payhawk's general terms and conditions", "name": "Licence" }, { "a": "none", "b": "82", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-08", "name": "Last release" }, { "a": "2026-09-10", "b": "2025-12-09", "name": "Terms last updated" }, { "a": "2026-04-01", "b": "2026-06-29", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "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": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Payhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Expensify or Payhawk API + MCP?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Expensify and Payhawk API + MCP need an API key?" }, { "answer": "Yes. Expensify has a hosted endpoint at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations and Payhawk API + MCP at https://api.payhawk.com.", "question": "Can an agent call Expensify and Payhawk API + MCP without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 13" ], "also": null, "goodFor": "A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.", "slug": "expensify", "watchFor": "No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API" }, { "aheadOn": [ "Schema \u0026 documentation, 71 against 28", "Agent ergonomics, 52 against 45", "Security \u0026 auth, 71 against 34", "Maintenance \u0026 community, 53 against 23", "Transparency \u0026 trust, 78 against 58" ], "also": null, "goodFor": "A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals.", "slug": "payhawk", "watchFor": "No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form" } ], "job": { "capability": "spend.transactions", "name": "Spend transactions" }, "others": [ { "json": "https://www.anchorterminal.com/compare/airwallex-vs-expensify.json", "title": "Airwallex Spend and Issuing vs Expensify", "url": "https://www.anchorterminal.com/compare/airwallex-vs-expensify" }, { "json": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk.json", "title": "Airwallex Spend and Issuing vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/airwallex-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/bill-vs-expensify.json", "title": "BILL vs Expensify", "url": "https://www.anchorterminal.com/compare/bill-vs-expensify" }, { "json": "https://www.anchorterminal.com/compare/bill-vs-payhawk.json", "title": "BILL vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/bill-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/brex-vs-expensify.json", "title": "Brex vs Expensify", "url": "https://www.anchorterminal.com/compare/brex-vs-expensify" }, { "json": "https://www.anchorterminal.com/compare/brex-vs-payhawk.json", "title": "Brex vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/brex-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-mercury.json", "title": "Expensify vs Mercury API", "url": "https://www.anchorterminal.com/compare/expensify-vs-mercury" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-pleo.json", "title": "Expensify vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/expensify-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-ramp.json", "title": "Expensify vs Ramp", "url": "https://www.anchorterminal.com/compare/expensify-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/expensify-vs-spendesk.json", "title": "Expensify vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/expensify-vs-spendesk" }, { "json": "https://www.anchorterminal.com/compare/mercury-vs-payhawk.json", "title": "Mercury API vs Payhawk API + MCP", "url": "https://www.anchorterminal.com/compare/mercury-vs-payhawk" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-pleo.json", "title": "Payhawk API + MCP vs Pleo API + MCP", "url": "https://www.anchorterminal.com/compare/payhawk-vs-pleo" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-ramp.json", "title": "Payhawk API + MCP vs Ramp", "url": "https://www.anchorterminal.com/compare/payhawk-vs-ramp" }, { "json": "https://www.anchorterminal.com/compare/payhawk-vs-spendesk.json", "title": "Payhawk API + MCP vs Spendesk API + MCP", "url": "https://www.anchorterminal.com/compare/payhawk-vs-spendesk" } ], "scores": [ { "by": 4, "edge": "expensify", "expensify": 62, "key": "reliability", "name": "Reliability", "payhawk": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 43, "edge": "payhawk", "expensify": 28, "key": "schema", "name": "Schema \u0026 documentation", "payhawk": 71, "weight": 13 }, { "by": 7, "edge": "payhawk", "expensify": 45, "key": "ergonomics", "name": "Agent ergonomics", "payhawk": 52, "weight": 13 }, { "by": 37, "edge": "payhawk", "expensify": 34, "key": "security", "name": "Security \u0026 auth", "payhawk": 71, "weight": 14 }, { "by": 17, "edge": "expensify", "expensify": 30, "key": "payments", "name": "Payments \u0026 pricing", "payhawk": 13, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "payhawk", "expensify": 23, "key": "maintenance", "name": "Maintenance \u0026 community", "payhawk": 53, "weight": 7 }, { "by": 20, "edge": "payhawk", "expensify": 58, "key": "transparency", "name": "Transparency \u0026 trust", "payhawk": 78, "weight": 7 } ], "summary": "Payhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing. Both do spend transactions.", "verdicts": { "expensify": "One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published and a status page that tracks the API separately. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, and one credential pair carries the whole account's rights.", "payhawk": "The Developer API has a public OpenAPI 3.1 definition with 179 operations, read-only or full-access keys and a published limit of 15 requests a second. It needs a Payhawk customer account, no official SDK or API changelog was found, and the 82-tool MCP server is added by hand because it is not yet in the assistant directories." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/expensify-vs-payhawk", "json": "https://www.anchorterminal.com/compare/expensify-vs-payhawk.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/expensify-vs-payhawk.md", "slim": "https://www.anchorterminal.com/compare/expensify-vs-payhawk.min.md" }, "markdown": "Payhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing. Both do spend transactions.\n\n- Expensify: grade E, 41.1/100, rank #801 of 842. Markdown https://www.anchorterminal.com/tools/expensify.md · JSON https://www.anchorterminal.com/api/v1/tools/expensify.json\n- Payhawk API + MCP: grade C, 57.1/100, rank #561 of 842. Markdown https://www.anchorterminal.com/tools/payhawk.md · JSON https://www.anchorterminal.com/api/v1/tools/payhawk.json\n\n## Which one, for what\n\n### Expensify (E)\n\nGood for: A finance team already on Expensify that wants an agent to export approved reports to an accounting system, create expenses and reports, keep categories, tags and employees in step with an HR system, or mark reports reimbursed.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 13\n\nWatch for: No OpenAPI spec, llms.txt, version number or changelog was found for the Integration Server API\n\n### Payhawk API + MCP (C)\n\nGood for: A finance team already on Payhawk that wants an ERP or accounting sync, master data kept in step, purchase orders raised from another system, or an assistant that answers spend questions and prepares approvals.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 28\n- Agent ergonomics, 52 against 45\n- Security \u0026 auth, 71 against 34\n- Maintenance \u0026 community, 53 against 23\n- Transparency \u0026 trust, 78 against 58\n\nWatch for: No self-serve route. The API needs a Payhawk customer account, and a development sandbox is requested through a form\n\n\n## Score by category\n\n| Category | Weight | Expensify | Payhawk API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 58 | Expensify +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 28 | 71 | Payhawk API + MCP +43 |\n| Agent ergonomics | 13% (16.2 this run) | 45 | 52 | Payhawk API + MCP +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 34 | 71 | Payhawk API + MCP +37 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 13 | Expensify +17 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 23 | 53 | Payhawk API + MCP +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 78 | Payhawk API + MCP +20 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **41.1 · E** | **57.1 · C** | |\n\n## Facts side by side\n\n| Fact | Expensify | Payhawk API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Expensify, Inc. | Payhawk Limited |\n| Hosted endpoint | `https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations` | `https://api.payhawk.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Expensify Terms of Service. The Expensify app client and help articles on GitHub (Expensify/App) are MIT | Proprietary service under Payhawk's general terms and conditions |\n| Tools exposed | none | 82 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-08 |\n| Terms last updated | 2026-09-10 | 2025-12-09 |\n| Privacy policy last updated | 2026-04-01 | 2026-06-29 |\n| Customer content may train models | not found in the text | not found in the text |\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 | yes | not found in the text |\n\n## Verdicts\n\n**Expensify.** One endpoint exports reports through caller-written templates and creates expenses, reports, rules and workspace settings, with limits of 5 requests per 10 seconds published and a status page that tracks the API separately. There is no OpenAPI spec, changelog, SDK, pagination or idempotency key, and one credential pair carries the whole account's rights.\n\n**Payhawk API + MCP.** The Developer API has a public OpenAPI 3.1 definition with 179 operations, read-only or full-access keys and a published limit of 15 requests a second. It needs a Payhawk customer account, no official SDK or API changelog was found, and the 82-tool MCP server is added by hand because it is not yet in the assistant directories.\n\n## Before you call either\n\n### Expensify\n\n1. POST `requestJobDescription` as a form field to the single endpoint. Keep it out of the URL query string, because it carries the secret\n2. Read `responseCode` in the body on every reply. HTTP status can be 200 on failure, and validation errors use 410\n3. Stay under 5 requests per 10 seconds and 20 per 60 seconds. No Retry-After header is documented, so space retries yourself\n4. Export in two calls. A `file` job returns a filename, then a `download` job fetches it. Amounts are in cents\n5. Don't retry a create job blindly. No idempotency key exists, so export and check before resending. Set `dry-run` to true when testing the Advanced Employee Updater\n\n### Payhawk API + MCP\n\n1. Send the key in `X-Payhawk-ApiKey` or as a Bearer token to `https://api.payhawk.com/api/v3`. A read-only key returns 403 on writes\n2. Page lists with `$skip` and `$take`. The help centre gives 1,000 a page and the definition a maximum of 10,000, so count what comes back\n3. Pass `$filter` as URL-encoded JSON, for example `{\"status\":{\"$equal\":\"draft\"}}`. Date filters compare the date part only\n4. Keep to 15 requests a second and wait for `Retry-After` on a 429. Do not send `Idempotency-Key` when creating a per diem expense, which returns 400\n5. Use a group-level key and the `/groups/{groupId}` paths for master data in a multi-entity group. Expenses and payments stay on account paths\n\n## Questions\n\n### Which is better for AI agents, Expensify or Payhawk API + MCP?\n\nPayhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing.\n\n### Do Expensify and Payhawk API + MCP need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Expensify and Payhawk API + MCP without installing anything?\n\nYes. Expensify has a hosted endpoint at https://integrations.expensify.com/Integration-Server/ExpensifyIntegrations and Payhawk API + MCP at https://api.payhawk.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/expensify-vs-payhawk.json, and with the fewest tokens: https://www.anchorterminal.com/compare/expensify-vs-payhawk.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"expensify\", \"b\": \"payhawk\"}`. From a terminal: `anchor compare expensify payhawk`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/expensify.json and https://www.anchorterminal.com/api/v1/tools/payhawk.json\n\n## Other comparisons with Expensify or Payhawk API + MCP\n\n- [Airwallex Spend and Issuing vs Expensify](https://www.anchorterminal.com/compare/airwallex-vs-expensify.md)\n- [Airwallex Spend and Issuing vs Payhawk API + MCP](https://www.anchorterminal.com/compare/airwallex-vs-payhawk.md)\n- [BILL vs Expensify](https://www.anchorterminal.com/compare/bill-vs-expensify.md)\n- [BILL vs Payhawk API + MCP](https://www.anchorterminal.com/compare/bill-vs-payhawk.md)\n- [Brex vs Expensify](https://www.anchorterminal.com/compare/brex-vs-expensify.md)\n- [Brex vs Payhawk API + MCP](https://www.anchorterminal.com/compare/brex-vs-payhawk.md)\n- [Expensify vs Mercury API](https://www.anchorterminal.com/compare/expensify-vs-mercury.md)\n- [Expensify vs Pleo API + MCP](https://www.anchorterminal.com/compare/expensify-vs-pleo.md)\n- [Expensify vs Ramp](https://www.anchorterminal.com/compare/expensify-vs-ramp.md)\n- [Expensify vs Spendesk API + MCP](https://www.anchorterminal.com/compare/expensify-vs-spendesk.md)\n- [Mercury API vs Payhawk API + MCP](https://www.anchorterminal.com/compare/mercury-vs-payhawk.md)\n- [Payhawk API + MCP vs Pleo API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-pleo.md)\n- [Payhawk API + MCP vs Ramp](https://www.anchorterminal.com/compare/payhawk-vs-ramp.md)\n- [Payhawk API + MCP vs Spendesk API + MCP](https://www.anchorterminal.com/compare/payhawk-vs-spendesk.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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": "Expensify vs Payhawk API + MCP", "url": "" } ], "description": "Payhawk API + MCP scores 57.1 (C) on agent readiness against Expensify's 41.1 (E), and leads in 5 of 7 scored categories. Expensify leads on payments \u0026 pricing. Both do spend transactions. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Expensify E 41.1", "Payhawk API + MCP C 57.1", "scores" ], "h1": "Expensify vs Payhawk API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-expensify-vs-payhawk.png", "path": "/compare/expensify-vs-payhawk", "published": "2026-10-01", "section": "tools", "title": "Expensify vs Payhawk API + MCP for AI agents, E 41.1 vs C 57.1", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/expensify-vs-payhawk" }, "tokens": { "markdown": 2250, "slim": 730 }, "version": 1 }