Can AI agents automate Perk?
Perk · saas · financeenterprise
Perk is automatable today through its first-party MCP server at https://mcp.perk.com/api/mcp/mcp. This record is the Perk travel, spend, invoice, and events platform. It is not SAP Concur, Navan, Brex, or Ramp. The MCP server uses OAuth 2.0 authorization code with PKCE and dynamic client registration. The opened tools reference covers trips, flight, hotel, train, and car search, expenses, invoices, reporting, policy, events, cards, and trip-approval links. Checkout links and trip-approval links finish in the Perk web app. Reporting data is one day behind; expense queries are live. Access follows the signed-in role and plan. The Travel REST API at https://api.perk.com returns JSON for trips, bookings, invoices, users, companies, and cost centers, plus SCIM user provisioning. Customers send Authorization: ApiKey. Partners use OAuth 2.0 authorization code; access tokens expire after one hour. API keys have the same access as an admin user. Calls to https://api.travelperk.com are still accepted. The Spend API is documented separately at developer.yokoy.ai; its authentication page was not opened, so Spend auth is not listed here. Perk POSTs webhook events as JSON and signs them with HMAC-SHA256 in Tk-webhook-hmac-sha256. developers.perk.com/llms.txt is a first-party docs index. No official language SDK was established. iPaaS catalogs were not opened. Computer-use viability is unassessed. MCP scores 8 and the API scores 7. MCP is the best path because the tool reference covers expense writes and booking search that the Travel REST overview does not list as resources.
Best path today: mcp · Overall automatability: 8/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | restapi-keyoauth2 coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: official |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | webhooks: True |
| Data access | export: csv, xlsx, pdf · import: unknown | |
| RPA / UI automation | unknown | web-dom No repeatable UI probe was run. Perk's MCP server and Travel REST API cover trips, expenses, invoices, and webhooks without browser control of the Perk web app. Booking checkout and trip approval still finish in that app.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 7 | 8 | — | — | — | — | 8 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-30 |
license | declared | source | 2026-09-30 |
deployment | declared | source | 2026-09-30 |
modalities.rpa.ui_stack[0] | declared | source | 2026-09-30 |
modalities.api.exists | declared | source | 2026-09-30 |
modalities.api.kinds[0] | declared | source | 2026-09-30 |
modalities.api.auth[0] | declared | source | 2026-09-30 |
modalities.api.auth[1] | declared | source | 2026-09-30 |
modalities.api.coverage | declared | source | 2026-09-30 |
modalities.api.docs | declared | source | 2026-09-30 |
modalities.mcp.first_party | declared | source | 2026-09-30 |
modalities.mcp.verdict | declared | source | 2026-09-30 |
modalities.extensibility.webhooks | declared | source | 2026-09-30 |
modalities.data_access.export[0] | declared | source | 2026-09-30 |
modalities.data_access.export[1] | declared | source | 2026-09-30 |
modalities.data_access.export[2] | declared | source | 2026-09-30 |
modalities.agent_docs.llms_txt | declared | source | 2026-09-30 |
verdict.scores.api | declared | source | 2026-09-30 |
verdict.scores.mcp | declared | source | 2026-09-30 |
freshness.watch[0].url | declared | source | 2026-09-30 |
freshness.watch[1].url | declared | source | 2026-09-30 |
freshness.watch[2].url | declared | source | 2026-09-30 |
freshness.watch[3].url | declared | source | 2026-09-30 |
Related tools
Other products in this database that share a category with Perk.
Last verified 2026-09-30 · volatility high · JSON record