Chrome River (Emburse)

Chrome River is an enterprise travel and expense (T&E) management platform now part of Emburse, offering expense reporting, invoice management, corporate card reconciliation, and travel spend controls for large and global organizations. The chromeriver.com brand now redirects to Emburse Enterprise; expense, invoice, and analytics data are exchanged through Emburse's gated API host (api.emburse.com) and app.chromeriver.com sign-in. Emburse publishes a broad compliance posture (SOC 1/2 Type 2, ISO/IEC 27001/27701/42001, PCI DSS, GDPR/CCPA/CPRA, TX-RAMP) via its trust center and operates a public responsible-disclosure program and Atlassian-hosted status page. This profile was surfaced as a Bain Capital Ventures portfolio lead and enriched by the API Evangelist pipeline from Emburse's public surface; no open developer portal or OpenAPI is published, so spec-bearing artifacts are intentionally absent.

Chrome River (Emburse) is profiled on the APIs.io network. Tagged areas include Company, Ai Apps, Expense Management, Travel And Expense, and Invoice Management.

Chrome River (Emburse)’s developer surface includes support, engineering blog, and 15 more developer resources.

🌐 Visit website 📡 Source on GitHub

22.6/100 emerging ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

0 APIs

Company Ai Apps Expense ManagementTravel And ExpenseInvoice Management Corporate Cards Spend Management Fintech Enterprise Software

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 22.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 7.4 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.9 / 9

Regulatory Posture 7.0 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/chrome-river-emburse: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Chrome River Emburse Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Chrome River Emburse Vulnerability Disclosure

security.txt · contact published

SECURITY

Chrome River Emburse Trust Center

SOC 1 Type 2, SOC 2 Type 2, ISO/IEC 27001, ISO/IEC 27701, ISO/IEC 42001:2023, PCI DSS, GDPR, CCPA, CPRA, EU-US DPF, TX-RAMP

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Access & Security 6

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Compliance

TrustCenter

Security

SecurityTxt

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: chrome-river-emburse
name: Chrome River (Emburse)
description: Chrome River is an enterprise travel and expense (T&E) management platform now part of Emburse, offering expense
  reporting, invoice management, corporate card reconciliation, and travel spend controls for large and global organizations.
  The chromeriver.com brand now redirects to Emburse Enterprise; expense, invoice, and analytics data are exchanged through
  Emburse's gated API host (api.emburse.com) and app.chromeriver.com sign-in. Emburse publishes a broad compliance posture
  (SOC 1/2 Type 2, ISO/IEC 27001/27701/42001, PCI DSS, GDPR/CCPA/CPRA, TX-RAMP) via its trust center and operates a public
  responsible-disclosure program and Atlassian-hosted status page. This profile was surfaced as a Bain Capital Ventures portfolio
  lead and enriched by the API Evangelist pipeline from Emburse's public surface; no open developer portal or OpenAPI is published,
  so spec-bearing artifacts are intentionally absent.
url: https://raw.githubusercontent.com/api-evangelist/chrome-river-emburse/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- bain-capital-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://cdn.sanity.io/images/l5mo20ew/production/d30ee9875c084270cf6a7b0daa1827ae69c0bb09-1200x630.png?fm=jpg&q=75
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Ai Apps
- Expense Management
- Travel And Expense
- Invoice Management
- Corporate Cards
- Spend Management
- Fintech
- Enterprise Software
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis: []
common:
- type: VulnerabilityDisclosure
  url: security/chrome-river-emburse-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/chrome-river-emburse-domain-security.yml
- type: Website
  url: https://www.emburse.com/enterprise/
- type: Support
  url: https://help.emburse.com/hc/en-us
- type: Blog
  url: https://www.emburse.com/blog
- type: PrivacyPolicy
  url: https://legal.emburse.com/
- type: TermsOfService
  url: https://legal.emburse.com/
- type: Login
  url: https://app.chromeriver.com/login
- type: Integrations
  url: https://www.emburse.com/learn/integrations/directory
- type: StatusPage
  url: https://status.emburse.com/
- type: Compliance
  url: https://trust.emburse.com/
- type: TrustCenter
  url: security/chrome-river-emburse-trust-center.yml
- type: Security
  url: https://www.emburse.com/responsible-disclosure
- type: WellKnown
  url: well-known/chrome-river-emburse-well-known.yml
- type: SecurityTxt
  url: well-known/chrome-river-emburse-security.txt
- type: Conformance
  url: conformance/chrome-river-emburse-conformance.yml
- type: Lifecycle
  url: lifecycle/chrome-river-emburse-lifecycle.yml
- type: LLMsTxt
  url: llms/chrome-river-emburse-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/chrome-river-emburse"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/chrome-river-emburse/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/chrome-river-emburse/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.